What Is This Thing and What Does It Do?
summary
HTML semantics and browser implementations decide what assistive tech hears, not visual styling or JavaScript tricks; ARIA only labels — it doesn’t turn a span into a native widget. Examples: href="#" anchors that do nothing, chosen jQuery plugin and pretty checkable replace selects/radios but omit the dozens of keyboard behaviors and exposed properties browsers provide. Accessibility APIs consume only name state role value. WCAG maps to POUR and lists ~400 techniques, so use native controls or fully reimplement every behavior.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:35The fundamental question
- 4:21History of DOM and controls
- 9:53DOM and accessibility APIs
- 16:02API communication
- 20:44Principles of web standards
- 23:29UX and consistency
- 30:16Role of ARIA and conclusion
related talks
27mMaking Interactions Accessible to All Users
25mThe web is inherently accessible
48mCoding For Accessibility Best Practices from the Front Lines
21mAccessibility matters
01h 07mInclusive Design Series: How to stop worrying and love accessible forms
22mWeb Accessibility - a better user experience for everyone!
20mImpactful Accessibility: The Changes that Mean the Most
29mAccessibility Matters: Creating a Better Web