What are accessible names and why should you care?
summary
Explains exactly how browsers compute accessible names using the W3C Accessible Name and Description Computation 1.1, shows the DOM → accessibility tree → API flow, and inspects results in Chrome accessibility tab and Firefox devtools where non-winning sources are crossed out. Demonstrates the priority: ARIA-labelledby wins, then aria-label, then element content/alt, with title as last resort, and gives practical fixes (aria-label, off-screen text) and why placeholders and title are unreliable.
AI-written summary · about
chapters (14)
- 0:00Start
- 2:15Application Programming Interfaces
- 2:51What about Accessibility APIs?
- 3:251. The object's role.
- 3:54The DOM
- 4:36Accessibility Tree
- 7:483. The browser creates a DOM tree.
- 8:47Accessible names
- 17:12Step E.
- 19:07A and BUTTON elements
- 21:45IMG elements
- 23:03Buttons
- 26:05Placeholder
- 28:43Conclusion
related talks
33mIt's the markup that matters
43mBeyond the DOM: what’s in the accessibility tree for you?
40mWebsite Accessibility Examples That Hinder Accessibility
47mPeeling Back the Layers of Web Accessibility
11mIt's the Markup that Matters
46mSemantics and How to Get Them Right
12mHarnessing the Accessibility Tree
01h 07mA web for anyone, anywhere, anytime