Open LaurenceRLewis opened 2 years ago
It seems the primary question is whether the spec should mention the need for expanded? If so, we will transfer this to the ARIA spec repo.
BTW, we do not recommend use of tab pattern for accordion.
The ARIA Authoring Practices (APG) Task Force just discussed Issue 2363 - ARIA 1.2 Specification role Tab Tabpanel - does not match the info on new APG
.
The Specification for the TAB Role it states "For a multi-selectable tablist, authors SHOULD ensure each visible tabpanel has its aria-expanded attribute set to true, and that the remaining hidden tabpanel elements have their aria-expanded attributes set to false.". AND "In either case, authors SHOULD ensure that a selected tab has its aria-selected attribute set to true, that inactive tab elements have their aria-selected attribute set to false".
For the tab role and aria-selected, would this be better as a MUST not a SHOULD, as without it there is no indication that the tab panel is selected or expanded. What is the purpose of adding aria-expanded to the tabpanel?
I know of no other widgets, for example the Accordion where aria-expanded is placed on the expanding element and not the triggering button.
References
ARIA Authoring Practices Guide (APG) - Tabs WAI-ARIA Roles, States, and Properties
Accessible Rich Internet Applications (WAI-ARIA) 1.2 - W3C Candidate Recommendation Draft 08 December 2021 tab role