Inaccessible websites? - it's you, not JavaScript

on YouTube ↗35m

" summary

Claim: JavaScript often causes, not solves, accessibility failures and small fixes restore usability. Demos show a div-as-button that excludes keyboard users and is fixed with tabindex + role + keydown and preventDefault; a modal that requires focus trapping, Escape to close and focus restore and the sample code implements and works; motion respects prefers-reduced-motion media query or matchMedia; WHO stat 15% appears. Testing and dev tools used include Lighthouse aXe Wave and VS Code/webhint and eslint-plugin-jsx-a11y.

AI-written summary · about

" chapters (13)

1. 0:00Start
2. 2:44Multiple type of disabilities
3. 3:21Cognitive and neurological
4. 6:10versus for interactivity
5. 11:16Keyboard interactions
6. 12:35Event handlers
7. 17:13Modal interactions
8. 24:48Use Case - Animations
9. 28:14Useful tools and extensions
10. 30:48TESTING
11. 31:00DEVELOPMENT
12. 32:43Conclusion
13. 33:25Resources

" related talks

• 30mAccessible.JSJemima Abu · CityJS Conference 2020
• 33mAccessibility and JS: side-by-sideFelipe de Albuquerque · JSConf US 2015
• 42mCSS, JavaScript and AccessibilityIre Aderinokun · Pixel Pioneers 2023
• 29mJavaScript for EverybodyMarcy Sutton Todd · JSConf EU 2014
• 38mWeb accessibility - it's not just about HTMLIre Aderinokun · ffconf 2023
• 32mCommon ways we break accessibility and how to avoid themLaura Carvajal · Render Conference 2018
• 41mWhat If We Talked About Web Accessibility?Olivier Leplus · DevFest Toulouse 2018
• 26mMake the internet a better place - with coding for accessibilityLarissa Günther · XConf Europe 2023