Don't Develop Just for Yourself - A Developer's Checklist to Accessibility
summary
Checklist of concrete checks: run automated tools like axe-core and browser extensions but expect them to catch only 15–50% of accessibility failures, so follow with manual tests: verify tab/shift+tab keyboard navigation and that interactive elements are real buttons (not divs with onclick), focus indicators remain visible, hidden content is removed from the tab order, html lang attributes match content, color is not the sole signal (simulate grayscale), pinch-to-zoom works on mobile, and all audio/video has captions or transcripts.
AI-written summary · about
chapters (14)
- 0:00Introduction and welcome
- 1:09Why accessibility matters
- 4:02Automated accessibility testing
- 9:59Test site with only keyboard
- 13:11Keyboard navigation issues
- 18:27Focus indicator importance
- 21:43Use semantic HTML elements
- 22:45Check page language
- 25:14Language mismatch demo
- 27:40Avoid color-only communication
- 30:27Colorblindness simulation
- 33:53Mobile zooming capability
- 37:04Captions and transcripts
- 39:35Summary and resources
related talks
26mDon't Develop Just for Yourself - A Developer's Checklist to Accessibility
35mBuilding an accessibility testing habit
44mTesting Web Accessibility
01h 05mAccessibility Testing 101
56mAccessibility Testing 101
45mTips from the Trenches: Accessibility Testing
29mUnlocking Inclusion, How to Get Started With A11y Testing
21mTesting A11y: Validating Web App Accessibility