Brief History of ARIA: Purpose
- Provide an interoperable way to describe the features of custom widgets:
Role: Describes the types of widget, which implies the keyboard interaction patterns.
Properties and States: Describing features like "expandable", "checked" or "selected".
Language independence: Roles, properties and states can be translated by the operating systems and assistive technologies to local languages.
Labeling: How to label the features of the widget and its components (e.g. accessible name).
- Define markup mappings to accessibility APIs:
- ATK/AT-SPI (Linux/Unix)
- Microsoft Active Accessibility (MSAA) + IAccessible2
- Microsoft UI Automate
- MacOS Accessibility API