Devon Persing - SeattleJS Conference
summary
Accessibility integrates into the full feature lifecycle, not an end-of-cycle fix, and this talk gives concrete steps: follow WCAG/ARIA specs and prefer simple HTML over complex JS, run keyboard-only testing and automated linters, validate DOM order across breakpoints, ensure form labels and text equivalents, and log measurable fixes. Ask vendors for third-party procurement checks (can output be adapted, do they follow accessibility guidelines), recruit teammates for quick keyboard walkthroughs, test with people with disabilities, and set small repeatable goals.
AI-written summary · about
chapters (8)
- 0:00Introduction to accessibility
- 1:04Why accessibility is unsustainable
- 2:49Technical best practices for accessibility
- 5:16Procurement and third-party code
- 6:37Automated and manual testing
- 7:41Asking stakeholders the right questions
- 9:08Understanding user needs
- 10:10Building a community practice
related talks
26mAccessibility Is a Marathon, not a Sprint
30mAccessible.JS
45mTips from the Trenches: Accessibility Testing
35mAccelerating accessibility in web
22mFrom a Workshop to a Wake-Up Call: My Journey into Accessibility
33mAccessibility and JS: side-by-side
01h 02mAccessibility - how to get the job done in a highly collaborative manner
14mAccessible Accessibility