| Accessible Rich Internet Applications Specification |
- Defines the vocabulary for the roles, properties and states to describe the features of a website.
- Adding aria markup does not effect web bowser behavior or rendering, only what is communicated through accessibility APIs to screen readers.
|
| HTML living standard |
- Defines the semantics and behaviors of HTML markup.
- Native HTML markup should be used instead of ARIA markup.
- This document is a living standard, so it has no version number and reflects the current state of interoperability of HTML on the web.
|
| HTML Accessibility API Mappings 1.0 |
- Defines default ARIA roles for HTML elements.
- Restricts ARIA roles that can override the default role, based on the semantics of the element.
|
|
Accessible Name and Description Computation 1.1
|
- Defines the priority and the algorithms for computing accessible name and accessible description.
- Complexity of algorithm due to
aria-labelledby and aria-describedby computation.
- Simpler explanation of the basics of naming and describing in ARIA Authoring Practices.
|
| Core Accessibility API Mappings for ARIA |
- Defines how ARIA roles, properties and states are mapped to specific accessibility APIs.
- Currently supported APIs:
- ATK/AT-SPI (Linux/Unix)
- Microsoft Active Accessibility (MSAA) + IAccessible2
- Microsoft UI Automate
- MacOS Accessibility API
|