Each WCAG 2.2 success criterion beside the provisions in the current WCAG 3 draft that succeed it, with both texts quoted so you can compare them directly.
87WCAG 2.2 Criteria
86Mapped WCAG 3 Provisions
62With a Successor
9No Provision in Draft
💡
How to Read the Evolution Matrix
Column 1 shows the WCAG 2.2 criterion: its level, the bare minimum it requires, and the usability gap that remains.
Column 2 quotes the WCAG 3 draft provision(s) that succeed it, from the editor's draft at the tracked commit.
Column 3 gives the mapping status and any related provisions. The mapping is this site's reviewed interpretation; W3C has not published one.
🔍
Level:
Mapping:
Showing 87 of 87 criteria
🔎
No matching criteria found
No criteria match your active search and filter combinations. Try clearing keywords or adjusting the level and evolution filters.
Every piece of non-text content shown to users has a text alternative that serves the equivalent purpose. Controls and inputs need a name that describes their purpose. Time-based media, tests that would be invalid in text, and content meant to create a specific sensory experience only need a text alternative that identifies them. A CAPTCHA needs a text alternative describing its purpose and a version that uses a different sense. Content that is pure decoration, used only for visual formatting, or not presented to users must be implemented so assistive technology can ignore it.
Usability gap
Alt text can be present and equivalent yet still tiring to use, for example when it repeats the caption beside it or runs to a paragraph.
Prerecorded audio-only content has a text alternative that presents equivalent information (an "alternative for time-based media"). Prerecorded video-only content has either that text alternative or an audio track with equivalent information. Media that is itself an alternative for text, and clearly labeled as such, is exempt.
Usability gap
A transcript that technically exists but sits on another page, or is only linked from a footer, is easy to miss. Users who need it may never find it.
Prerecorded audio in synchronized media (video with sound) has captions. By definition, captions cover both speech and the non-speech audio needed to understand the content. Media that is a clearly labeled alternative for text is exempt.
Usability gap
Complete captions can still be hard to follow when they are split mid-phrase, cover on-screen text, or can't be resized.
Prerecorded video with sound has either a full text alternative for time-based media or audio description of the video. Media that is a clearly labeled alternative for text is exempt.
Usability gap
Meeting Level A with a text document means blind users leave the video to read instead of experiencing it with everyone else.
Prerecorded video in synchronized media has audio description: narration added to describe important visual details that can't be understood from the main soundtrack alone.
Usability gap
Description squeezed into short pauses can leave out context. A separate described version is often hard to find, or lags behind updates to the main video.
Information, structure and relationships conveyed through presentation can be programmatically determined, or are available in text. If something looks like a heading, list, table or group, that structure has to be available to software too.
Usability gap
A page can convey its structure with the bare minimum of semantics and still be slow to navigate. Without landmarks or a sensible heading outline, screen reader users have fewer ways to jump around.
When the order of content affects its meaning, a correct reading order can be programmatically determined.
Usability gap
CSS that reorders content visually (flex order, grid placement) can still pass, yet keyboard and screen magnifier users see focus and reading jump around the screen.
2WCAG 3 Draft Successor(s)
0 successor provisions
No successor provision in the current draft.
3Mapping Status
No provision in the draft
📝
Mapping note
No provision in the current draft addresses reading sequence.
Instructions for understanding and operating content don't rely solely on sensory characteristics such as shape, color, size, visual location, orientation or sound.
Usability gap
Instructions that lead with position ("in the panel on the right") still slow down people who can't see the layout, or who see a reflowed version of it.
If the platform has a default orientation, content supports that orientation. If the platform does not have a default orientation, content supports both portrait and landscape orientations.
Input fields collecting information about the user have a programmatically determinable purpose, when the field's purpose is one listed in WCAG's Input Purposes section and the technology supports it. (In HTML, W3C's sufficient technique is the autocomplete attribute; techniques are informative.)
Usability gap
Correct autocomplete values don't help if scripts or browser workarounds stop autofill from working. People with motor or memory impairments are left retyping their details.
2WCAG 3 Draft Successor(s)
0 successor provisions
No successor provision in the current draft.
3Mapping Status
Related provisions only
📝
Mapping note
No provision in the current draft requires identifying input purpose. Automated entry allowed covers not blocking autofill or paste.
↔️
Related, not a successor
Automated Entry Allowed (core requirement):
Automated input of personal information from user agents, third-party tools, or paste is not prevented.
If audio plays automatically for more than 3 seconds, there is either a way to pause or stop it, or a way to control its volume separately from the system volume. Under WCAG's non-interference requirement this applies to everything on the page, even content not relied on to meet other criteria.
Usability gap
A pause button at the bottom of the page is hard to find for screen reader users, whose speech is drowned out by the audio while they look for it.
A mechanism is available to pause, stop, and adjust the volume independently of the overall system volume level, of any automatically playing audio in a page/view.
3Mapping Status
Successor in the draft
The provision(s) in column 2 cover the same subject. Compare the two texts for differences in scope and strictness.
Text and images of text have a contrast ratio of at least 4.5:1. Large-scale text (at least 18pt, or 14pt bold) needs 3:1. Text in inactive components, pure decoration, invisible text, text inside pictures with significant other visual content, and logos have no contrast requirement.
Usability gap
4.5:1 is a floor. Thin or small fonts at exactly 4.5:1 can still be hard to read for people with low vision, in glare, or on low-quality screens.
Apart from captions and images of text, text can be resized up to 200 percent without assistive technology and without loss of content or functionality.
Usability gap
Many people enlarge only the text, through browser or OS font settings rather than zoom. Layouts with fixed heights can clip that text even when they pass with page zoom.
If the technology can produce the visual presentation, real text is used instead of images of text. Exceptions: the image of text can be visually customized (font, size, color and background can be set), or a particular presentation is essential.
Usability gap
Text baked into banners and social cards can't be resized, recolored or reflowed, and blurs when magnified.
2WCAG 3 Draft Successor(s)
0 successor provisions
No successor provision in the current draft.
3Mapping Status
Related provisions only
📝
Mapping note
No provision in the current draft restricts images of text.
↔️
Related, not a successor
Text Detectable (core requirement):
All visible text has a programmatically determinable equivalent.
Content can be presented without losing information or functionality, and without scrolling in two directions, at a width of 320 CSS pixels (for vertically scrolling content) or a height of 256 CSS pixels (for horizontally scrolling content). Parts of the content that need a two-dimensional layout for their use or meaning are exempt.
Usability gap
A page can reflow while hiding key actions behind menus, or by covering much of the small viewport with sticky headers. People using 400% zoom then see very little content at once.
All content fits within 320 CSS pixels in the default orientation of text without requiring scrolling in more than one direction. Sections of content within the page/view that scroll in a different direction to the page/view fit within 320 CSS pixels of the page-scrolling direction.
These have a contrast ratio of at least 3:1 against adjacent colors: the visual information needed to identify user interface components and their states (except inactive components, and components whose appearance is set by the browser and not modified by the author), and the parts of graphics needed to understand the content (unless a particular presentation is essential).
Usability gap
A state change that meets 3:1 but is shown only by a thin border change is easy to miss.
In content built with markup languages, nothing is lost and nothing stops working when a user sets line height to 1.5 times the font size, spacing after paragraphs to 2 times, letter spacing to 0.12 times and word spacing to 0.16 times, changing no other style. Languages and scripts that don't use one of these properties are exempt for that property.
Usability gap
Layouts can survive the test values exactly but break with slightly larger user settings, or with fonts swapped in for dyslexia.
The presentation of text style properties can be adjusted, without loss of content or functionality, to meet the @@ [values to be determined] for: * typeface * font width * text decoration * capitalization * automatic end-of-line hyphenation
The presentation of blocks of text can be adjusted, without loss of content or functionality, to meet the @@ [values to be determined] for: * inline margin * block margin * line length * line height * justification
3Mapping Status
Successor in the draft
The provision(s) in column 2 cover the same subject. Compare the two texts for differences in scope and strictness.
When hover or keyboard focus makes extra content appear (such as a custom tooltip or submenu): it can be dismissed without moving the pointer or focus, unless it shows an input error or doesn't cover other content; if triggered by hover, the pointer can move onto it without it disappearing; and it stays visible until the trigger is removed, the user dismisses it, or its information is no longer valid. Content whose presentation the browser controls, such as a title-attribute tooltip, is exempt.
Usability gap
Hover content can pass and still be awkward on touch screens, where there is no hover, and for magnifier users who lose it off-screen.
A mechanism is available to dismiss content that appears on pointer hover or keyboard focus without moving pointer hover or keyboard focus, unless the additional content does not obscure or replace other content.
Content that appears on pointer hover or keyboard focus remains visible until the hover or keyboard focus trigger is removed, the user dismisses it, or its information is no longer valid.
3Mapping Status
Successor in the draft
The provision(s) in column 2 cover the same subject. Compare the two texts for differences in scope and strictness.
All functionality can be operated through a keyboard interface, without needing specific timing for individual keystrokes. The exception is functionality whose underlying function depends on the path of the user's movement, not just its endpoints (such as freehand drawing).
Usability gap
Something can be keyboard-operable yet take dozens of Tab presses, or rely on key combinations nobody would guess.
All components on the page/view that can be operated by pointer, audio (voice or other), gesture, camera, or other means can be operated using keyboard interface only.
If keyboard focus can move into a component, it can move out again using only the keyboard. If leaving needs more than unmodified arrow or Tab keys or another standard exit method, the user is told how. Under WCAG's non-interference requirement this applies to everything on the page.
Usability gap
A non-standard exit that is documented somewhere technically passes, but users rarely find the instructions.
Components that can be activated or entered using the keyboard interface, can be deactivated or exited using a standard keyboard navigation-operation technique, standard platform keyboard commands.
3Mapping Status
Successor in the draft
The provision(s) in column 2 cover the same subject. Compare the two texts for differences in scope and strictness.
If a keyboard shortcut uses only a letter, punctuation, number or symbol key, at least one of these is true: it can be turned off; it can be remapped to include a non-printable key such as Ctrl or Alt; or it only works while the relevant component has focus.
Usability gap
A setting to turn shortcuts off that is hard to find leaves speech-input users accidentally triggering actions until they discover it.
For each time limit the content sets, at least one is true: the user can turn it off before reaching it; adjust it to at least ten times the default; or is warned before it expires and given at least 20 seconds to extend it with a simple action, at least ten times. The limit is exempt if it's a required part of a real-time event with no possible alternative, if it's essential and extending it would invalidate the activity, or if it's longer than 20 hours.
Usability gap
Twenty seconds to respond to a warning is short for people using screen readers, switch access or speech input, especially if the warning doesn't take focus or isn't announced.
Moving, blinking or scrolling information that starts automatically, lasts more than five seconds and is shown alongside other content can be paused, stopped or hidden, unless the movement is essential. Auto-updating information that starts automatically and is shown alongside other content can be paused, stopped or hidden, or its update frequency controlled, unless essential. Under WCAG's non-interference requirement this applies to everything on the page.
Usability gap
A small pause button that is hard to find, or that resets when the page reloads, still passes. Motion can distract people with attention-related disabilities long before they find it.
Nothing on the page flashes more than three times in any one second, or the flashing is below the general flash and red flash thresholds defined in WCAG. Under WCAG's non-interference requirement this applies to everything on the page.
Usability gap
The thresholds are approximations. Content near them can still affect some people with photosensitive epilepsy, or cause migraines.
If a page can be navigated sequentially and the order affects meaning or operation, focusable components receive focus in an order that preserves meaning and operability.
Usability gap
An order that preserves meaning can still jump around the screen, which disorients sighted keyboard and magnifier users.
The purpose of each link can be determined from its text alone, or from its text together with its programmatically determined context, except where the purpose would be ambiguous to everyone.
Usability gap
Screen reader users who browse a list of links hear "Read more" ten times with no context, even though each link passes.
2WCAG 3 Draft Successor(s)
0 successor provisions
No successor provision in the current draft.
3Mapping Status
Related provisions only
📝
Mapping note
No provision in the current draft covers link purpose.
↔️
Related, not a successor
Interactive Element Names Available (core requirement):
Persistent names (including labels) that identify the purpose of the interactive element are visually and programmatically available.
Meaningful blocks of content have a semantically appropriate label that defines their purpose.
3Mapping Status
Successor in the draft
↔️
Related, not a successor
Interactive Element Names Available (core requirement):
Persistent names (including labels) that identify the purpose of the interactive element are visually and programmatically available.
Any keyboard-operable interface has a mode of operation in which the keyboard focus indicator is visible.
Usability gap
A visible indicator, even one that meets 3:1, can be hard to spot if it's thin or close in style to the hover state.
2WCAG 3 Draft Successor(s)
0 successor provisions
No successor provision in the current draft.
3Mapping Status
Related provisions only
📝
Mapping note
No provision in the current draft requires a visible focus indicator as such; the related provisions cover its contrast and the use of the browser default.
↔️
Related, not a successor
Focus Indicator Contrast Sufficient (core requirement):
If a custom focus indicator is used, it has sufficient adjacent contrast and change of contrast.
Default Focus Indicator Used (supplemental requirement):
The focusable item uses the user agent default focus indicator.
Functionality that uses dragging can also be done with a single pointer without dragging, unless dragging is essential or the browser provides the functionality and the author hasn't modified it.
Usability gap
An alternative that takes many taps, or sits in an overflow menu, technically passes but is tiring for people with motor impairments.
All functionality and content available using complex pointer inputs is also available using a simple pointer input, or a sequence of simple pointer inputs that do not require timing.
3Mapping Status
Successor in the draft
The provision(s) in column 2 cover the same subject. Compare the two texts for differences in scope and strictness.
Pointer targets are at least 24 by 24 CSS pixels, except when: a 24 CSS pixel circle centered on each smaller target doesn't overlap another target or another such circle; the same function is available through another control on the page that meets this criterion; the target is in a sentence or limited by the line height of surrounding text; the browser sets the size and the author hasn't changed it; or the presentation is essential or legally required.
Usability gap
24 by 24 is still small for people with tremors or limited dexterity. Targets that pass only through spacing are easy to miss.
2WCAG 3 Draft Successor(s)
0 successor provisions
No successor provision in the current draft.
3Mapping Status
No provision in the draft
📝
Mapping note
No provision in the current draft covers target size.
The default human language of each page can be programmatically determined. (In HTML, W3C's sufficient technique is the lang attribute on the html element; techniques are informative.)
Usability gap
A correct but generic code, such as en with no region, can't tell a screen reader which accent or spelling conventions to use.
The human language of each passage or phrase can be programmatically determined. Exempt: proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the surrounding language.
Usability gap
Proper names and technical terms are exempt, so a page full of untagged foreign names can still be mispronounced.
When any component receives focus, that doesn't start a change of context. WCAG defines a change of context as a change of user agent, viewport, focus, or content that changes the meaning of the page.
Usability gap
Focus-triggered changes that fall short of a "change of context", such as large panels expanding, can still disorient people using magnification.
2WCAG 3 Draft Successor(s)
0 successor provisions
No successor provision in the current draft.
3Mapping Status
Related provisions only
📝
Mapping note
No provision in the current draft forbids a change of context on focus; the related ones cover notification and focus movement.
↔️
Related, not a successor
Change Of Focus Notified (core requirement):
When the focus changes on-focus or automatically, the user is notified visually and programmatically.
Focus user-controlled (core requirement):
The keyboard focus only moves as a result of user interaction.
Changing the setting of a component doesn't automatically cause a change of context, unless the user was told about this behavior before using the component.
Usability gap
Advance notice that is technically present, such as a sentence above the form, is easily missed. Keyboard users browsing a select with arrow keys can trigger navigation by accident.
2WCAG 3 Draft Successor(s)
0 successor provisions
No successor provision in the current draft.
3Mapping Status
Related provisions only
📝
Mapping note
No provision in the current draft forbids a change of context on input.
↔️
Related, not a successor
Change Of User Agent Notified (core requirement):
When content triggers a device change or an automatic user agent change, the user is notified before the change occurs.
Page/view change notified (core requirement):
When content triggers a change of page/view there is a visual change within the view and programmatic notification of the change.
If pages in a set repeat any of these help mechanisms, they appear in the same order relative to other page content, unless the user changes it: human contact details, a human contact mechanism, a self-help option, or a fully automated contact mechanism.
Usability gap
Consistently placed help can still be unhelpful, such as a chatbot that can't reach a person.
Labels or instructions are provided when content requires user input. WCAG defines a label as text, or a component with a text alternative, presented to the user to identify a component.
Usability gap
Placeholder-only labels disappear as soon as people type, so users with memory or attention difficulties lose track of what a field wants, and prefilled fields can't be checked.
Information the user has already entered, or that was provided to them, and that must be entered again in the same process, is either auto-populated or available to select. Exceptions: re-entry is essential, is needed for security, or the earlier information is no longer valid.
Usability gap
Offering the earlier value in a hard-to-find control satisfies "available to select" but still makes people re-enter data.
Information previously entered by or provided to the user that is required to be entered again in the same process is either auto-populated, or available for the user to select.
3Mapping Status
Successor in the draft
The provision(s) in column 2 cover the same subject. Compare the two texts for differences in scope and strictness.
No step of an authentication process requires a cognitive function test, unless that step offers one of: another method that doesn't rely on one; a mechanism to help complete it; a test that is recognizing objects; or a test that is identifying non-text content the user provided. WCAG defines a cognitive function test as remembering, manipulating or transcribing information, such as remembering a password, transcribing characters, correct spelling, calculations or puzzles. Name, email and phone number don't count.
Usability gap
Object-recognition CAPTCHAs are allowed at AA but are still very hard for many blind and low-vision users and people with cognitive disabilities.
For all interface components (including form elements, links and scripted components), the name and role can be programmatically determined; states, properties and values the user can set can be programmatically set; and changes to them are notified to user agents, including assistive technologies.
Usability gap
Custom widgets can expose a valid name and role yet not match expected keyboard behavior or announce in a useful order.
In content built with markup languages, status messages can be programmatically determined through role or properties, so assistive technologies can present them without them receiving focus. WCAG defines a status message as a change in content that isn't a change of context and that tells the user about success or results, waiting, progress, or errors.
Usability gap
Over-announcing (live regions for every update) can drown out the messages that matter.
Sign language interpretation is provided for all prerecorded audio content in the primary sign language that is most appropriate for each intended audience or region.
3Mapping Status
Successor in the draft
↔️
Related, not a successor
Sign Language Controllable (supplemental requirement):
A mechanism is available to show and hide sign language interpretation.
Where pauses in the foreground audio are too short for audio description to convey the sense of the video, extended audio description is provided: the video pauses so there is time for more description. Applies to prerecorded video in synchronized media.
Usability gap
Frequent pauses can make the experience choppy if the description is longer than it needs to be.
All prerecorded synchronized media and all prerecorded video-only media have an alternative for time-based media: a document with correctly sequenced text descriptions of the visual and auditory information, and a way to achieve the outcome of any interaction.
Usability gap
A complete alternative is little use if users can't find it.
The default visual presentation of text meets @@[contrast measure to be determined, at a higher level than the core requirement for Text contrast sufficient (minimum)].
3Mapping Status
Successor in the draft
📝
Mapping note
The draft's contrast measure is still to be determined.
For prerecorded audio-only content that is mainly foreground speech (not an audio CAPTCHA, audio logo, or singing or rapping), one of these is true: there are no background sounds, they can be turned off, or they are at least 20 decibels quieter than the speech, apart from occasional sounds of one or two seconds.
Usability gap
Even background music at 20dB lower can make speech hard to follow for people with hearing loss.
2WCAG 3 Draft Successor(s)
0 successor provisions
No successor provision in the current draft.
3Mapping Status
No provision in the draft
📝
Mapping note
No provision in the current draft covers background audio levels.
For blocks of text, a mechanism is available to: choose foreground and background colors; limit width to 80 characters (40 for CJK); avoid justified text; get line spacing of at least 1.5 and paragraph spacing at least 1.5 times the line spacing; and resize text to 200 percent without horizontal scrolling in a full-screen window.
Usability gap
Relying on users to find browser settings means many never benefit.
The presentation of blocks of text can be adjusted, without loss of content or functionality, to meet the @@ [values to be determined] for: * inline margin * block margin * line length * line height * justification
The default/authored presentation of blocks of text meets the minimum @@ [values to be determined] for: * inline margin * block margin * line length * line height
All functionality can be operated through a keyboard interface without needing specific timing for individual keystrokes. Unlike 2.1.1, there is no exception for path-dependent input.
Usability gap
Keyboard alternatives for drawing or gesture tools can be technically present but tedious.
All components on the page/view that can be operated by pointer, audio (voice or other), gesture, camera, or other means can be operated using keyboard interface only.
A mechanism is available so that the purpose of each link can be identified from the link text alone, except where the purpose would be ambiguous to everyone.
Usability gap
Visually hidden text added to make links unique can mismatch what speech-input users see and say.
2WCAG 3 Draft Successor(s)
0 successor provisions
No successor provision in the current draft.
3Mapping Status
No provision in the draft
📝
Mapping note
No provision in the current draft covers link purpose.
Pointer targets are at least 44 by 44 CSS pixels. Exceptions: an equivalent target of that size is on the same page; the target is in a sentence or block of text; the browser sets the size and the author hasn't changed it; or the presentation is essential.
Usability gap
None beyond 2.5.8. This is the stricter version.
2WCAG 3 Draft Successor(s)
0 successor provisions
No successor provision in the current draft.
3Mapping Status
No provision in the draft
📝
Mapping note
No provision in the current draft covers target size.
When text needs reading ability above lower secondary education level (after removing proper names and titles), supplemental content or a simpler version is available.
Usability gap
Readability formulas measure sentence and word length, not whether people actually understand the text.
2WCAG 3 Draft Successor(s)
0 successor provisions
No successor provision in the current draft.
3Mapping Status
Related provisions only
📝
Mapping note
No provision in the current draft uses a reading-level test.
↔️
Related, not a successor
Summaries Available (core requirement):
A summary is available for long-form text content and: * is identifiable visually and programmatically, * uses concise sentences, and * provides access to explanations of any uncommon words that are used in the summary.
Common Words Used (supplemental requirement):
Common words are used, and definitions are available for uncommon words.
Changes of context happen only at the user's request, or there's a mechanism to turn such changes off.
Usability gap
Opening new windows or tabs without warning remains common and disorienting.
2WCAG 3 Draft Successor(s)
0 successor provisions
No successor provision in the current draft.
3Mapping Status
Related provisions only
📝
Mapping note
No provision in the current draft restricts changes of context to user request.
↔️
Related, not a successor
Focus user-controlled (core requirement):
The keyboard focus only moves as a result of user interaction.
Change Of User Agent Notified (core requirement):
When content triggers a device change or an automatic user agent change, the user is notified before the change occurs.
For pages that require the user to submit information, at least one is true: submissions are reversible; input is checked and the user can correct it; or the user can review, confirm and correct before final submission.
Usability gap
None beyond 3.3.4. This extends it to every submission.
Data entry interfaces allow for users to do at least one of the following before submission: * Review, confirm, and correct all information. * Review and correct input errors found during validation.
3Mapping Status
Successor in the draft
The provision(s) in column 2 cover the same subject. Compare the two texts for differences in scope and strictness.
Users are warned how long they can be inactive before data is lost, unless the data is kept for more than 20 hours of inactivity.
Usability gap
A warning shown once at the start of a long form is forgotten by the time it matters.
2WCAG 3 Draft Successor(s)
0 successor provisions
No successor provision in the current draft.
3Mapping Status
Related provisions only
📝
Mapping note
No provision in the current draft covers warnings about inactivity timeouts.
↔️
Related, not a successor
Time Limits Conveyed (supplemental requirement):
Users are informed at the start of the process or session that a time limit exists, its length, and that it can be adjusted.
When the focus indicator is visible, an area of it is at least as large as a 2 CSS pixel thick perimeter of the unfocused component, and has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states. It doesn't apply if the browser sets the indicator and the author can't adjust it, or if the author hasn't modified the indicator or its background.
Usability gap
An indicator can meet the area and contrast numbers yet be hard to spot if it is inside the component or similar to other states such as hover.
Functionality that uses multipoint gestures (such as pinch) or path-based gestures (such as a swipe pattern) can also be operated with a single pointer without a path-based gesture, unless the gesture is essential.
Usability gap
A single-pointer alternative hidden in a menu technically passes but is rarely discovered.
All functionality and content available using complex pointer inputs is also available using a simple pointer input, or a sequence of simple pointer inputs that do not require timing.
3Mapping Status
Successor in the draft
The provision(s) in column 2 cover the same subject. Compare the two texts for differences in scope and strictness.
For single-pointer functionality, at least one is true: nothing happens on the down-event; the function completes on the up-event and can be aborted before or undone after; the up-event reverses whatever the down-event did; or completing on the down-event is essential.
Usability gap
Undo that is only available briefly in a toast is easy to miss for screen reader and magnifier users.
At least one of the following is true for functionality that can be activated using a simple pointer input: No down event : The down event of the pointer is not used to execute any part of the function. Cancel or undo : Completion of the function is on the up event and a mechanism is available to cancel the function before completion, or there is a mechanism to undo the function after completion. Up reversal : The up event reverses any outcome of the preceding down event.
3Mapping Status
Successor in the draft
↔️
Related, not a successor
Consistent Pointer Cancellation (supplemental requirement):
The method of pointer cancellation is consistent for each type of interaction within a set of pages/views.
Functionality operated by device motion (such as shaking or tilting) or user motion can also be operated through interface components, and responding to motion can be turned off. Exceptions: the motion works through an accessibility-supported interface, or it's essential and doing it another way would invalidate the activity.
Usability gap
A motion setting that is off only once the user finds it means people with tremors may trigger actions by accident on first use.
Content doesn't restrict the input methods available on a platform, except where that is essential, needed for security, or needed to respect user settings.
Usability gap
Switching off touch on "desktop" layouts strands people who use a touchscreen with a keyboard.
The relative order of navigation items is consistent within blocks of navigation that are repeated on multiple pages/views of the conformance scope or process.
3Mapping Status
Successor in the draft
↔️
Related, not a successor
Consistent Navigation Labels (supplemental requirement):
The labeling of navigation items within blocks of navigation that are repeated on multiple pages/views in the conformance scope or process is consistent.
Components with the same functionality within a set of pages are identified consistently.
Usability gap
Consistent labels with inconsistent icons, or the reverse, still undermine recognition.
2WCAG 3 Draft Successor(s)
0 successor provisions
No successor provision in the current draft.
3Mapping Status
Related provisions only
📝
Mapping note
No provision in the current draft requires consistent identification of all same-function components.
↔️
Related, not a successor
Consistent Navigation Labels (supplemental requirement):
The labeling of navigation items within blocks of navigation that are repeated on multiple pages/views in the conformance scope or process is consistent.
Consistent Control Location (supplemental requirement):
Where an interactive element with the same purpose is used across pages/views, its visual position in the layout is maintained.
If an input error is automatically detected and suggestions for correcting it are known, the suggestions are provided, unless that would compromise the security or purpose of the content.
Usability gap
Correct suggestions can still be hard to act on, for example when they appear only in a summary at the top of a long form.
For pages that create legal commitments or financial transactions, modify or delete user-controllable data, or submit test responses, at least one is true: submissions are reversible; input is checked for errors and the user can correct them; or the user can review, confirm and correct before final submission.
Usability gap
A review step that users can click through without noticing errors technically confirms, but doesn't prevent costly mistakes.
Data entry interfaces allow for users to do at least one of the following before submission: * Review, confirm, and correct all information. * Review and correct input errors found during validation.
3Mapping Status
Successor in the draft
↔️
Related, not a successor
Consequences Explained Before Agreement (supplemental requirement):
Legal, financial, privacy, and security consequences are provided before finalizing an agreement.
No step of an authentication process requires a cognitive function test, unless that step offers another method that doesn't rely on one, or a mechanism to help complete it. Unlike 3.3.8, there are no object-recognition or personal-content exceptions.
Usability gap
None beyond 3.3.8. This removes 3.3.8's object-recognition and personal-content exceptions.
Nothing. WCAG 2.2 marks this criterion obsolete and removed, so it can't be failed under 2.2. WCAG 2.2's introduction notes that organizations required by policy to conform to WCAG 2.0 or 2.1 may still need to test and report it.
Usability gap
Invalid markup that doesn't affect the accessibility tree isn't a WCAG failure, but it can make behavior inconsistent across browsers and assistive technologies.