Design·
Share
Run an Accessibility Audit
Audit your product for accessibility issues and create a remediation plan.
2-4 weeks
8 steps
Overview
A comprehensive accessibility audit process covering automated testing, manual review, assistive technology testing, and prioritized remediation. Ensures your product works for users with disabilities and meets WCAG guidelines.
Prerequisites
- Product or feature to audit
- Access to automated testing tools
- Screen reader available for testing
- Understanding of WCAG 2.1 guidelines
Steps
1
Define Audit Scope
2-3 hoursDetermine what to audit and which standards to apply.
Deliverables:
- •Scope definition (pages, flows, components)
- •WCAG conformance level target (A, AA, AAA)
- •Priority areas identified
- •Audit timeline
Tips:
- •Start with high-traffic pages and critical flows
- •Target WCAG 2.1 AA as minimum standard
- •Include forms, navigation, and interactive components
- •Consider legal requirements for your industry
2
Run Automated Tests
1-2 daysUse automated tools to identify common accessibility issues.
Deliverables:
- •Automated scan results
- •Issues categorized by severity
- •False positives identified
- •Initial issue inventory
Tips:
- •Use tools like axe, WAVE, or Lighthouse
- •Run on multiple pages and states
- •Automated tools catch ~30% of issues - manual testing is essential
- •Document tool versions for reproducibility
3
Manual Accessibility Review
3-5 daysManually test for issues automated tools miss.
Deliverables:
- •Manual test results
- •Keyboard navigation issues
- •Focus order problems
- •Color contrast issues
- •Content and structure issues
Tips:
- •Test keyboard-only navigation (Tab, Enter, Escape, Arrow keys)
- •Check focus visibility and order
- •Verify color contrast (4.5:1 for text)
- •Check heading structure and landmarks
- •Test at 200% zoom
4
Assistive Technology Testing
2-3 daysTest with screen readers and other assistive technologies.
Prompts to use:
Deliverables:
- •Screen reader test results
- •VoiceOver / NVDA / JAWS findings
- •Alternative text issues
- •ARIA implementation issues
Tips:
- •Test with VoiceOver (Mac) and NVDA (Windows) at minimum
- •Complete critical user flows with screen reader only
- •Check that all interactive elements are announced correctly
- •Verify ARIA labels and roles are accurate
5
Document Findings
1-2 daysCompile all findings into a structured accessibility report.
Prompts to use:
Deliverables:
- •Accessibility audit report
- •Issues by WCAG criterion
- •Severity ratings
- •Screenshots and reproduction steps
- •Affected user groups
Tips:
- •Link each issue to specific WCAG criterion
- •Rate severity by user impact (critical, serious, moderate, minor)
- •Include clear reproduction steps
- •Note which user groups are affected
6
Prioritize Remediation
2-3 hoursCreate a prioritized plan to fix accessibility issues.
Prompts to use:
Deliverables:
- •Prioritized issue list
- •Remediation roadmap
- •Quick wins identified
- •Effort estimates
- •Owner assignments
Tips:
- •Fix critical issues first (blocks users entirely)
- •Group related issues for efficient fixes
- •Identify quick wins (high impact, low effort)
- •Consider fixing at component level for broad impact
7
Fix & Verify
2-4 weeksImplement fixes and verify they resolve the issues.
Deliverables:
- •Issues fixed
- •Verification testing completed
- •Regression testing done
- •Documentation updated
Tips:
- •Test fixes with the same methods used to find issues
- •Check for regressions in related areas
- •Update component library if applicable
- •Document patterns for future development
8
Establish Ongoing Process
2-3 hoursSet up processes to maintain accessibility going forward.
Deliverables:
- •Accessibility checklist for new features
- •Automated testing in CI/CD
- •Design review criteria
- •Training plan
Tips:
- •Add accessibility to definition of done
- •Include automated checks in CI/CD pipeline
- •Train designers and developers on basics
- •Schedule periodic audits (quarterly or biannually)