What does WCAG compliance mean?
WCAG compliance (the W3C's own term is conformance) means that a page satisfies every applicable success criterion of the Web Content Accessibility Guidelines at a stated level. The criteria are pass-or-fail statements - "text has a contrast ratio of at least 4.5:1", "all functionality is operable through a keyboard" - so compliance is testable, not a matter of opinion.
Three things follow from that definition, and they surprise people:
- Compliance belongs to pages, not products. A platform, theme or plugin cannot be "WCAG compliant" on your behalf; the delivered page, with your content and code, is what passes or fails.
- It is all-or-nothing per level. One failing criterion on the page means the page does not conform at that level. There is no 92% compliant.
- It moves. Every release, new banner or embedded widget can break a criterion that passed last month, which is why one-time fixes decay without monitoring.
What does WCAG stand for?
WCAG stands for Web Content Accessibility Guidelines. It is published by the World Wide Web Consortium (W3C) through its Web Accessibility Initiative (WAI), and it is the technical standard that nearly every digital accessibility law and contract points to. The current versions in use are WCAG 2.1 (2018) and WCAG 2.2 (2023); each new version contains the previous one, so meeting 2.2 also means meeting 2.1 and 2.0.
WCAG compliant at which level? A, AA or AAA
Every success criterion carries a level, and the levels are cumulative:
| Level | What it represents | Who requires it |
|---|---|---|
| A | The minimum. Failures here lock some users out entirely. | Included in every AA requirement |
| AA | The working standard: contrast, keyboard, captions, reflow, labels, focus. | EN 301 549, the EAA, the ADA Title II rule, AODA, Section 508 - and most contracts |
| AAA | Enhanced provisions such as 7:1 contrast and sign language. | Specific content only; the W3C advises against site-wide AAA policies |
How to make a website WCAG compliant
The path is the same whether you run a five-page site or an enterprise platform; only the scale changes.
- Baseline scan. Run an automated audit across your templates to surface the machine-detectable failures - missing alt text, contrast, unlabeled fields, broken ARIA. A free page-level scan takes seconds with an accessibility checker; a full-site picture comes from a crawler.
- Manual audit. Roughly two thirds of WCAG criteria need human judgement: keyboard-only walkthroughs, screen reader testing, checking that alt text is meaningful and error messages actually help. This is where certified auditors earn their keep.
- Remediate at the source. Fix templates and components, not individual pages - one corrected component can close hundreds of page-level failures. Automated remediation can resolve a large share of the common issue patterns; the remainder is code and content work.
- Document. Record what was tested, what passed and what was fixed. For B2B sales and public-sector work this becomes an Accessibility Conformance Report (VPAT); for everyone it is the evidence that stands behind an accessibility statement.
- Monitor. Sites change weekly; compliance decays silently. Continuous monitoring catches regressions before they accumulate - or before someone else finds them.
The most common WCAG violations
Year after year, large-scale scans of the web find the same handful of failures dominating. If you fix only these six, you eliminate the majority of barriers users actually hit:
- Low-contrast text (1.4.3) - the single most common failure on the web
- Images with missing or useless alternative text (1.1.1)
- Form inputs without programmatic labels (1.3.1, 4.1.2)
- Empty links and buttons that announce nothing to a screen reader (2.4.4)
- Functionality that cannot be reached or operated by keyboard (2.1.1)
- Missing document language (3.1.1)
WCAG compliance software vs services
Tooling and human services answer different parts of the problem, and mature programs use both:
| Compliance software | Compliance services | |
|---|---|---|
| What it covers | Automated detection and automated fixes for the machine-detectable share of issues; continuous scanning | Manual audits, remediation of code and content, legal-grade documentation, expert judgement |
| Speed | Minutes to first results | Days to weeks for a full audit cycle |
| Limit | Cannot judge meaning, context or task flow - no tool alone makes a site compliant | Point-in-time unless paired with monitoring |
| Fits | Ongoing hygiene and regression-catching at scale | Reaching conformance, proving it, and high-risk pages |
Is WCAG compliance a legal requirement?
WCAG itself is a standard, not a statute - but the laws that matter reference it directly. EN 301 549 and the European Accessibility Act (in force since 28 June 2025) bind it into EU law at Level AA. In the US, the Department of Justice's ADA Title II rule sets WCAG 2.1 AA for state and local government, with compliance dates of 26 April 2027 and 26 April 2028 by entity size - and for private businesses, plaintiffs' firms treat WCAG AA as the de facto benchmark, with more than 5,000 US lawsuits filed in 2025.
Frequently asked questions
What is WCAG compliance?
Meeting every success criterion of the Web Content Accessibility Guidelines at a declared level - in practice Level AA of WCAG 2.1 or 2.2 - on your pages as actually delivered to users.
What does WCAG stand for?
Web Content Accessibility Guidelines - a standard published by the W3C's Web Accessibility Initiative.
What does "WCAG compliant" mean for a website?
That the site's pages pass all 50 Level A and AA success criteria: sufficient contrast, full keyboard operation, captions, labeled forms, reflow at mobile widths, visible focus, and the rest. One failing criterion means the page does not conform.
Can software alone make my site WCAG compliant?
No. Automation reliably finds and fixes only the machine-detectable share of issues - roughly a third of the criteria. The remainder requires human testing and remediation. The effective model combines both.
How long does it take to become WCAG compliant?
A typical mid-size site takes weeks, not days: baseline scan, manual audit, remediation sprints, verification and documentation. Managed programs compress this by running audit and remediation in parallel.
Which WCAG level is legally required?
Level AA. EN 301 549, the European Accessibility Act, the ADA Title II rule, AODA and Section 508 all reference Level AA of WCAG 2.0 or 2.1.
- W3C, Understanding Conformance - WCAG 2.1 - w3.org
- W3C WAI, WCAG 2 Overview - w3.org/WAI
- US Department of Justice, ADA Title II web and mobile accessibility rule - ada.gov
- European Commission, European Accessibility Act - eur-lex.europa.eu
Last updated . Reviewed by the EqualWeb accessibility team.
Get a criterion-by-criterion compliance picture
Certified IAAP/CPWA specialists audit your site against WCAG Level AA, fix what fails, and hand you the documentation that proves it. Free accessibility checks included, no credit card required.