WCAG Version Comparison Tool
Use this guided checker to choose a WCAG target, mark what your site passes or misses, and export a clear gap report for your team.
Start here
What this tool is for
This tool helps a business answer three practical questions: which WCAG version should we target, what changed between WCAG 2.1 and 2.2, and which items are still open before we can make a responsible accessibility claim.
Recommended default
For most business sites, start with WCAG 2.2 Level AA. Use WCAG 2.1 only when a contract or regulation specifically names it.
- 1
Pick your target
Choose region, site type, WCAG version, and level.
- 2
Add evidence
Paste HTML or scan a URL to pre-fill obvious checks.
- 3
Close the gaps
Mark pass/fail/unknown and export a report.
Step 1: Choose the standard to check
These choices control the checklist below. WCAG 3.0 is not selectable because it is still a draft, but a readiness preview appears later on the page.
Recommended target: WCAG 2.2 AA for business risk reduction
US businesses often use WCAG AA as the practical benchmark for ADA accessibility programs even where exact obligations depend on context. WCAG 2.2 AA covers newer mobile, focus, target-size, and authentication risks.
Step 2: Add evidence from a page
This step is optional, but useful. Paste HTML or try a URL and the tool will generate a first-pass result from obvious signals such as page title, language, image alt attributes, labels, landmarks, captions, and focus risks.
Generated result
This is the main outcome of the tool. It tells you what the pasted page clearly passes, what clearly needs work, and what still needs manual testing.
Add HTML or scan a URL in Step 2 to generate page-based hints. You can still use the checklist manually without page source.
Step 3: Review or adjust the result
Most people only need to review the failed and unknown items below. Use Pass only when you have evidence. Use Fail for confirmed gaps. Leave Unknown when the item still needs testing.
55 criteria shown
| Criterion | Version | Level | Status | What to check | Source |
|---|---|---|---|---|---|
1.1.1 Non-text Content Perceivable | WCAG 2.0 | Level A | All non-text content has a text alternative that serves an equivalent purpose. | W3C | |
1.2.1 Audio-only and Video-only (Prerecorded) Perceivable | WCAG 2.0 | Level A | Provide alternatives for prerecorded audio-only and video-only media. | W3C | |
1.2.2 Captions (Prerecorded) Perceivable | WCAG 2.0 | Level A | Captions are provided for prerecorded audio content in synchronized media. | W3C | |
1.2.3 Audio Description or Media Alternative Perceivable | WCAG 2.0 | Level A | Alternative for prerecorded video content in synchronized media. | W3C | |
1.2.4 Captions (Live) Perceivable | WCAG 2.0 | Level AA | Captions are provided for all live audio content in synchronized media. | W3C | |
1.2.5 Audio Description (Prerecorded) Perceivable | WCAG 2.0 | Level AA | Audio description is provided for all prerecorded video content. | W3C | |
1.3.1 Info and Relationships Perceivable | WCAG 2.0 | Level A | Structure and relationships conveyed through presentation can be programmatically determined. | W3C | |
1.3.2 Meaningful Sequence Perceivable | WCAG 2.0 | Level A | The reading sequence can be programmatically determined. | W3C | |
1.3.3 Sensory Characteristics Perceivable | WCAG 2.0 | Level A | Instructions don't rely solely on shape, color, size, location, or sound. | W3C | |
1.3.4 Orientation Perceivable | WCAG 2.1 | Level AA | Content is not restricted to a single display orientation. | W3C | |
1.3.5 Identify Input Purpose Perceivable | WCAG 2.1 | Level AA | The purpose of common input fields can be programmatically determined via autocomplete. | W3C | |
1.4.1 Use of Color Perceivable | WCAG 2.0 | Level A | Color is not the only means of conveying information. | W3C | |
1.4.2 Audio Control Perceivable | WCAG 2.0 | Level A | Audio that plays for more than 3 seconds can be paused. | W3C | |
1.4.3 Contrast (Minimum) Perceivable | WCAG 2.0 | Level AA | Text has a contrast ratio of at least 4.5:1 (3:1 for large text). | W3C | |
1.4.4 Resize Text Perceivable | WCAG 2.0 | Level AA | Text can be resized up to 200% without loss of content or functionality. | W3C | |
1.4.5 Images of Text Perceivable | WCAG 2.0 | Level AA | Use text instead of images of text where possible. | W3C | |
1.4.10 Reflow Perceivable | WCAG 2.1 | Level AA | Content reflows to a single column at 320 CSS pixels without loss. | W3C | |
1.4.11 Non-text Contrast Perceivable | WCAG 2.1 | Level AA | UI components and graphical objects have at least 3:1 contrast. | W3C | |
1.4.12 Text Spacing Perceivable | WCAG 2.1 | Level AA | No loss of content when users override text spacing. | W3C | |
1.4.13 Content on Hover or Focus Perceivable | WCAG 2.1 | Level AA | Additional content triggered on hover/focus is dismissible, hoverable, and persistent. | W3C | |
2.1.1 Keyboard Operable | WCAG 2.0 | Level A | All functionality is available from a keyboard. | W3C | |
2.1.2 No Keyboard Trap Operable | WCAG 2.0 | Level A | Keyboard focus can move away from any component. | W3C | |
2.1.4 Character Key Shortcuts Operable | WCAG 2.1 | Level A | Single-character shortcuts can be turned off, remapped, or only active on focus. | W3C | |
2.2.1 Timing Adjustable Operable | WCAG 2.0 | Level A | Users can turn off, adjust, or extend time limits. | W3C | |
2.2.2 Pause, Stop, Hide Operable | WCAG 2.0 | Level A | Moving, blinking, scrolling, or auto-updating content can be paused. | W3C | |
2.3.1 Three Flashes or Below Threshold Operable | WCAG 2.0 | Level A | No content flashes more than 3 times per second. | W3C | |
2.4.1 Bypass Blocks Operable | WCAG 2.0 | Level A | A mechanism (skip link, landmarks) bypasses repeated content. | W3C | |
2.4.2 Page Titled Operable | WCAG 2.0 | Level A | Pages have titles that describe topic or purpose. | W3C | |
2.4.3 Focus Order Operable | WCAG 2.0 | Level A | Focus order preserves meaning and operability. | W3C | |
2.4.4 Link Purpose (In Context) Operable | WCAG 2.0 | Level A | The purpose of each link can be determined from the link text alone or context. | W3C | |
2.4.5 Multiple Ways Operable | WCAG 2.0 | Level AA | More than one way is available to locate a page. | W3C | |
2.4.6 Headings and Labels Operable | WCAG 2.0 | Level AA | Headings and labels describe topic or purpose. | W3C | |
2.4.7 Focus Visible Operable | WCAG 2.0 | Level AA | Keyboard focus indicator is visible. | W3C | |
2.4.11 Focus Not Obscured (Minimum) Operable | WCAG 2.2 | Level AA | Focused element is not entirely hidden by author-created content. | W3C | |
2.5.1 Pointer Gestures Operable | WCAG 2.1 | Level A | Multipoint or path-based gestures have single-point alternatives. | W3C | |
2.5.2 Pointer Cancellation Operable | WCAG 2.1 | Level A | Users can abort or undo pointer activations. | W3C | |
2.5.3 Label in Name Operable | WCAG 2.1 | Level A | Accessible name contains the visible label text. | W3C | |
2.5.4 Motion Actuation Operable | WCAG 2.1 | Level A | Motion-triggered functions have UI alternatives and can be disabled. | W3C | |
2.5.7 Dragging Movements Operable | WCAG 2.2 | Level AA | Dragging functions have single-pointer alternatives. | W3C | |
2.5.8 Target Size (Minimum) Operable | WCAG 2.2 | Level AA | Touch targets are at least 24 by 24 CSS pixels. | W3C | |
3.1.1 Language of Page Understandable | WCAG 2.0 | Level A | Default language of the page can be programmatically determined. | W3C | |
3.1.2 Language of Parts Understandable | WCAG 2.0 | Level AA | Language of each passage can be programmatically determined. | W3C | |
3.2.1 On Focus Understandable | WCAG 2.0 | Level A | Receiving focus does not trigger a change of context. | W3C | |
3.2.2 On Input Understandable | WCAG 2.0 | Level A | Changing a setting does not automatically change context. | W3C | |
3.2.3 Consistent Navigation Understandable | WCAG 2.0 | Level AA | Navigation repeated on multiple pages is in the same order. | W3C | |
3.2.4 Consistent Identification Understandable | WCAG 2.0 | Level AA | Components with the same function are identified consistently. | W3C | |
3.2.6 Consistent Help Understandable | WCAG 2.2 | Level A | Help mechanisms are provided in the same relative order across pages. | W3C | |
3.3.1 Error Identification Understandable | WCAG 2.0 | Level A | Input errors are identified and described to the user. | W3C | |
3.3.2 Labels or Instructions Understandable | WCAG 2.0 | Level A | Labels or instructions are provided when content requires user input. | W3C | |
3.3.3 Error Suggestion Understandable | WCAG 2.0 | Level AA | If input errors are detected, suggestions for correction are provided. | W3C | |
3.3.4 Error Prevention (Legal, Financial, Data) Understandable | WCAG 2.0 | Level AA | For sensitive submissions, users can review, correct, or reverse. | W3C | |
3.3.7 Redundant Entry Understandable | WCAG 2.2 | Level A | Information previously entered is auto-populated or available. | W3C | |
3.3.8 Accessible Authentication (Minimum) Understandable | WCAG 2.2 | Level AA | No cognitive function test is required for authentication. | W3C | |
4.1.2 Name, Role, Value Robust | WCAG 2.0 | Level A | Name, role, and state of UI components are programmatically determinable. | W3C | |
4.1.3 Status Messages Robust | WCAG 2.1 | Level AA | Status messages can be programmatically determined via role/aria-live. | W3C |
WCAG 2.1 vs 2.2 differences
Use this panel when someone asks, "What changed?" WCAG 2.2 keeps the WCAG 2.1 baseline and adds these Level A/AA checks that affect focus, touch targets, help placement, repeated entry, dragging, and authentication.
- 2.4.11 Focus Not Obscured (Minimum)Level AA
Focused element is not entirely hidden by author-created content.
- 2.5.7 Dragging MovementsLevel AA
Dragging functions have single-pointer alternatives.
- 2.5.8 Target Size (Minimum)Level AA
Touch targets are at least 24 by 24 CSS pixels.
- 3.2.6 Consistent HelpLevel A
Help mechanisms are provided in the same relative order across pages.
- 3.3.7 Redundant EntryLevel A
Information previously entered is auto-populated or available.
- 3.3.8 Accessible Authentication (Minimum)Level AA
No cognitive function test is required for authentication.
4.1.1 Parsing (Obsolete in 2.2) is obsolete and removed from WCAG 2.2, though older policies may still ask about it.
WCAG 3.0 future-readiness preview
Do not use WCAG 3.0 for a compliance claim today. It is still an in-progress Working Draft. This preview only shows whether your WCAG 2.x evidence supports themes that are likely to remain important.
Text alternatives and media
DevelopingWCAG 3 drafts continue the need for alternatives for images, audio, video, and non-text content.
Evidence: Alt text, captions, transcripts, and audio description coverage.
Mapped criteria: 0 pass, 0 fail, 3 unknown
Clear structure and navigation
DevelopingDraft direction keeps strong emphasis on meaningful structure, labels, headings, and navigation.
Evidence: Semantic landmarks, headings, labels, tables, reading order, and page titles.
Mapped criteria: 0 pass, 0 fail, 3 unknown
Keyboard and pointer interaction
DevelopingInteractive flows should remain operable across keyboard, pointer, touch, and alternate input.
Evidence: Keyboard-only completion, no traps, alternatives to drag gestures, and adequate target size.
Mapped criteria: 0 pass, 0 fail, 4 unknown
Usability and cognitive access
ExploratoryWCAG 3 work explores more measurable support for cognitive and learning accessibility.
Evidence: Consistent help, reduced redundant entry, and authentication without memory puzzles.
Mapped criteria: 0 pass, 0 fail, 3 unknown
Robust code and assistive technology support
DevelopingAccessible names, roles, values, state changes, and status messages remain central.
Evidence: Screen-reader checks, accessible names, roles, live regions, and custom widget testing.
Mapped criteria: 0 pass, 0 fail, 2 unknown
Editorial guidance
How this compliance tool supports accessibility work
The wcag version comparison tool is designed to turn a common accessibility review task into a repeatable workflow. It focuses on compare wcag 2.1, wcag 2.2, and wcag 3.0 draft direction, then track which criteria a site meets, misses, or still needs to test. The goal is not to replace expert judgment, but to make the first review faster, more consistent, and easier to explain to designers, developers, QA teams, and content owners.
Use the output as evidence for a remediation conversation. A failed check normally means the implementation needs a closer look against WCAG 1.1.1, 1.3.1, 2.1.1, 2.4.7, 3.3.8, 4.1.2, while a passing check means the specific automated rule did not find a problem. Passing automated checks is helpful, but it is not the same as a full conformance claim.
For best results, test real production markup instead of simplified snippets. Templates, CSS state, JavaScript behavior, responsive layouts, and content changes can all affect the final accessibility experience. Re-run the tool after fixes so the before-and-after evidence is easy to compare.
Pair this tool with manual keyboard testing, zoom and reflow checks, screen-reader review, and content judgment. Those human checks catch issues that automated logic cannot reliably infer, such as whether labels are meaningful, instructions are clear, or a complete user task can be finished without a mouse.
How to use
- 1Open the wcag version comparison tool and enter the page content, settings, or code you want to test or generate.
- 2Review the result cards, scores, or generated code to identify the safest accessible option before implementation.
- 3Copy the recommended fix or starter markup, then validate it again in your real product with keyboard and assistive technology testing.
FAQs
Tips here are tailored for the wcag version comparison tool so people can move from checking to fixing faster.
What to verify manually
Keyboard: move through the related flow with Tab, Shift+Tab, Enter, Space, Escape, and arrow keys where the pattern expects them.
Assistive technology: check names, roles, states, reading order, announcements, and focus changes with at least one screen reader.
Content quality: confirm that instructions, labels, headings, errors, and alternatives make sense in the real user task.
This page is written as practical guidance, not a legal certification. For procurement, VPAT/ACR work, or regulated launches, combine tool output with expert review and documented manual test results.
Related learning