Should I be using WAI-ARIA?
Summary
Use WAI-ARIA only when native HTML cannot provide the required accessibility, especially for dynamic or custom interface components. Prefer standard HTML elements whenever possible, and apply WAI-ARIA selectively to enhance accessibility for assistive technology users rather than as a default solution.
What it is
The introduction of WAI-ARIA has added new ways for website owners to make sure their websites live up to the success criteria in WCAG. It is one of many tools that can help you create and maintain accessible web content.
How it works
In many cases, normal HTML can be fully accessible without the use of WAI-ARIA.
An example is the WAI-ARIA landmark roles (e.g. role="navigation"). These can be applied to sections of a page to indicate the semantic role of each section of the page. The same information can be provided with HTML5 sections (e.g., <nav>) for navigation.
When to use vs. when not to use
When to use WAI-ARIA
- When implementing non-standard functionality that is dynamic or interactive
- When enhancing accessibility for assistive technology users (e.g., screen readers, speech interfaces)
- When retrofitting an existing site to improve accessibility where native HTML cannot fully meet requirements
WAI-ARIA provides tools for making non-standard functionality accessible for users of speech-based interfaces.
When NOT to use WAI-ARIA
- When native HTML elements already provide the needed semantics
- When building a site from scratch where standard HTML can achieve accessibility
- As the only method of creating an accessible website
Most users will not benefit from WAI-ARIA alone, so it should not be relied on as the primary accessibility solution.
Why it matters
The target group for WAI-ARIA is relatively narrow. Blind people who use screen readers to access web content, and people using speech instructions to control their computers will benefit from WAI-ARIA. Most other users will not benefit from WAI-ARIA, which means that it shouldn't be your only means of creating an accessible website.
WAI-ARIA really shines if you have some non-standard functionality that is dynamic or interactive. In these cases, WAI-ARIA provides tools for making your non-standard functionality accessible for users of speech-based interfaces.
If you are redesigning your website from scratch, accessibility through native HTML should be preferred where possible. However, if you are retrofitting your site to improve accessibility, using WAI-ARIA might be the best way to get the job done in many cases.
Key Takeaways
- Prefer native HTML first; it is often sufficient for accessibility
- Use WAI-ARIA only when necessary for dynamic or custom components
- WAI-ARIA is most beneficial for screen reader and speech interface users
- Do not rely on WAI-ARIA as a standalone accessibility solution
- Use it strategically when retrofitting accessibility into existing experiences
Additional resources
Did you find it helpful? Yes No
Send feedback