Post-launch accessibility testing on a shoestring budget
Short answer: After launch, run a focused afternoon pass: keyboard everything, sample VoiceOver or NVDA on forms, check contrast on real phones, and log issues with severity—not perfection scores.
Incremental fixes beat deferred “big bang” audits you never schedule.
Shoestring sequence
- Top 5 user journeys from analytics.
- Automated scan on those URLs.
- Manual verification of flagged items and traps.
Triaging
Label blockers vs nice-to-haves; ship blockers quickly, schedule the rest.
Culture
Put accessibility checks in your launch checklist alongside SSL and analytics—same tier.
Frequently asked questions
Free screen readers?
NVDA on Windows; VoiceOver built into macOS/iOS—learn basics internally.
How to prevent regressions?
Component libraries, training, and CI checks on templates you control.