It's the markup that matters
summary
Markup determines the accessibility tree and the values assistive tech sees, not frameworks or buzzwords; browsers generate roles, names and states from HTML and the Accessibility Name computation, and an audit of top sites finds almost half of inputs lack accessible names. Concrete fixes include proper <label> associations, table <caption>s, and using <button> not divs. Emerging platform work—the Accessibility Object Model and Open UI primitives—are already testable: selectmenu and popup attributes are experimental behind flags in Chromium/Canary.
AI-written summary · about
chapters (19)
- 0:00Introduction to HTML
- 2:44Speaker background
- 3:24Accessibility fundamentals
- 5:35The accessibility tree
- 7:11Semantic markup
- 8:29Structure and navigation
- 10:45Landmarks for navigation
- 12:24Form controls
- 14:14Table semantics
- 15:30Button accessibility
- 17:16Learning resources
- 18:20Accessibility Object Model
- 20:18AOM events and testing
- 22:00Future of web controls
- 23:03Standardizing controls
- 25:09Select menu proposal
- 27:22Pop-up attribute
- 28:23Pop-up behavior
- 30:29Wrapping up
related talks
11mIt's the Markup that Matters
33mMarkup matters
28mHumanizing The Markup Language: Thoughtful Semantics for Better Web Experiences
46mSemantics and How to Get Them Right
48mCoding For Accessibility Best Practices from the Front Lines
35mWhat are accessible names and why should you care?
41mTechnologic (Human After All): Accessibility remix
38mWeb accessibility - it's not just about HTML