WCAG Coverage
This page lists every WCAG 2.2 success criterion, a short summary of what it asks for, and how A11y Pulse covers it. For the headline numbers and a comparison with other tools, see WCAG coverage.
Contents:
Summary
Of the 55 success criteria at Level A and AA, A11y Pulse checks 24 automatically today, and plans to check 15 more by the end of 2027. Across all 86 criteria, including Level AAA, we check 25 today.
A checked criterion is not a passed criterion. Many checks only cover part of a criterion, and some criteria can only be judged by a person. Use A11y Pulse alongside thorough manual testing to help you work towards WCAG compliance. See Does passing every audit mean my site is WCAG compliant? for more.
What each status means
- Checked today: at least one A11y Pulse audit tests this criterion. Some of these audits are experimental, and you can switch them on in your site’s settings. See A11y Pulse Audits.
- Partially: our audits test some of the criterion’s requirements, but not all of them.
- Planned: we plan to add an audit for this criterion in the quarter shown. Dates are estimates and may change.
- Automatable, not yet planned: we believe this criterion can be tested automatically, but it isn’t on our roadmap yet.
- Needs AI or human judgment: testing this criterion means judging the quality or meaning of content, which a rule-based check can’t do reliably.
- AI review planned: we plan to add an AI-assisted review in the quarter shown that flags issues for a person to confirm. These criteria still need human judgment, so they don’t count towards the planned total.
- Needs human testing: this criterion can’t be tested automatically.
4.1.1 Parsing is not listed because it was removed in WCAG 2.2.
Perceivable
1.1 Text Alternatives
| Success criterion | Level | Status |
|---|
| 1.1.1 Non-text ContentImages, icons and other non-text content have a text alternative that serves the same purpose. | A | Checked todayChecks that text alternatives exist. Whether they are accurate needs human or AI review. |
|---|
1.2 Time-based Media
1.3 Adaptable
| Success criterion | Level | Status |
|---|
| 1.3.1 Info and RelationshipsStructure and relationships shown visually, like headings, lists, tables and form labels, are also available in code. | A | Checked today |
|---|
| 1.3.2 Meaningful SequenceContent is presented in a meaningful reading order in the code. | A | Needs human testingReading order of static content is a meaning judgment. |
|---|
| 1.3.3 Sensory CharacteristicsInstructions don't rely only on shape, color, size, location or sound. | A | Needs human testingInstructions that rely on shape, size or location need human review. |
|---|
| 1.3.4 OrientationContent works in both portrait and landscape orientation. | AA | Planned for Q2 2027 |
|---|
| 1.3.5 Identify Input PurposeFields that collect personal information identify their purpose, for example with autocomplete. | AA | Checked today |
|---|
| 1.3.6 Identify PurposeThe purpose of interface components, icons and page regions can be identified in code. | AAA | Needs human testing |
|---|
1.4 Distinguishable
| Success criterion | Level | Status |
|---|
| 1.4.1 Use of ColorColor is not the only way information is conveyed. | A | Checked today (partially)Only links distinguished from surrounding text by color alone are checked today. |
|---|
| 1.4.2 Audio ControlAudio that plays automatically for more than three seconds can be paused or muted. | A | Checked today |
|---|
| 1.4.3 Contrast (Minimum)Text has a contrast ratio of at least 4.5:1, or 3:1 for large text. | AA | Checked todayText over images and gradients is reported for review. |
|---|
| 1.4.4 Resize TextText can be resized up to 200% without losing content or functionality. | AA | Checked today (partially)Only checks that zoom is not blocked. Text is never actually resized. |
|---|
| 1.4.5 Images of TextText is used instead of images of text, except where the appearance is essential. | AA | AI review planned for Q3 2027 |
|---|
| 1.4.6 Contrast (Enhanced)Text has a contrast ratio of at least 7:1, or 4.5:1 for large text. | AAA | Automatable, not yet plannedaxe-core's color-contrast-enhanced rule exists but is disabled by default. |
|---|
| 1.4.7 Low or No Background AudioSpeech recordings have little or no background sound, or it can be turned off. | AAA | Needs human testing |
|---|
| 1.4.8 Visual PresentationBlocks of text can be presented with user-chosen colors, limited line width, no justification and comfortable spacing. | AAA | Automatable, not yet planned (partially)Line length, justification and line spacing are measurable. A mechanism to select colors needs human review. |
|---|
| 1.4.9 Images of Text (No Exception)Images of text are only used for decoration or where the appearance is essential. | AAA | Needs AI or human judgment |
|---|
| 1.4.10 ReflowContent reflows at 320 CSS pixels wide without scrolling in two directions. | AA | Checked today |
|---|
| 1.4.11 Non-text ContrastInterface components, focus indicators and meaningful graphics have a contrast ratio of at least 3:1. | AA | Planned for Q1 2027 |
|---|
| 1.4.12 Text SpacingNo content is lost when users increase line, paragraph, letter and word spacing. | AA | Checked today |
|---|
| 1.4.13 Content on Hover or FocusContent that appears on hover or focus can be dismissed, can be hovered, and stays visible until dismissed. | AA | Planned for Q2 2027 |
|---|
Operable
2.1 Keyboard Accessible
| Success criterion | Level | Status |
|---|
| 2.1.1 KeyboardAll functionality can be used with a keyboard. | A | Checked today (partially)Only iframes, scrollable regions and server-side image maps are checked today. |
|---|
| 2.1.2 No Keyboard TrapKeyboard focus never gets trapped in a component. | A | Planned for Q4 2026 |
|---|
| 2.1.3 Keyboard (No Exception)All functionality can be used with a keyboard, without exception. | AAA | Checked today (partially)Only scrollable regions are checked today. |
|---|
| 2.1.4 Character Key ShortcutsSingle-character keyboard shortcuts can be turned off, remapped, or only work on focus. | A | Needs human testingWhether a shortcut can be turned off or remapped needs human review. |
|---|
2.2 Enough Time
| Success criterion | Level | Status |
|---|
| 2.2.1 Timing AdjustableUsers can turn off, adjust or extend time limits. | A | Checked today (partially)Only meta refresh timers are checked. Script-driven time limits need human review. |
|---|
| 2.2.2 Pause, Stop, HideMoving, blinking, scrolling or auto-updating content can be paused, stopped or hidden. | A | Checked today (partially)Only blink and marquee elements are checked. Carousels and animations need human review. |
|---|
| 2.2.3 No TimingTiming is not an essential part of the content or activity. | AAA | Needs human testing |
|---|
| 2.2.4 InterruptionsInterruptions, such as updates and alerts, can be postponed or suppressed. | AAA | Automatable, not yet planned (partially)axe-core's meta-refresh-no-exceptions rule exists but is disabled by default. |
|---|
| 2.2.5 Re-authenticatingUsers can continue where they left off without losing data after re-authenticating. | AAA | Needs human testing |
|---|
| 2.2.6 TimeoutsUsers are warned about inactivity timeouts that could cause data loss. | AAA | Needs human testing |
|---|
2.3 Seizures and Physical Reactions
2.4 Navigable
| Success criterion | Level | Status |
|---|
| 2.4.1 Bypass BlocksA mechanism, such as a skip link, lets users bypass blocks of repeated content. | A | Checked today |
|---|
| 2.4.2 Page TitledPages have titles that describe their topic or purpose. | A | Checked today |
|---|
| 2.4.3 Focus OrderFocus moves through the page in an order that preserves meaning and operability. | A | Planned for Q4 2026 (partially)Findings are review signals. Whether an order preserves meaning needs human review. |
|---|
| 2.4.4 Link Purpose (In Context)The purpose of each link is clear from its text or its context. | A | Checked today |
|---|
| 2.4.5 Multiple WaysThere is more than one way to find a page within a site, such as navigation, search or a sitemap. | AA | Planned for Q3 2027Compares pages across your site. |
|---|
| 2.4.6 Headings and LabelsHeadings and labels describe their topic or purpose. | AA | Planned for Q4 2026 (partially)Catches names that are code or placeholders. Whether a fluent name is descriptive needs human or AI review. |
|---|
| 2.4.7 Focus VisibleKeyboard focus is visible. | AA | Checked today |
|---|
| 2.4.8 LocationUsers can tell where they are within a set of pages. | AAA | Planned for Q4 2026 (partially)Checks that the current page is marked in navigation. |
|---|
| 2.4.9 Link Purpose (Link Only)The purpose of each link is clear from its text alone. | AAA | Planned for Q4 2026 (partially)Flags generic link text. axe-core's identical-links-same-purpose rule is disabled by default. |
|---|
| 2.4.10 Section HeadingsSection headings are used to organize content. | AAA | Needs AI or human judgment |
|---|
| 2.4.11 Focus Not Obscured (Minimum)A focused element is not entirely hidden by other content, like sticky headers or banners. | AA | Checked today |
|---|
| 2.4.12 Focus Not Obscured (Enhanced)No part of a focused element is hidden by other content. | AAA | Automatable, not yet plannedThe focus-not-obscured audit could also report partially obscured focus. |
|---|
| 2.4.13 Focus AppearanceFocus indicators are large enough and have enough contrast to be clearly visible. | AAA | Planned for Q1 2027 |
|---|
2.5 Input Modalities
| Success criterion | Level | Status |
|---|
| 2.5.1 Pointer GesturesAnything that uses a multipoint or path-based gesture can also be done with a single pointer. | A | Needs human testing |
|---|
| 2.5.2 Pointer CancellationSingle-pointer actions can be canceled or undone, for example by completing them on the up-event. | A | Needs human testing |
|---|
| 2.5.3 Label in NameA component's accessible name contains the text of its visible label. | A | Planned for Q4 2026 |
|---|
| 2.5.4 Motion ActuationAnything triggered by device motion can also be done with the interface, and motion can be turned off. | A | Needs human testing |
|---|
| 2.5.5 Target Size (Enhanced)Pointer targets are at least 44 by 44 CSS pixels. | AAA | Automatable, not yet plannedTarget bounding boxes are measurable. |
|---|
| 2.5.6 Concurrent Input MechanismsContent doesn't restrict the input methods, like touch, mouse or keyboard, that users can switch between. | AAA | Needs human testing |
|---|
| 2.5.7 Dragging MovementsAnything that uses dragging can also be done with a single pointer without dragging. | AA | Planned for Q1 2027 |
|---|
| 2.5.8 Target Size (Minimum)Pointer targets are at least 24 by 24 CSS pixels, or have enough space around them. | AA | Checked today |
|---|
Understandable
3.1 Readable
| Success criterion | Level | Status |
|---|
| 3.1.1 Language of PageThe default language of each page is identified in code. | A | Checked today |
|---|
| 3.1.2 Language of PartsChanges of language within a page are identified in code. | AA | Checked today (partially)Only validates lang attribute values. |
|---|
| 3.1.3 Unusual WordsUnusual words, idioms and jargon are defined. | AAA | Needs AI or human judgment |
|---|
| 3.1.4 AbbreviationsThe expanded form or meaning of abbreviations is available. | AAA | Needs AI or human judgment |
|---|
| 3.1.5 Reading LevelContent that needs more than a lower secondary reading level has a simpler alternative. | AAA | Needs AI or human judgment |
|---|
| 3.1.6 PronunciationThe pronunciation of ambiguous words is available. | AAA | Needs human testing |
|---|
3.2 Predictable
| Success criterion | Level | Status |
|---|
| 3.2.1 On FocusFocusing an element doesn't cause an unexpected change of context. | A | Checked today |
|---|
| 3.2.2 On InputChanging a form control's value doesn't cause an unexpected change of context. | A | Planned for Q2 2027 |
|---|
| 3.2.3 Consistent NavigationRepeated navigation appears in the same relative order on each page. | AA | Planned for Q2 2027Compares pages across your site. |
|---|
| 3.2.4 Consistent IdentificationComponents with the same function are identified consistently across pages. | AA | Planned for Q2 2027Compares pages across your site. |
|---|
| 3.2.5 Change on RequestChanges of context only happen when the user requests them. | AAA | Automatable, not yet planned (partially)axe-core's meta-refresh-no-exceptions rule exists but is disabled by default. |
|---|
| 3.2.6 Consistent HelpHelp mechanisms, like contact details or chat, appear in the same relative order on each page. | A | Planned for Q3 2027Compares pages across your site. |
|---|
3.3 Input Assistance
| Success criterion | Level | Status |
|---|
| 3.3.1 Error IdentificationInput errors are identified and described to the user in text. | A | Needs AI or human judgmentChecking error messages means submitting forms, which a scan must never do on a live site. |
|---|
| 3.3.2 Labels or InstructionsForm fields have labels or instructions. | A | Checked today (partially)Only fields with more than one label are checked today. Whether instructions are clear needs human review. |
|---|
| 3.3.3 Error SuggestionWhen an input error is detected, suggestions for fixing it are provided. | AA | Needs AI or human judgmentChecking error suggestions means submitting forms, which a scan must never do on a live site. |
|---|
| 3.3.4 Error Prevention (Legal, Financial, Data)Legal, financial and data submissions can be reversed, checked or confirmed. | AA | Needs human testing |
|---|
| 3.3.5 HelpContext-sensitive help is available. | AAA | Needs human testing |
|---|
| 3.3.6 Error Prevention (All)All form submissions can be reversed, checked or confirmed. | AAA | Needs human testing |
|---|
| 3.3.7 Redundant EntryInformation the user has already entered in a process is filled in or available to select. | A | Needs human testing |
|---|
| 3.3.8 Accessible Authentication (Minimum)Logging in doesn't require a cognitive test, like remembering a password, without an alternative or assistance. | AA | AI review planned for Q3 2027 |
|---|
| 3.3.9 Accessible Authentication (Enhanced)Logging in doesn't require any cognitive test, including recognizing objects or personal content. | AAA | Needs AI or human judgment |
|---|
Robust
4.1 Compatible
| Success criterion | Level | Status |
|---|
| 4.1.2 Name, Role, ValueInterface components have a name, role and state that assistive technologies can read. | A | Checked today |
|---|
| 4.1.3 Status MessagesStatus messages are announced by assistive technologies without receiving focus. | AA | Planned for Q2 2027 |
|---|