The Web Content Accessibility Guidelines (WCAG) are the world's de facto rulebook for digital accessibility. Published by the World Wide Web Consortium (W3C) through its Web Accessibility Initiative, WCAG explains — in testable, technology-neutral terms — how to make websites, web apps, and documents usable by people with disabilities, including those who are blind or have low vision, are deaf or hard of hearing, have motor impairments, or have cognitive differences.
Here's the key thing to understand: WCAG itself is not a law. It's a technical standard. But nearly every accessibility law that matters — the ADA in the United States, the European Accessibility Act, Section 508, Canada's AODA, and many others — uses WCAG as its measuring stick. When a regulator, court, or plaintiff asks whether your website is accessible, the practical question is almost always "does it conform to WCAG?"
That makes WCAG the single most useful thing for a business owner to understand about web accessibility. If your site conforms to the current widely-referenced version at Level AA, you are in a strong position under virtually every accessibility regime in the world.
A standard, not a statute
WCAG is published by the W3C, not a government. It carries legal weight because laws and courts around the world adopt it as the benchmark for what "accessible" means.
Three conformance levels
Level A is the minimum, Level AA is the widely accepted legal and industry target, and Level AAA is the highest tier. Almost every law that cites WCAG requires Level AA.
Built on four principles
Content must be Perceivable, Operable, Understandable, and Robust — the POUR principles. Every WCAG success criterion rolls up to one of these four ideas.
WCAG 2.2 is current
WCAG 2.2, published in October 2023, is the latest finished version. It is backwards compatible: a site that meets 2.2 AA also meets 2.1 AA and 2.0 AA.
What WCAG is and where it came from
WCAG is developed through an open, international process by the W3C — the same body that standardizes HTML and CSS. WCAG 2.0 arrived in 2008 and became so foundational that it was also published as an ISO standard (ISO/IEC 40500). WCAG 2.1 followed in 2018, adding criteria for mobile devices, low vision, and cognitive disabilities. WCAG 2.2 landed in October 2023 with further refinements around focus visibility, dragging alternatives, and easier authentication.
A future WCAG 3.0 is in development, but it remains a working draft and is years away from replacing the 2.x series. For planning purposes in 2026, WCAG 2.1 and 2.2 at Level AA are the versions that matter: most laws still formally cite 2.0 or 2.1, while 2.2 is the sensible target for new work since it includes everything in the earlier versions.
Who needs to comply
Because WCAG is a standard rather than a law, nobody is required to follow WCAG in the abstract — you are required to follow the laws that reference it. In practice, that covers a very wide net:
- US businesses: courts and the Department of Justice treat WCAG as the reference point for ADA website claims, and a 2024 DOJ rule formally requires WCAG 2.1 AA for state and local government websites.
- US federal agencies and their vendors: Section 508 incorporates WCAG 2.0 AA for federal digital content and procurement.
- Companies selling into the EU: the European Accessibility Act, whose obligations have applied since June 28, 2025, points to the EN 301 549 standard, which is built on WCAG.
- Organizations in Ontario, Canada: the AODA requires WCAG 2.0 AA for most public-facing websites.
- Many other jurisdictions — the UK, Australia, Japan, and beyond — reference WCAG in public-sector or general accessibility rules.
The core requirements: POUR and conformance levels
WCAG organizes its requirements — called success criteria — under four principles. Perceivable means users can take in your content: images need text alternatives, videos need captions, and text needs sufficient color contrast. Operable means users can navigate and interact: everything must work with a keyboard alone, focus must be visible, and nothing should trap or rush the user. Understandable means content and controls behave predictably: clear labels, helpful error messages, readable language. Robust means your code is clean enough for assistive technologies like screen readers to interpret reliably.
Each success criterion is assigned a level. Level A criteria address the most severe barriers — failing them can make a site unusable for some people. Level AA adds requirements like a 4.5:1 contrast ratio for normal text, visible focus indicators, and consistent navigation. Level AAA is aspirational for most sites and is rarely required by law. When people say "WCAG compliant," they almost always mean conformance at Level AA, which includes meeting every Level A criterion too.
Enforcement and legal risk
WCAG has no enforcement body of its own — the risk comes through the laws that adopt it. In the US, thousands of ADA lawsuits and demand letters targeting inaccessible websites are filed every year, and settlements typically include monetary payments, legal fees, and a commitment to remediate to WCAG AA. In the EU, member states enforce the European Accessibility Act with penalties that vary by country and can be substantial, particularly for continued non-compliance. Public-sector rules like Section 508 and the AODA carry their own compliance and penalty mechanisms.
Beyond legal exposure, there is a straightforward business case: roughly one in six people worldwide has a significant disability, and an inaccessible site turns those customers away while often hurting SEO and overall usability for everyone else.
Practical steps toward WCAG conformance
You do not need to memorize dozens of success criteria to make real progress. Most sites fail on a familiar handful of issues, so a focused effort goes a long way:
- Run an automated scan to catch machine-detectable issues like missing alt text, poor contrast, missing form labels, and broken ARIA attributes.
- Test your key user journeys — homepage, navigation, checkout or signup, contact forms — using only a keyboard, then with a screen reader such as NVDA or VoiceOver.
- Fix the fundamentals first: text alternatives for images, captions for video, sufficient color contrast, visible focus states, and properly labeled forms.
- Add accessibility to your workflow so new pages and features are checked before launch, not retrofitted after a complaint.
- Publish an accessibility statement describing your target (e.g., WCAG 2.2 AA), known gaps, and a way for users to report problems.
- Schedule periodic audits — automated tools catch many issues, but some criteria can only be verified by a human.
How tools like AccessWiser fit in
Automated tools and accessibility widgets can meaningfully accelerate this work. AccessWiser helps by scanning for WCAG issues, applying AI-driven fixes for common failures, and giving visitors adjustable display options — but no tool alone can guarantee full WCAG conformance or legal compliance. Some criteria, like whether alt text is genuinely meaningful or whether a workflow makes sense to a screen reader user, require human judgment. The strongest approach combines automated tooling for speed and coverage with human review of your most important user journeys.
Frequently asked questions
Is WCAG legally required for my website?
WCAG itself is not a law, but the laws that likely apply to you — such as the ADA in the US or the European Accessibility Act in the EU — use WCAG as the benchmark for accessibility. Practically speaking, conforming to WCAG at Level AA is how you demonstrate compliance with those laws.
Which version and level of WCAG should I target?
Target WCAG 2.2 at Level AA for new work. It is the current version, it is backwards compatible with 2.1 and 2.0, and Level AA is the tier referenced by regulators and courts. If a specific law you fall under cites 2.0 or 2.1 AA, meeting 2.2 AA covers it.
What is the difference between Level A, AA, and AAA?
Level A covers the most critical barriers, Level AA adds the requirements most laws expect (like adequate color contrast and visible keyboard focus), and Level AAA is the strictest tier, which is rarely mandated because some AAA criteria cannot be met for all content types. Level AA is the standard target.
Can an accessibility widget make my site WCAG compliant?
Not on its own. Widgets and automated tools can fix or flag many common issues and improve usability quickly, but full conformance also involves things only humans can verify, such as meaningful alt text, logical reading order, and sensible link labels. Use tooling as an accelerator alongside human testing and remediation.
How often should I check my site against WCAG?
Continuously, ideally. Every new page, feature, or redesign can introduce regressions. A practical rhythm is automated scanning on an ongoing basis plus a manual review of key user journeys whenever your site changes significantly, with a fuller audit at least annually.
This article is provided for general information about accessibility regulations and standards. It is not legal advice — consult a qualified professional about your specific compliance obligations.