WCAG vs. Remediation: What's the Difference?

"WCAG vs. remediation" is one of the most common search phrases in accessibility — and it is a bit of a category error, because the two are not alternatives. WCAG is the standard you are measured against. Remediation is the work of fixing your site so it meets that standard. You do not choose one or the other; you use WCAG to define "done" and remediation to get there.

This guide untangles the vocabulary — WCAG, audit, remediation, conformance, and monitoring — so you can scope the right project and brief an agency without ambiguity.

What WCAG is

WCAG stands for the Web Content Accessibility Guidelines, the technical standard published by the World Wide Web Consortium (W3C) through its Web Accessibility Initiative. The current version is WCAG 2.2, organized around four principles — content must be Perceivable, Operable, Understandable, and Robust (POUR) — and three conformance levels: A, AA, and AAA. Most legal and contractual obligations target Level AA.

WCAG is not a law. It is the yardstick that laws point to. The U.S. Department of Justice treats WCAG as the practical measure of whether a website meets the Americans with Disabilities Act, and Section 508 formally adopts WCAG as its baseline for federal technology. For the W3C's own plain-language overview, see the authoritative sources at the end of this guide.

What remediation is

Remediation is the process of fixing an existing website so it conforms to WCAG. It is the hands-on engineering and content work: correcting heading structure and landmarks, adding text alternatives, fixing color contrast, making every control keyboard-operable, labeling forms, taming focus order, and repairing ARIA. Remediation is what you do *after* you know what is broken.

If WCAG is the test, remediation is the studying and the corrections. You can read more on our WCAG remediation service overview and the line-by-line WCAG 2.2 checklist.

Where audits and monitoring fit

Most real engagements have three phases, and the words are often used loosely. Here is the precise sequence:

1. Audit — A WCAG audit measures your current site against the standard and produces a prioritized list of issues mapped to specific success criteria. A credible audit is *manual* — real keyboard and screen-reader testing with JAWS, NVDA, and VoiceOver — not an automated-only scan. Automated tools catch roughly 30–40% of issues; the rest require human judgment.

2. Remediation — Developers and content authors fix the issues the audit found, ideally retesting each fix.

3. Monitoring — Because new content and features can reintroduce barriers, ongoing monitoring re-validates the site over time so conformance does not silently regress.

A quick glossary

WCAG — The Web Content Accessibility Guidelines; the W3C technical standard (current: 2.2) with levels A, AA, AAA. The "what."

Conformance — A formal claim that a page or site meets a specific WCAG level. "WCAG 2.2 AA conformant" is the typical target.

Audit / assessment — Manual + automated evaluation that finds and documents issues against WCAG.

Remediation — The corrective work that brings a non-conformant site into conformance.

VPAT / ACR — A document reporting conformance, required for federal and many enterprise procurements. See our Section 508 hub.

Overlay — A third-party widget that claims instant compliance. It does not produce conformance and is excluded from this directory.

So which do you need?

If you have an existing website that has never been evaluated, you need an audit first, then remediation of what it finds, then monitoring to hold the line. If you are building something new, bake WCAG in from design rather than remediating later — it is cheaper and more durable. Either way, WCAG is always the standard; remediation is simply the work. Compare vetted, manual-testing WCAG remediation agencies that never use overlays.