What HTML5 Means for Web Accessibility
summary
HTML5 adds semantics but real accessibility depends on concrete pieces: many sectioning elements show spotty browser and assistive‑technology support so add role attributes (header role=banner, footer role=contentinfo, nav role=navigation) as ARIA suspenders. Use native audio/video plus <track kind="captions"> (WebVTT) or provide captions; prefer <button> for custom controls. Canvas is weak — include a hidden DOM fallback that exposes links and keyboard focus; test across browsers, screen readers and older users because support is inconsistent.
AI-written summary · about
chapters (10)
- 0:00Start
- 5:06Accessibility is easy
- 5:46Accessibility is hard
- 6:51Accessibility is Frustrating
- 7:56father, for have sinned
- 9:34Accessibility is good for you
- 14:26HTML5 mean for web accessibility?
- 18:41Is there any hope?
- 36:48about Mobile Accessibility
- 37:33Use HTML5 elements They're natively supported
related talks
38mWeb accessibility - it's not just about HTML
46mSemantics and How to Get Them Right
01h 07mA web for anyone, anywhere, anytime
33mIt's the markup that matters
45mA Web for Anyone, Anywhere, Anytime
28mHumanizing The Markup Language: Thoughtful Semantics for Better Web Experiences
33mMarkup matters
44mWeb accessibility for Artisans