HOW TO DO GOOD WITHOUT DOING ANYTHING
summary
Claims that a small upfront investment plus automation yields big long‑term savings and guards against regressions, and demonstrates it end to end: eslint-plugin-jsx-a11y, Lighthouse, axe-core, and browser tools wired into CI plus unit/integration/e2e tests (jest + react‑testing‑library, Cypress with cypress‑axe). Builds a real slack signup flow with an accessible input and a visually hidden alert and reports that automated checks catch only about 60–70% so manual screen‑reader/keyboard testing still runs.
AI-written summary · about
chapters (20)
- 0:00Start
- 1:55How Can I Do Good without Doing Nothing
- 2:23Yuraima Estevez
- 2:53Accessibility
- 3:19Web Accessibility
- 5:54Disclaimers
- 7:08Tools
- 8:21Lighthouse
- 11:11Reactx
- 13:45Tool Recommendations
- 14:39Unit Tests
- 15:52Accessible Button
- 19:28Focus
- 23:57Accessible Alert Component
- 25:15Create an Integration Test
- 27:28End-to-End Tests
- 27:50Intent Testing Library Needs
- 36:21Screen Meters
- 39:51Accessibility Is Not the First Priority
- 40:23Accessibility Is for Your Users
related talks
31mHow to do Good Without Doing Anything
25mHow to do good without doing anything
29mBuilding Accessibility Testing into Your Workflow
53mAutomating Accessibility Assurance
01h 06mnpm run a11y-test
33mAutomated Accessibility Testing
07mHow to Catch a11y Defects During Unit and E2E Testing
35mAutomated Accessibility Testing