When to use aria-hidden="true", and when you might need display: none:
aria-hiddenby itself is not enough to completely hide an element from all users, if that is the end goal.
When to use role="presentation" (or role="none"):
Where
aria-hiddencan be used to completely hide content from assistive technology, modifying an element’sroleto “none” or “presentation” removes the semantics of the element, but does not hide the content from assistive technologies.
Hidde gives an in-depth explanation of the Accessibility Object Model, coming soon to browsers near you:
In a way, that’s a bit like what Service Workers do for the network and Houdini for style: give developers control over something that was previously done only by the browser.
On the need for a way to mark parts of a document as “inert” while the user is interacting with modal content.
A great presentation on web components by Marcy, with an emphasis on keeping them accessible.
Alice Bartlett shares her experience of getting aria-live regions to work in a meaningful way.
This helps to clarify the difference between native semantics and ARIA additions.
Trying to understand a different mindset to mine.
JavaScript should only do what only JavaScript can do.
Here’s how I interpret the top-level guidance in the Web Content Accessibility Guidelines.
When it comes to sustainable web design, the hard work is invisible.
Business, sustainability, and inclusivity.