You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the solution you'd like
When creating components that include a toggle it's accessibility best practice to add aria-expanded and aria-controls/aria-owns. However, the aria-controls needs to reference a unique ID on a page so assistive technology knows "if I click this button this other element over here should expand".
Describe the solution you'd like
When creating components that include a toggle it's accessibility best practice to add
aria-expanded
andaria-controls
/aria-owns
. However, thearia-controls
needs to reference a unique ID on a page so assistive technology knows "if I click this button this other element over here should expand".Something like the following would be ideal:
Which would render something like:
Describe alternatives you've considered
The current solution is to add this to our individual twig files:
Came across this craftCMS approach that we might be able to use: https://craftcms.stackexchange.com/questions/29628/give-included-twig-component-unique-id
The text was updated successfully, but these errors were encountered: