Accessibility feedback loop: Continuous a11y improvement in your development life cycle
summary
Banking teams adopt a per-application feedback loop that replaces infrequent audits with continuous checks: one-team WCAG audits plus remediation sprints, accessibility champions and a guild, testers with visual impairments doing manual evaluations, and a monitoring dashboard fed by pipeline runs. Automation uses ESLint + axe-core + Playwright and Lighthouse, reports average 20–30 issues per report, tickets copy-paste into JIRA, and successful apps earn an accessibility certificate and scheduled recertification.
AI-written summary · about
chapters (18)
- 0:00Digital accessibility intro
- 3:22Why accessibility matters
- 4:47WCAG and W3C standards
- 6:33Agile development lifecycle
- 8:19Accessibility guild programs
- 10:09Four key accessibility initiatives
- 13:25Organization-wide accessibility steps
- 14:07Champion program details
- 15:58Guild program structure
- 17:21Accessibility training start
- 19:27Testing insights frequently
- 24:03Delayed audits problems
- 25:46Continuous feedback loop
- 27:53Accessibility certification
- 29:19Reporting issues effectively
- 32:17Acceptance criteria explained
- 36:36Automation and monitoring
- 44:22Accessibility integration summary
related talks
53mAutomating Accessibility Assurance
28mEnterprise Grade Accessibility for Everyone
50mShift Left on Accessibility: Beyond the Audit
33mAutomated Accessibility Testing
29mBuilding Accessibility Testing into Your Workflow
35mAutomated Accessibility Testing
52mAfter the audit: Integrating accessibility into the testing process
38mHow to set up an accessibility program in an imperfect world