Description of the need
Backdrop tabs, such as those on /user have role="tablist" but the children tab links do not have role="tab". As per https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/ta..., the tab links need the tab role. It also states that the "panels" need have the role tabpanel, though given that only one is actually loaded to the page at a time, it's not clear if it makes sense.
Example from Mozilla:
<div class="tabs">
<div role="tablist" aria-label="Sample Tabs">
<button
role="tab"
aria-selected="true"
aria-controls="panel-1"
id="tab-1"
tabindex="0">
First Tab
</button>
<button
role="tab"
aria-selected="false"
aria-controls="panel-2"
id="tab-2"
tabindex="-1">
Second Tab
</button>
<button
role="tab"
aria-selected="false"
aria-controls="panel-3"
id="tab-3"
tabindex="-1">
Third Tab
</button>
</div>
<div id="panel-1" role="tabpanel" tabindex="0" aria-labelledby="tab-1">
<p>Content for the first panel</p>
</div>
<div id="panel-2" role="tabpanel" tabindex="0" aria-labelledby="tab-2" hidden>
<p>Content for the second panel</p>
</div>
<div id="panel-3" role="tabpanel" tabindex="0" aria-labelledby="tab-3" hidden>
<p>Content for the third panel</p>
</div>
</div>
GitHub Issue #:
5982
Recent comments
One effective way to handle this in Backdrop CMS without adding heavy modules is to use a simple "File" field on your content type and set the display formatter to "Generic file." This creates a...
Simple PDF Upload & Link
That sounds like a frustrating loop. Since you're considering a manual update, overwriting the /core folder is usually the most reliable way to get past those archive errors. Just make sure to...
Update Problems
I’ve been looking into different ways to handle integrations more efficiently, and the approach you mentioned here clarifies a few things I was stuck on. Definitely going to try implementing...
Integration