Web Content Accessibility Guidelines (WCAG)
The international standard for web accessibility developed by the W3C.
Detailed Explanation
WCAG is organized into four principles: Perceivable, Operable, Understandable, and Robust (POUR). It defines three levels of conformance: A (lowest), AA (standard), and AAA (highest). Most government and enterprise sites aim for AA compliance. Following WCAG helps developers create sites that are usable by everyone, regardless of the device or assistive technology they use.
Quick Summary
WCAG is the W3C's checklist for accessible web content, grouped under the POUR principles and graded at conformance levels A, AA, and AAA. AA is the de-facto legal and procurement baseline worldwide.
Key Takeaways
- WCAG 2.1 and 2.2 add success criteria for mobile, low-vision, and cognitive disabilities on top of the 2.0 baseline.
- Level AA is the target most laws cite (ADA, EU EN 301 549, UK Equality Act); AAA is aspirational and not required site-wide.
- Each success criterion is testable, pass/fail, which is why automated tools can only cover ~30% of them.
- Conformance is per-page, not per-site: every page in scope must meet every criterion at the chosen level.
- WCAG is the technical standard; WAI-ARIA, ATAG, and UAAG are companion specs that fill in widget and authoring-tool gaps.
When to use it
- Auditing a site or app to meet legal accessibility obligations (Section 508, EAA, AODA).
- Writing acceptance criteria for design systems so components are accessible by default.
- Procurement: requiring vendor VPATs that document WCAG conformance before purchase.
- Training designers and engineers on concrete, testable accessibility rules instead of vague "a11y" goals.
Common Mistakes
- Relying only on automated scanners, they catch contrast and missing-alt issues but miss most criteria like focus order or meaningful labels.
- Claiming "WCAG compliant" without specifying the version and level, which makes the claim unverifiable.
- Bolting on accessibility at the end of a project instead of designing for it from the start.
- Treating AAA as the goal everywhere, WCAG itself says AAA is not generally achievable for full sites.
Web Content Accessibility Guidelines (WCAG), Frequently Asked
What is the difference between WCAG 2.1 and 2.2?
WCAG 2.2 (published 2023) is backward-compatible with 2.1 and adds nine new success criteria focused on mobile use, dragging gestures, focus appearance, and reducing cognitive load. Sites that conform to 2.2 automatically conform to 2.1 and 2.0.
Is WCAG legally required?
It is not a law itself, but most accessibility laws cite WCAG as the technical standard. The U.S. ADA, EU European Accessibility Act, UK Equality Act, and Canada's AODA all use WCAG AA as the benchmark courts and regulators apply.
Can a single-page app be WCAG-compliant?
Yes, but it has to handle focus management, route announcements, and dynamic content updates explicitly. SPAs fail WCAG most often on criteria 2.4.3 (focus order) and 4.1.3 (status messages) because route changes are invisible to assistive tech without code.