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
I noticed that inside your accessibility documentation in the section Content Structure, you have a tip for landmarks that's not up-to-date. The quote I am referring to is this:
Avoid specifying redundant roles. In practice this particular instance of redundancy will likely not have unforeseen side effects, other than unnecessarily making the markup more verbose, and incorrectly signalling to other authors that this practice is useful.
I recommend replacing the current tip with the just-named information. The table of examples for landmark roles you give within your docs implies using the redundant ARIA roles is what one should do.
Thanks!
The text was updated successfully, but these errors were encountered:
dnikub
changed the title
Update Accessibility Documentation on
Update Accessibility Documentation on content structure (landmarks)
Jul 19, 2023
Hello,
I noticed that inside your accessibility documentation in the section Content Structure, you have a tip for landmarks that's not up-to-date. The quote I am referring to is this:
I believe this tip can be removed from the Vue 3 docs due to multiple reasons:
The only legacy browser referenced here is IE, which is not supported anymore since June 2022.
Vue 3 does not support IE, as it uses ES2015 features that cannot be polyfilled in legacy browsers (as you write yourself in your FAQs).
Sticking to the semantic HTML element and avoiding adding a redundant ARIA landmark role is recommended. The official W3C recommendation for ARIA in HTML in 2023 is:
I recommend replacing the current tip with the just-named information. The table of examples for landmark roles you give within your docs implies using the redundant ARIA roles is what one should do.
Thanks!
The text was updated successfully, but these errors were encountered: