Length 13:09Accessible Names Deconstructed: From ARIA Attributes to proper Testing - Web Accessibility For All
About this video
The video explains how browsers derive accessible names from ARIA, HTML and DOM structure, and why those names matter for screen reader and voice control users. It covers common developer pitfalls, testing, and how professional teams keep naming consistent.
What you’ll learn
- Explain how browsers compute an accessible name from ARIA, HTML and DOM structure
- Avoid common pitfalls such as mixing aria-label and aria-labelledby
- Keep element names consistent across components, devices and languages
Recommended
Length 13:09
Length 13:51One Press at a Time: Designing for Switch Device Users - Web Accessibility For All
IntermediateAccessibility
Length 13:53Sticky, Floating, and Completely Inaccessible? Not Anymore - Web Accessibility For All
IntermediateAccessibility
Length 16:16
Length 20:07
Length 26:02RF21 – Eeva-Jonna Panula – How to Catch Low-Hanging Accessibility Fruits while Developing
IntermediateAccessibility
Length 22:11Marianna Österlund - Better accessibility with a user-centric view
IntermediateAccessibility
Length 26:17Eeva Jonna 'Eevis' Panula - Let’s Keep Our Promises - ARIA, Styles and Keyboard Navigation
IntermediateAccessibility
Length 23:28Roosa Kallionpää - Accessible navigation in single-page applications
IntermediateAccessibility
Length 25:30Proven ways to make your website accessible in 2023 - Alena Nikolaeva | JSHeroes 2023
IntermediateAccessibility
Length 27:53Built-in accessibility: blessing or curse? - Hidde de Vries | JSHeroes 2025
IntermediateAccessibility
Length 19:37