Web Accessibility Audit: WCAG Compliance and Audit Process
Web accessibility audit is a systematic process that evaluates your site's compliance with WCAG standards. This guide covers the accessibility audit process, methodologies, and reporting techniques.
Last updated:What is Accessibility Audit?
Accessibility audit is a systematic process that evaluates a website's compliance with WCAG (Web Content Accessibility Guidelines) standards.
Audit combines automated tools, manual tests, and real user tests. Each method detects different issues.
Audit result: Compliance report, issue list, severity classification, fix recommendations, and roadmap.
Legal requirement: Laws like ADA (US), EN 301 549 (EU), Equality Act (UK) can mandate WCAG compliance.
Audit Methodology
1. Scope definition: Which pages and components will be audited? Critical user flows (login, checkout, form submission) prioritized.
2. Automated scanning: Automatic issue detection with axe, WAVE, Lighthouse. Fast and comprehensive scanning.
3. Manual testing: Keyboard navigation, screen reader testing, contrast check, zoom test. Detects issues that automated tools miss.
4. User testing: Testing with real users with disabilities. Detects issues that automated and manual tests don't reflect.
5. Reporting: Issue list, severity, WCAG criterion, fix recommendation, responsible, estimated time.
WCAG Compliance Levels
A (Minimum): Most basic accessibility requirements. Insufficient for most sites.
AA (Standard): Standard for most legal requirements. 90%+ of websites target AA level.
AAA (Highest): Highest accessibility level. Not required for all content (e.g., live video caption).
Conformance statement: Official statement like 'This site conforms to WCAG 2.1 AA level'. Partial conformant and non-conformant options also available.
Audit Tools
axe DevTools: Most comprehensive automated testing tool. Chrome/Firefox extension. CI/CD integration.
WAVE: WebAIM's free tool. Shows issues with visual overlay. Chrome extension and web version.
Lighthouse: Built into Chrome DevTools. Accessibility score and recommendations. Ideal for quick checks.
Pa11y: CLI tool. Integrates into CI/CD pipeline. Automated accessibility tests.
Screen readers: NVDA (Windows), VoiceOver (Mac/iOS), TalkBack (Android). Mandatory for manual testing.
Contrast checkers: WebAIM Contrast Checker, Colour Contrast Analyser. Check WCAG contrast ratios.
Audit Report
Report structure: Executive summary, test methodology, findings list, severity distribution, WCAG compliance status, remediation roadmap.
Finding format: Issue description, affected page/component, WCAG criterion, severity, fix recommendation, screenshot.
Severity classification: Critical (completely blocks user), Major (makes usage difficult), Minor (small issue), Enhancement (improvement suggestion).
Remediation roadmap: Priority order, estimated time, responsible team, deadline.
Re-audit: Re-audit after fixes. Verify compliance status.
Continuous Accessibility
Shift-left: Think about accessibility from the beginning of the development process. In design and development phase.
Design system: Accessible component library. Each component complies with accessibility standards.
CI/CD integration: Integrate accessibility tests into pipeline. Automated testing with Pa11y, axe-core.
Developer training: Train team on accessibility. WCAG, ARIA, semantic HTML.
Monitoring: Periodic accessibility audit. Accessibility check on new pages and components.
Related tools
Practical articles on this topic
White Text on a Green Button: Measure Before Choosing
A bright green sign-up button may attract attention while its white label remains uncomfortable to read.
Dark Mode Implementation Guide: CSS, JavaScript and System Preference
Dark mode reduces eye strain and extends battery life.
Web Accessibility: WCAG, ARIA and Inclusive Design
Web accessibility ensures that people with disabilities can use websites.