Web accessibility - it's not just about HTML
summary
Plain semantic HTML produces accessible pages by default and about 90% of accessibility comes from using HTML correctly while 10% breaks when CSS/JavaScript are misused. CSS generator content (content:) is unreliable for assistive tech, and display: none hides from AT whereas position off-screen for screen readers keeps content reachable; use feature queries and media queries like prefers-reduced-motion to adapt. Don’t replace buttons/links with divs — adding tabindex, role and key handlers recreates many built‑in behaviors. Require JS only when unavoidable; carousels and video often need ARIA, controls and JS to be truly accessible.
AI-written summary · about
chapters (8)
- 0:00Web accessibility intro
- 2:09Access needs groups
- 8:14CSS vs HTML semantics
- 13:32CSS with accessible defaults
- 22:34CSS for accessibility
- 23:17JavaScript as enhancement
- 30:43JS improves accessibility
- 36:44Accessibility by default
related talks
42mCSS, JavaScript and Accessibility
52mCommon Accessibility Pitfalls
01h 07mA web for anyone, anywhere, anytime
44mWeb accessibility for Artisans
51mWriting even more CSS with Accessibility in Mind
41mBuilding Accessible Vue Components
01h 01mA web for anyone, anywhere, anytime
46mSemantics and How to Get Them Right