◆ accessibility compliance
WCAG compliance, explained without the standards-speak
WCAG — the Web Content Accessibility Guidelines — is the standard regulators, courts and enterprise procurement teams use to decide whether a website is accessible. This page covers what level AA actually asks for, what WCAG 2.2 added, and how to produce an audit record you can hand to a client or a lawyer.
◆ audit checklist
WCAG 2.2 accessibility audit
Generated around your framework, page types, media, forms and target conformance level — every applicable success criterion with a test method and a pass/fail column.
The four WCAG principles
Perceivable
Text alternatives for images, captions and transcripts for media, 4.5:1 contrast on body text, and content that survives 200% zoom or a 320px viewport.
Operable
Every control reachable and usable by keyboard, no traps, visible focus, skip links, generous timing, and 24×24 CSS pixel minimum target size (new in 2.2).
Understandable
Declared page language, predictable navigation, labelled inputs, clear error identification and suggestions, and consistent help placement (new in 2.2).
Robust
Valid name, role and value for every custom widget, correct ARIA usage, and status messages announced to assistive technology without stealing focus.
What WCAG 2.2 added
WCAG 2.2 is backwards compatible with 2.1. If you already conform at 2.1 AA, these are the criteria left to check.
- 2.4.11 / 2.4.12 Focus Not Obscured
- Focused elements must not be hidden behind sticky headers, cookie bars or chat widgets.
- 2.4.13 Focus Appearance (AAA)
- Focus indicators need a defined minimum area and contrast.
- 2.5.7 Dragging Movements
- Anything draggable needs a single-pointer alternative.
- 2.5.8 Target Size (Minimum)
- Interactive targets must be at least 24×24 CSS pixels, or spaced equivalently.
- 3.2.6 Consistent Help
- Help links, phone numbers and chat entry points stay in the same relative place.
- 3.3.7 Redundant Entry
- Do not ask a user to re-enter information they already gave in the same session.
- 3.3.8 Accessible Authentication
- No cognitive function tests (puzzles, transcription) without an alternative.
How to run a WCAG audit
- 01
Pick the conformance target (almost always 2.2 AA) and list the page types in scope: landing, auth, forms, checkout, dashboard.
- 02
Run automated tooling on each page type to clear contrast, labels, landmarks and duplicate IDs.
- 03
Do a keyboard-only pass: tab order, visible focus, no traps, skip link, modals returning focus.
- 04
Do a screen reader pass (VoiceOver or NVDA) on the same flows, checking names, roles, states and status messages.
- 05
Test zoom to 200% and a 320px viewport for reflow, plus target size and spacing on touch.
- 06
Record every criterion as pass, fail or not applicable with evidence, then publish an accessibility statement citing the result and remediation dates.
WCAG compliance FAQ
- What is WCAG compliance?
- WCAG compliance means a website meets the Web Content Accessibility Guidelines published by the W3C. Conformance is measured at level A, AA or AAA against four principles: content must be perceivable, operable, understandable and robust. AA is the level referenced by most laws and procurement contracts.
- What is the difference between WCAG 2.1 and WCAG 2.2?
- WCAG 2.2 (published October 2023) keeps everything in 2.1 and adds nine success criteria covering focus appearance, dragging alternatives, minimum target size, consistent help, redundant entry and accessible authentication. One 2.1 criterion, 4.1.1 Parsing, was made obsolete. If you already meet 2.1 AA, 2.2 AA is a short list of additions rather than a rewrite.
- Is WCAG legally required?
- It depends on where you operate. In the United States, ADA Title II regulations adopted in 2024 require WCAG 2.1 AA for state and local government web content, and Section 508 applies WCAG 2.0 AA to federal agencies and their vendors. In the EU, the European Accessibility Act and EN 301 549 reference WCAG AA. Private US businesses are frequently sued under the ADA using WCAG as the yardstick, so AA is the practical standard.
- Which WCAG level should I target?
- AA. Level A alone leaves obvious barriers in place, and AAA includes criteria (such as sign language for all video) that most teams cannot meet across a whole site. Regulations and contracts almost always specify AA.
- How do I run a WCAG audit?
- Start with automated tooling to catch contrast, labels and landmark issues, then manually test keyboard-only navigation, focus order, form errors, zoom to 200%, and a screen reader pass with VoiceOver or NVDA. Record each success criterion with a pass, fail or not-applicable verdict plus evidence — that record is what an accessibility statement or a legal response is built from.
- How much does the WCAG audit checklist cost?
- The WCAG 2.2 accessibility audit checklist is $2.95 as a one-time purchase, generated around your framework, page types and target conformance level.
Related compliance documents
Email marketing compliance checklist
CAN-SPAM, GDPR, PECR, CASL — mapped to your audience & stack.
Paid ads policy checklist
Meta, Google, TikTok ad policy + jurisdictional disclaimers.
Cookie consent checklist
GDPR + ePrivacy + CCPA-aware banner spec for your stack.
GDPR readiness checklist
Lawful basis, consent, DSARs, retention, processors — audit-ready list.
Employee Onboarding Checklist
Day-one to day-90 onboarding and compliance checklist for a new hire.
Beneficial Ownership (FinCEN BOI) Worksheet
Work out whether your new entity is a reporting company and prepare every data point FinCEN asks for.
⚖ Not legal advice — The Doc Rocket is a self-service document generation platform. We are not a law firm, we do not provide legal representation, legal advice or attorney services, and no attorney-client relationship is created by using this site. Templates are provided for your own review; consult a licensed attorney in your jurisdiction for advice on your specific situation.