Testing for Accessibility
summary
Measures a site with several free checkers and finds roughly 110 violations and scores in the low 40–60% range, then uses Sally (s a11y) to highlight exact elements to fix and spends about four to five hours cleaning one page. Sally runs only on localhost via a small injected snippet, then accessibility tests move into CI by adding Playwright accessibility checks so builds fail on regressions. Also recommends hiring users with disabilities for direct, actionable feedback.
AI-written summary · about
chapters (13)
- 0:00Introduction to accessibility
- 2:11Why accessibility matters
- 9:15Ethics and legal responsibility
- 12:43Inclusive team hiring
- 15:53First step: Recognize the problem
- 20:12WCAG standards explained
- 26:16Measure accessibility gaps
- 32:21Tools for automated testing
- 35:54Fixing with Sally tool
- 43:03Verify improvements
- 45:54CI/CD integration with Playwright
- 50:12Continuous accessibility checks
- 54:02Real user feedback
