This tool provides a customizable view of WCAG 2 resources:
Background on these resources is provided in the WCAG Overview and The WCAG 2 documents. For important information about techniques, see Understanding Techniques for WCAG Success Criteria.
Techniques: Shows only the types of techniques and/or failures selected.
The Share this view button provides a link to this tool with the filters you have set. The SHARE buttons provide links to individual success criteria.
WCAG 2.2 WCAG 2.0 Only 2.1 Added Success CriteriaNote: Clear Filters will not change the selected version.
Information and user interface components must be presentable to users in ways they can perceive.
Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Short text alternative techniques for Situation A:
Short text alternative techniques for Situation B:
Long text alternative techniques for Situation B:
Text alternative techniques for controls and input for Situation C:
Short text alternative techniques for Situation D:
Techniques to indicate that text alternatives are not required for Situation F:
Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Captions are provided for all live audio content in synchronized media.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Note: Captions may be generated using real-time text translation service.
Audio description is provided for all prerecorded video content in synchronized media.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Sign language interpretation is provided for all prerecorded audio content in synchronized media.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
An alternative for time-based media that presents equivalent information for live audio-only content is provided.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound.
Note: For requirements related to color, refer to Guideline 1.4.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.
Note: Examples where a particular display orientation may be essential are a bank check, a piano application, slides for a projector or television, or virtual reality content where content is not necessarily restricted to landscape or portrait display orientation.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
The content is implemented using technologies with support for identifying the expected meaning for form input data.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
In content implemented using markup languages, the purpose of user interface components, icons, and regions can be programmatically determined.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
coga-simplification="simplest")aria-invalid and aria-requiredColor is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
Note: This success criterion addresses color perception specifically. Other forms of perception are covered in Guideline 1.3 including programmatic access to color and other visual presentation coding.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
If any audio on a web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.
Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the web page (whether or not it is used to meet other success criteria) must meet this success criterion. See Conformance Requirement 5: Non-Interference.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Logotypes: Text that is part of a logo or brand name has no contrast requirement.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Essential: A particular presentation of text is essential to the information being conveyed.
Note: Logotypes (text that is part of a logo or brand name) are considered essential.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Logotypes: Text that is part of a logo or brand name has no contrast requirement.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
20 dB: The background sounds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sounds that last for only one or two seconds.
Note: Per the definition of "decibel," background sound that meets this requirement will be approximately four times quieter than the foreground speech content.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window.
Note 1: Content is not required to use these values. The requirement is that a mechanism is available for users to change these presentation aspects. The mechanism can be provided by the browser or other user agent. Content is not required to provide the mechanism.
Note 2: Writing systems for some languages use different presentation aspects to improve readability and legibility. If a presentation aspect in this success criterion is not used in a writing system, content in that writing system does not need to use that presentation setting and can conform without it. Authors are encouraged to follow guidance for improving readability and legibility of text in their writing system.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed.
Note: Logotypes (text that is part of a logo or brand name) are considered essential.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Horizontal scrolling content at a height equivalent to 256 CSS pixels.
Except for parts of the content which require two-dimensional layout for usage or meaning.
Note 1: 320 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels wide at 400% zoom. For web content which is designed to scroll horizontally (e.g., with vertical text), 256 CSS pixels is equivalent to a starting viewport height of 1024 CSS pixels at 400% zoom.
Note 2: Examples of content which requires two-dimensional layout are images required for understanding (such as maps and diagrams), video, games, presentations, data tables (not individual cells), and interfaces where it is necessary to keep toolbars in view while manipulating content. It is acceptable to provide two-dimensional scrolling for such parts of the content.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Word spacing to at least 0.16 times the font size.
Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script.
Note 1: Content is not required to use these text spacing values. The requirement is to ensure that when a user overrides the authored text spacing, content or functionality is not lost.
Note 2: Writing systems for some languages use different text spacing settings, such as paragraph start indent. Authors are encouraged to follow locally available guidance for improving readability and legibility of text in their writing system.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Persistent: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author.
Note 1: Examples of additional content controlled by the user agent include browser tooltips created through use of the HTML title attribute [HTML].
Note 2: Custom tooltips, sub-menus, and other nonmodal popups that display on hover and focus are examples of additional content covered by this criterion.
Note 3: This criterion applies to content that appears in addition to the triggering component itself. Since hidden components that are made visible on keyboard focus (such as links used to skip to another part of a page) do not present additional content they are not covered by this criterion.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
User interface components and navigation must be operable.
All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.
Note 1: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not.
Note 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.
Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Active only on focus: The keyboard shortcut for a user interface component is only active when that component has focus.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
20 Hour Exception: The time limit is longer than 20 hours.
Note: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.
Note 1: For requirements related to flickering or flashing content, refer to Guideline 2.3.
Note 2: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.
Note 3: Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so.
Note 4: An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Note: Refer to Techniques for Addressing Success Criterion 2.2.1 for techniques related to providing notifications about time limits.
Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions.
Note: Privacy regulations may require explicit user consent before user identification has been authenticated and before user data is preserved. In cases where the user is a minor, explicit consent may not be solicited in most jurisdictions, countries or regions. Consultation with privacy professionals and legal counsel is advised when considering data preservation as an approach to satisfy this success criterion.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.
Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Web pages do not contain anything that flashes more than three times in any one second period.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
A mechanism is available to bypass blocks of content that are repeated on multiple web pages.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Web pages have titles that describe topic or purpose.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
If a web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
More than one way is available to locate a web page within a set of web pages except where the web page is the result of, or a step in, a process.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Headings and labels describe topic or purpose.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Note: Headings and labels must be programmatically determined, per Success Criterion 1.3.1.
Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Information about the user's location within a set of web pages is available.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Section headings are used to organize the content.
Note 1: "Heading" is used in its general sense and includes titles and other ways to add a heading to different types of content.
Note 2: This success criterion covers sections within writing, not user interface components. User interface components are covered under Success Criterion 4.1.2.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.
Note 1: Where content in a configurable interface can be repositioned by the user, then only the initial positions of user-movable content are considered for testing and conformance of this success criterion.
Note 2: Content opened by the user may obscure the component receiving focus. If the user can reveal the focused component without advancing the keyboard focus, the component with focus is not considered visually hidden due to author-created content.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
When a user interface component receives keyboard focus, no part of the component is hidden by author-created content.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states.
Exceptions:The focus indicator and the indicator's background color are not modified by the author.
Note 1: What is perceived as the user interface component or sub-component (to determine the perimeter) depends on its visual presentation. The visual presentation includes the component's visible content, border, and component-specific background. It does not include shadow and glow effects outside the component's content, background, or border.
Note 2: Examples of sub-components that may receive a focus indicator are menu items in an opened drop-down menu, or focusable cells in a grid.
Note 3: Contrast calculations can be based on colors defined within the technology (such as HTML, CSS, and SVG). Pixels modified by user agent resolution enhancements and anti-aliasing can be ignored.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.
Note: This requirement applies to web content that interprets pointer actions (i.e., this does not apply to actions that are required to operate the user agent or assistive technology).
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Essential: Completing the function on the down-event is essential.
Note 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.
Note 2: This requirement applies to web content that interprets pointer actions (i.e., this does not apply to actions that are required to operate the user agent or assistive technology).
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
For user interface components with labels that include text or images of text, the name contains the text that is presented visually.
Note: A best practice is to have the text of the label at the start of the name.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Essential: The motion is essential for the function and doing so would invalidate the activity.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Essential: A particular presentation of the target is essential to the information being conveyed.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or required to respect user settings.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
focus, blur, click, in Javascript (Potential future technique)All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author.
Note: This requirement applies to web content that interprets pointer actions (i.e., this does not apply to actions that are required to operate the user agent or assistive technology).
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Essential: A particular presentation of the target is essential or is legally required for the information being conveyed.
Note 1: Targets that allow for values to be selected spatially based on position within the target are considered one target for the purpose of the success criterion. Examples include sliders, color pickers displaying a gradient of colors, or editable areas where you position the cursor.
Note 2: For inline targets the line-height should be interpreted as perpendicular to the flow of text. For example, in a language displayed vertically, the line-height would be horizontal.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Information and the operation of the user interface must be understandable.
The default human language of each web page can be programmatically determined.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
A mechanism for identifying the expanded form or meaning of abbreviations is available.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Note: Different sites may address this success criterion in different ways. An audio version of the content may be helpful to some users. For some people who are deaf, a sign language version of the page may be easier to understand than a written language version since sign language may be their first language. Some sites may decide to do both or other combinations. No technique will help all users who have difficulty. So different techniques are provided as sufficient techniques here for authors trying to make their sites more accessible. Any numbered technique or combination above can be used by a particular site and it is considered sufficient by the Working Group.
A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
When any user interface component receives focus, it does not initiate a change of context.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Note: A change of content is not always a change of context. This success criterion is automatically met if changes in content are not also changes of context.
Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Note: A change of content is not always a change of context. This success criterion is automatically met if changes in content are not also changes of context.
Navigational mechanisms that are repeated on multiple web pages within a set of web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Components that have the same functionality within a set of web pages are identified consistently.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Text alternatives that are "consistent" are not always "identical." For instance, you may have a graphical arrow at the bottom of a web page that links to the next web page. The text alternative may say "Go to page 4." Naturally, it would not be appropriate to repeat this exact text alternative on the next web page. It would be more appropriate to say "Go to page 5". Although these text alternatives would not be identical, they would be consistent, and therefore would satisfy this success criterion.
A single non-text-content-item may be used to serve different functions. In such cases, different text alternatives are necessary and should be used. Examples can be commonly found with the use of icons such as check marks, cross marks, and traffic signs. Their functions can be different depending on the context of the web page. A check mark icon may function as "approved", "completed", or "included", to name a few, depending on the situation. Using "check mark" as text alternative across all web pages does not help users understand the function of the icon. Different text alternatives can be used when the same non-text content serves multiple functions.
Changes of context are initiated only by user request or a mechanism is available to turn off such changes.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
A fully automated contact mechanism.
Note 1: Help mechanisms may be provided directly on the page, or may be provided via a direct link to a different page containing the information.
Note 2: For this success criterion, "the same order relative to other page content" can be thought of as how the content is ordered when the page is serialized. The visual position of a help mechanism is likely to be consistent across pages for the same page variation (e.g., CSS break-point). The user can initiate a change, such as changing the page's zoom or orientation, which may trigger a different page variation. This criterion is concerned with relative order across pages displayed in the same page variation (e.g., same zoom level and orientation).
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Labels or instructions are provided when content requires user input.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Note: The techniques at the end of the above list should be considered "last resort" and only used when the other techniques cannot be applied to the page. The earlier techniques are preferred because they increase accessibility to a wider user group.
If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Note: In some cases, more than one of these situations may apply. For example, when a mandatory field also requires the data to be in a specific format.
Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Context-sensitive help is available.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
available for the user to select.
Except when:previously entered information is no longer valid.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Personal Content: The cognitive function test is to identify non-text content the user provided to the website.
Note 1: "Object recognition" and "Personal content" may be represented by images, video, or audio.
Note 2: Examples of mechanisms that satisfy this criterion include:
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Mechanism: A mechanism is available to assist the user in completing the cognitive function test.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.
In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.
Note 1: This success criterion should be considered as always satisfied for any content using HTML or XML.
Note 2:
Since this criterion was written, the HTML Living Standard has adopted specific requirements governing how user agents must handle incomplete tags, incorrect element nesting, duplicate attributes, and non-unique IDs. [HTML]
Although the HTML standard treats some of these cases as non-conforming for authors, it is considered to "allow these features" for the purposes of this success criterion because the specification requires that user agents support handling these cases consistently. In practice, this criterion no longer provides any benefit to people with disabilities in itself.
Issues such as missing roles due to inappropriately nested elements or incorrect states or names due to a duplicate ID are covered by different success criteria and should be reported under those criteria rather than as issues with 4.1.1.
For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
Note: This success criterion is primarily for web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Note: Not all examples in the preceding general techniques use status messages to convey warnings or errors to users. A role of "alert" is only necessary where a change of context does not take place.
role="progressbar" (future link)role="marquee" (future link)role="timer" (future link)role="alert" or aria-live="assertive" on content which is not important and time-sensitive (future link)We welcome feedback and suggestions:
Copyright © 2025 W3C ®. See Permission to Use WAI Material.