Prioritising Accessibility to Web Development
summary
A quick roadmap: run a Lighthouse audit (showed ~90% before fixing one missing img alt), add eslint-plugin-jsx-a11y to catch issues in-editor, and use tools like axe and Cypress for automated checks; common fixes include adding alt text, proper role="button", keyboard handlers for Enter/Space, and document lang. Claim: roughly 98% of sites have these easy-to-fix problems; building accessible custom widgets is hard, so prefer audited UI libraries — the fixes do work.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker intro
- 1:55What is web accessibility
- 4:25Keyboard compatibility importance
- 6:15WCAG guidelines overview
- 8:45Live coding accessibility demo
- 11:56Fixing common accessibility issues
- 14:42Six common accessibility errors
- 15:45Tools for accessibility testing
- 17:11Custom components and ARIA patterns
- 18:58Text-to-speech and screen readers
- 20:41Semantic HTML importance
- 21:23Conclusion and legal requirements
related talks
44mTesting Web Accessibility
14mAccessible Accessibility
21mPrevent, Catch and Fix Accessibility Issues
45mTips from the Trenches: Accessibility Testing
26mDon't Develop Just for Yourself - A Developer's Checklist to Accessibility
41mAccessibility is a Requirement
11mA11y Broke My Build
29mBuilding Accessibility Testing into Your Workflow