ARIA is often associated with more accessibility errors, but it was created to improve the web when used correctly.
ARIA modifies the accessibility meta-information, including roles, states, and properties, that assistive technologies use to build an interface for users.
Use landmarks to define key page regions and attributes like `aria-expanded` and `aria-pressed` to communicate the state of interactive controls.
Use `aria-label` for unlabeled controls, `aria-current` for active items, and `aria-live` to announce important dynamic UI changes.
Complex widgets like menus require careful implementation of roles and keyboard interactions, while `aria-hidden` can remove purely decorative content.
Avoid common mistakes like misinterpreting authoring guides, creating conflicts between ARIA states and the visual UI, or losing focus after an action.
Be cautious with attributes like `role="application"` and `aria-roledescription` that can break user expectations, and remember that ARIA adds semantics, not behavior.
31:38Anuradha Kumari
31:30Ramona Domen
30:07Julia Undeutsch
56:01Dirk Ginader
25:33Manuel Mauky
27:16Tanja Ulianova
56:00Karl Groves
29:59Konstantin Tieber
Jobs that call for the skills explored in this talk.
Bite Client
Atlanta, United States of America
Speech Processing Solutions
Vienna, Austria
JO Media Software Solutions GmBh
Brunn am Gebirge, Austria
webLyzard
Vienna, Austria