CSS, JavaScript and Accessibility
summary
Claims that plain semantic HTML yields ~90% of accessibility while CSS and JS cause the rest, with concrete fixes and failures: CSS generated content unreliable, using display:none hides from assistive tech so prefer position absolute off-screen for visually hidden text, use prefers-reduced-motion and feature queries for progressive enhancement, preserve native semantics (buttons/links) instead of rebuilding with divs, add JS only when it improves behavior (accessible media players, form suggestions, carousel controls). Cites 0.07% screen reader users disable JS and >50% Opera Mini share in some regions.
AI-written summary · about
chapters (8)
- 0:00Start
- 4:28Missing text alternatives
- 14:14Visual order
- 19:22Guideline 1.4.8 - Visual presentation
- 20:26Guideline 2.4.1 - Bypass blocks
- 22:27Legacy code
- 25:00CSS & Accessibility
- 40:11JavaScript & Accessibility
related talks
38mWeb accessibility - it's not just about HTML
33mMarkup matters
33mAccessibility and JS: side-by-side
51mWriting even more CSS with Accessibility in Mind
35mBetween Accessibility and Style: Semantics and CSS Architecture
35mInaccessible websites? - it's you, not JavaScript
44mWeb accessibility for Artisans
01h 07mA web for anyone, anywhere, anytime