Last active
June 24, 2024 13:15
-
-
Save lesliedoherty/d4e37c5b3ad38721853bf9854ffda65e to your computer and use it in GitHub Desktop.
WCAG 2.1 Guidelines in CSV
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Error | summary | sufficient techniques situation A | sufficient techniques situation B | sufficient techniques situation C | sufficient techniques situation D | sufficient techniques situation E | sufficient techniques situation F | Failures | Advisory Techniques | |
|---|---|---|---|---|---|---|---|---|---|---|
| 1.1.1 Non-text ContentLevel A | All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. Show Hide full descriptionControls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Success Criterion 4.1.2 for additional requirements for controls and content that accepts user input.)Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.)Test: If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content.Sensory: If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.CAPTCHA: If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.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. | Situation A: If a short description can serve the same purpose and present the same information as the non-text content: G94: Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content Short text alternative techniques for Situation A: ARIA6: Using aria-label to provide labels for objects ARIA10: Using aria-labelledby to provide a text alternative for non-text content G196: Using a text alternative on one item within a group of images that describes all items in the group FLASH1: Setting the name property for a non-text object FLASH5: Combining adjacent image and text buttons for the same resource FLASH28: Providing text alternatives for ASCII art, emoticons, and leetspeak in Flash H2: Combining adjacent image and text links for the same resource H35: Providing text alternatives on applet elements H37: Using alt attributes on img elements H53: Using the body of the object element H86: Providing text alternatives for ASCII art, emoticons, and leetspeak PDF1: Applying text alternatives to images with the Alt entry in PDF documents SL5: Defining a Focusable Image Class for Silverlight | Situation B: If a short description can not serve the same purpose and present the same information as the non-text content (e.g., a chart or diagram): G95: Providing short text alternatives that provide a brief description of the non-text content Short text alternative techniques for Situation B: ARIA6: Using aria-label to provide labels for objects ARIA10: Using aria-labelledby to provide a text alternative for non-text content G196: Using a text alternative on one item within a group of images that describes all items in the group FLASH1: Setting the name property for a non-text object FLASH5: Combining adjacent image and text buttons for the same resource FLASH28: Providing text alternatives for ASCII art, emoticons, and leetspeak in Flash H2: Combining adjacent image and text links for the same resource H35: Providing text alternatives on applet elements H37: Using alt attributes on img elements H53: Using the body of the object element H86: Providing text alternatives for ASCII art, emoticons, and leetspeak PDF1: Applying text alternatives to images with the Alt entry in PDF documents SL5: Defining a Focusable Image Class for Silverlight Long text alternative techniques for Situation B: ARIA15: Using aria-describedby to provide descriptions of images G73: Providing a long description in another location with a link to it that is immediately adjacent to the non-text content G74: Providing a long description in text near the non-text content, with a reference to the location of the long description in the short description G92: Providing long description for non-text content that serves the same purpose and presents the same information FLASH2: Setting the description property for a non-text object in Flash FLASH11: Providing a longer text description of an object H45: Using longdesc H53: Using the body of the object element SL8: Displaying HelpText in Silverlight User Interfaces | Situation C: If non-text content is a control or accepts user input: G82: Providing a text alternative that identifies the purpose of the non-text content Text alternative techniques for controls and input for Situation C: ARIA6: Using aria-label to provide labels for objects ARIA9: Using aria-labelledby to concatenate a label from several text nodes FLASH6: Creating accessible hotspots using invisible buttons FLASH25: Labeling a form control by setting its accessible name FLASH27: Providing button labels that describe the purpose of a button FLASH29: Setting the label property for form components FLASH30: Specifying accessible names for image buttons FLASH32: Using auto labeling to associate text labels with form controls H24: Providing text alternatives for the area elements of image maps H30: Providing link text that describes the purpose of a link for anchor elements H36: Using alt attributes on images used as submit buttons H44: Using label elements to associate text labels with form controls H65: Using the title attribute to identify form controls when the label element cannot be used SL18: Providing Text Equivalent for Nontext Silverlight Controls With AutomationProperties.Name SL26: Using LabeledBy to Associate Labels and Targets in Silverlight SL30: Using Silverlight Control Compositing and AutomationProperties.Name | Situation D: If non-text content is time-based media (including live video-only and live audio-only); a test or exercise that would be invalid if presented in text; or primarily intended to create a specific sensory experience: Providing a descriptive labelShort text alternative techniques for Situation D: ARIA6: Using aria-label to provide labels for objects ARIA10: Using aria-labelledby to provide a text alternative for non-text content G196: Using a text alternative on one item within a group of images that describes all items in the group FLASH1: Setting the name property for a non-text object FLASH5: Combining adjacent image and text buttons for the same resource FLASH28: Providing text alternatives for ASCII art, emoticons, and leetspeak in Flash H2: Combining adjacent image and text links for the same resource H35: Providing text alternatives on applet elements H37: Using alt attributes on img elements H53: Using the body of the object element H86: Providing text alternatives for ASCII art, emoticons, and leetspeak PDF1: Applying text alternatives to images with the Alt entry in PDF documents SL5: Defining a Focusable Image Class for Silverlight ARIA6: Using aria-label to provide labels for objects ARIA10: Using aria-labelledby to provide a text alternative for non-text content G68: Providing a short text alternative that describes the purpose of live audio-only and live video-only content Short text alternative techniques for Situation D: ARIA6: Using aria-label to provide labels for objects ARIA10: Using aria-labelledby to provide a text alternative for non-text content G196: Using a text alternative on one item within a group of images that describes all items in the group FLASH1: Setting the name property for a non-text object FLASH5: Combining adjacent image and text buttons for the same resource FLASH28: Providing text alternatives for ASCII art, emoticons, and leetspeak in Flash H2: Combining adjacent image and text links for the same resource H35: Providing text alternatives on applet elements H37: Using alt attributes on img elements H53: Using the body of the object element H86: Providing text alternatives for ASCII art, emoticons, and leetspeak PDF1: Applying text alternatives to images with the Alt entry in PDF documents SL5: Defining a Focusable Image Class for Silverlight G100: Providing a short text alternative which is the accepted name or a descriptive name of the non-text content Short text alternative techniques for Situation D: ARIA6: Using aria-label to provide labels for objects ARIA10: Using aria-labelledby to provide a text alternative for non-text content G196: Using a text alternative on one item within a group of images that describes all items in the group FLASH1: Setting the name property for a non-text object FLASH5: Combining adjacent image and text buttons for the same resource FLASH28: Providing text alternatives for ASCII art, emoticons, and leetspeak in Flash H2: Combining adjacent image and text links for the same resource H35: Providing text alternatives on applet elements H37: Using alt attributes on img elements H53: Using the body of the object element H86: Providing text alternatives for ASCII art, emoticons, and leetspeak PDF1: Applying text alternatives to images with the Alt entry in PDF documents SL5: Defining a Focusable Image Class for Silverlight | Situation E: If non-text content is a CAPTCHA: G143: Providing a text alternative that describes the purpose of the CAPTCHA AND G144: Ensuring that the Web Page contains another CAPTCHA serving the same purpose using a different modality | Situation F: If the non-text content should be ignored by assistive technology: Implementing or marking the non-text content so that it will be ignored by assistive technologyTechniques to indicate that text alternatives are not required for Situation F: C9: Using CSS to include decorative images FLASH3: Marking objects in Flash so that they can be ignored by AT H67: Using null alt text and no title attribute on img elements for images that AT should ignore PDF4: Hiding decorative images with the Artifact tag in PDF documents | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F3.html" class="">F3: Failure of Success Criterion 1.1.1 due to using CSS to include images that convey important information </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F13.html">F13: Failure of Success Criterion 1.1.1 and 1.4.1 due to having a text alternative that does not include information that is conveyed by color differences in the image </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F20.html" class="">F20: Failure of Success Criterion 1.1.1 and 4.1.2 due to not updating text alternatives when changes to non-text content occur </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F30.html">F30: Failure of Success Criterion 1.1.1 and 1.2.1 due to using text alternatives that are not alternatives (e.g., filenames or placeholder text) </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F38.html">F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images in HTML in a way that allows assistive technology to ignore them </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F39.html">F39: Failure of Success Criterion 1.1.1 due to providing a text alternative that is not null (e.g., alt="spacer" or alt="image") for images that should be ignored by assistive technology </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F65.html" class="">F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute or text alternative on img elements, area elements, and input elements of type "image" </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F67.html">F67: Failure of Success Criterion 1.1.1 and 1.2.1 due to providing long descriptions for non-text content that does not serve the same purpose or does not present the same information </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F71.html" class="">F71: Failure of Success Criterion 1.1.1 due to using text look-alikes to represent text without providing a text alternative </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F72.html">F72: Failure of Success Criterion 1.1.1 due to using ASCII art without providing a text alternative </a> | <a href="https://www.w3.org/WAI/WCAG21/Techniques/html/H46.html">H46: Using noembed with embed </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C18.html">C18: Using CSS margin and padding rules instead of spacer images for layout design </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/silverlight/SL19.html">SL19: Providing User Instructions With AutomationProperties.HelpText in Silverlight </a> | |
| 1.2.1 Audio-only and Video-only (Prerecorded)Level A | For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such: Show Hide full descriptionPrerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.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. | Situation A: If the content is prerecorded audio-only: G158: Providing an alternative for time-based media for audio-only content SL17: Providing Static Alternative Content for Silverlight Media Playing in a MediaElement | Situation B: If the content is prerecorded video-only: G159: Providing an alternative for time-based media for video-only content G166: Providing audio that describes the important video content and describing it as such SL17: Providing Static Alternative Content for Silverlight Media Playing in a MediaElement | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F30.html">F30: Failure of Success Criterion 1.1.1 and 1.2.1 due to using text alternatives that are not alternatives (e.g., filenames or placeholder text) </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F67.html">F67: Failure of Success Criterion 1.1.1 and 1.2.1 due to providing long descriptions for non-text content that does not serve the same purpose or does not present the same information </a> | <a href="https://www.w3.org/WAI/WCAG21/Techniques/html/H96.html">H96: Using the track element to provide audio descriptions </a> | |||||
| 1.2.2 Captions (Prerecorded)Level A | 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. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F8.html">F8: Failure of Success Criterion 1.2.2 due to captions omitting some dialogue or important sound effects </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F75.html">F75: Failure of Success Criterion 1.2.2 by providing synchronized media without captions when the synchronized media presents more information than is presented on the page </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F74.html">F74: Failure of Success Criterion 1.2.2 and 1.2.8 due to not labeling a synchronized media alternative to text as an alternative </a> | ||||||||
| 1.2.3 Audio Description or Media Alternative (Prerecorded)Level A | 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. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/html/H96.html">H96: Using the track element to provide audio descriptions </a> | ||||||||
| 1.2.4 Captions (Live)Level AA | Captions are provided for all live audio content in synchronized media. | |||||||||
| 1.2.5 Audio Description (Prerecorded)Level AA | Audio description is provided for all prerecorded video content in synchronized media. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/html/H96.html">H96: Using the track element to provide audio descriptions </a> | ||||||||
| 1.2.6 Sign Language (Prerecorded)Level AAA | Sign language interpretation is provided for all prerecorded audio content in synchronized media. | |||||||||
| 1.2.7 Extended Audio Description (Prerecorded)Level AAA | 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. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/html/H96.html">H96: Using the track element to provide audio descriptions </a> | ||||||||
| 1.2.8 Media Alternative (Prerecorded)Level AAA | An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media. | Situation A: If the content is prerecorded synchronized media: G69: Providing an alternative for time based media G58: Placing a link to the alternative for time-based media immediately next to the non-text content SL17: Providing Static Alternative Content for Silverlight Media Playing in a MediaElement Linking to the alternative for time-based media using one of the following techniques H53: Using the body of the object element | Situation B: If the content is prerecorded video-only: G159: Providing an alternative for time-based media for video-only content | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F74.html">F74: Failure of Success Criterion 1.2.2 and 1.2.8 due to not labeling a synchronized media alternative to text as an alternative </a> | <a href="https://www.w3.org/WAI/WCAG21/Techniques/html/H46.html">H46: Using noembed with embed </a> | |||||
| 1.2.9 Audio-only (Live)Level AAA | An alternative for time-based media that presents equivalent information for live audio-only content is provided. | |||||||||
| 1.3.1 Info and RelationshipsLevel A | Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. | Situation A: The technology provides semantic structure to make information and relationships conveyed through presentation programmatically determinable: ARIA11: Using ARIA landmarks to identify regions of a page ARIA12: Using role=heading to identify headings ARIA13: Using aria-labelledby to name regions and landmarks ARIA16: Using aria-labelledby to provide a name for user interface controls ARIA17: Using grouping roles to identify related form controls ARIA20: Using the region role to identify a region of the page G115: Using semantic elements to mark up structure AND H49: Using semantic markup to mark emphasized or special text G117: Using text to convey information that is conveyed by variations in presentation of text G140: Separating information and structure from presentation to enable different presentations ARIA24: Semantically identifying a font icon with role="img" Making information and relationships conveyed through presentation programmatically determinable using the following techniques: G138: Using semantic markup whenever color cues are used H51: Using table markup to present tabular information PDF6: Using table elements for table markup in PDF Documents PDF20: Using Adobe Acrobat Pro's Table Editor to repair mistagged tables H39: Using caption elements to associate data table captions with data tables FLASH31: Specifying caption text for a DataGrid H73: Using the summary attribute of the table element to give an overview of data tables FLASH23: Adding summary information to a DataGrid H63: Using the scope attribute to associate header cells and data cells in data tables H43: Using id and headers attributes to associate data cells with header cells in data tables FLASH21: Using the DataGrid component to associate column headers with cells H44: Using label elements to associate text labels with form controls H65: Using the title attribute to identify form controls when the label element cannot be used PDF10: Providing labels for interactive form controls in PDF documents PDF12: Providing name, role, value information for form fields in PDF documents FLASH32: Using auto labeling to associate text labels with form controls FLASH29: Setting the label property for form components FLASH25: Labeling a form control by setting its accessible name H71: Providing a description for groups of form controls using fieldset and legend elements SL20: Relying on Silverlight AutomationPeer Behavior to Set AutomationProperties.Name SL26: Using LabeledBy to Associate Labels and Targets in Silverlight H85: Using OPTGROUP to group OPTION elements inside a SELECT H48: Using ol, ul and dl for lists or groups of links H42: Using h1-h6 to identify headings PDF9: Providing headings by marking content with heading tags in PDF documents SCR21: Using functions of the Document Object Model (DOM) to add content to a page PDF11: Providing links and link text using the Link annotation and the /Link structure element in PDF documents PDF17: Specifying consistent page numbering for PDF documents PDF21: Using List tags for lists in PDF documents H97: Grouping related links using the nav element | Situation B: The technology in use does NOT provide the semantic structure to make the information and relationships conveyed through presentation programmatically determinable: G117: Using text to convey information that is conveyed by variations in presentation of text FLASH8: Adding a group name to the accessible name of a form control Making information and relationships conveyed through presentation programmatically determinable or available in text using the following techniques: T1: Using standard text formatting conventions for paragraphs T2: Using standard text formatting conventions for lists T3: Using standard text formatting conventions for headings | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F2.html">F2: Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F33.html">F33: Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to create multiple columns in plain text content </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F34.html">F34: Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to format tables in plain text content </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F42.html">F42: Failure of Success Criteria 1.3.1, 2.1.1, 2.1.3, or 4.1.2 when emulating links </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F43.html">F43: Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F46.html">F46: Failure of Success Criterion 1.3.1 due to using th elements, layout tables </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F48.html">F48: Failure of Success Criterion 1.3.1 due to using the pre element to markup tabular information </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F87.html">F87: Failure of Success Criterion 1.3.1 due to inserting non-decorative content by using :before and :after pseudo-elements and the 'content' property in CSS </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F90.html">F90: Failure of Success Criterion 1.3.1 for incorrectly associating table headers and content via the headers and id attributes </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F91.html">F91: Failure of Success Criterion 1.3.1 for not correctly marking up table headers </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F92.html">F92: Failure of Success Criterion 1.3.1 due to the use of role presentation on content which conveys semantic information </a> | <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C22.html">C22: Using CSS to control visual presentation of text </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G162.html">G162: Positioning labels to maximize predictability of relationships </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA1.html">ARIA1: Using the aria-describedby property to provide a descriptive label for user interface controls </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA2.html">ARIA2: Identifying a required field with the aria-required property </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G141.html">G141: Organizing a page using headings </a> | |||||
| 1.3.2 Meaningful SequenceLevel A | When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F34.html">F34: Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to format tables in plain text content </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F33.html">F33: Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to create multiple columns in plain text content </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F32.html">F32: Failure of Success Criterion 1.3.2 due to using white space characters to control spacing within a word </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F49.html">F49: Failure of Success Criterion 1.3.2 due to using an HTML layout table that does not make sense when linearized </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F1.html">F1: Failure of Success Criterion 1.3.2 due to changing the meaning of content by positioning information with CSS </a> | ||||||||
| 1.3.3 Sensory CharacteristicsLevel A | 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 1: For requirements related to color, refer to Guideline 1.4. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F14.html">F14: Failure of Success Criterion 1.3.3 due to identifying content only by its shape or location </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F26.html">F26: Failure of Success Criterion 1.3.3 due to using a graphical symbol alone to convey information </a> | ||||||||
| 1.3.4 OrientationLevel AA(Added in 2.1) | 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. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F97.html">F97: Failure due to locking the orientation to landscape or portrait view </a> | ||||||||
| 1.3.5 Identify Input PurposeLevel AA(Added in 2.1) | The purpose of each input field collecting information about the user can be programmatically determined when: Show Hide full descriptionThe input field serves a purpose identified in the Input Purposes for User Interface Components section; andThe content is implemented using technologies with support for identifying the expected meaning for form input data. | |||||||||
| 1.3.6 Identify PurposeLevel AAA(Added in 2.1) | In content implemented using markup languages, the purpose of User Interface Components, icons, and regions can be programmatically determined. | Enable user agents to find the version of the content that best fits their needs. Using semantics to identify important features (coga-simplification="simplest"). Use of aria-invalid and aria-required. | ||||||||
| 1.4.1 Use of ColorLevel A | Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.Note 1: 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. | Situation A: If the color of particular words, backgrounds, or other content is used to indicate information: G14: Ensuring that information conveyed by color differences is also available in text G205: Including a text cue for colored form control labels G182: Ensuring that additional visual cues are available when text color differences are used to convey information G183: Using a contrast ratio of 3:1 with surrounding text and providing additional visual cues on focus for links or controls where color alone is used to identify them | Situation B: If color is used within an image to convey information: G111: Using color and pattern G14: Ensuring that information conveyed by color differences is also available in text | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F13.html">F13: Failure of Success Criterion 1.1.1 and 1.4.1 due to having a text alternative that does not include information that is conveyed by color differences in the image </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F73.html">F73: Failure of Success Criterion 1.4.1 due to creating links that are not visually evident without color vision </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F81.html">F81: Failure of Success Criterion 1.4.1 due to identifying required or error fields using color differences only </a> | <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C15.html">C15: Using CSS to change the presentation of a user interface component when it receives focus </a> | |||||
| 1.4.2 Audio ControlLevel A | 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 1: 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. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F23.html">F23: Failure of 1.4.2 due to playing a sound longer than 3 seconds where there is no mechanism to turn it off </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F93.html">F93: Failure of Success Criterion 1.4.2 for absence of a way to pause or stop an HTML5 media element that autoplays </a> | ||||||||
| 1.4.3 Contrast (Minimum)Level AA | The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: Show Hide full descriptionLarge Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1;Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.Logotypes: Text that is part of a logo or brand name has no contrast requirement. | Situation A: text is less than 18 point if not bold and less than 14 point if bold G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text G148: Not specifying background color, not specifying text color, and not using technology features that change those defaults G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast SL13: Providing A Style Switcher To Switch To High Contrast | Situation B: text is at least 18 point if not bold and at least 14 point if bold G145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text G148: Not specifying background color, not specifying text color, and not using technology features that change those defaults G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast SL13: Providing A Style Switcher To Switch To High Contrast | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F24.html">F24: Failure of Success Criterion 1.4.3, 1.4.6 and 1.4.8 due to specifying foreground colors without specifying background colors or vice versa </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F83.html">F83: Failure of Success Criterion 1.4.3 and 1.4.6 due to using background images that do not provide sufficient contrast with foreground text (or images of text) </a> | <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G156.html">G156: Using a technology that has commonly-available user agents that can change the foreground and background of blocks of text </a> | |||||
| 1.4.4 Resize textLevel AA | Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F69.html">F69: Failure of Success Criterion 1.4.4 when resizing visually rendered text up to 200 percent causes the text, image or controls to be clipped, truncated or obscured </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F80.html">F80: Failure of Success Criterion 1.4.4 when text-based form controls do not resize when visually rendered text is resized up to 200% </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F94.html">F94: Failure of Success Criterion 1.4.4 due to text sized in viewport units </a> | <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C17.html">C17: Scaling form elements which contain text </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C20.html">C20: Using relative measurements to set column widths so that lines can average 80 characters or less when the browser is resized </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C22.html">C22: Using CSS to control visual presentation of text </a> | |||||||
| 1.4.5 Images of TextLevel AA | If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: Show Hide full descriptionCustomizable: The image of text can be visually customized to the user's requirements;Essential: A particular presentation of text is essential to the information being conveyed.Note 1: Logotypes (text that is part of a logo or brand name) are considered essential. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C12.html">C12: Using percent for font sizes </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C13.html">C13: Using named font sizes </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C14.html">C14: Using em units for font sizes </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C8.html">C8: Using CSS letter-spacing to control spacing within a word </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C6.html">C6: Positioning content based on structural markup </a> | ||||||||
| 1.4.6 Contrast (Enhanced)Level AAA | The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following: Show Hide full descriptionLarge Text: Large-scale text and images of large-scale text have a contrast ratio of at least 4.5:1;Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.Logotypes: Text that is part of a logo or brand name has no contrast requirement. | Situation A: text is less than 18 point if not bold and less than 14 point if bold G17: Ensuring that a contrast ratio of at least 7:1 exists between text (and images of text) and background behind the text G148: Not specifying background color, not specifying text color, and not using technology features that change those defaults G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast SL13: Providing A Style Switcher To Switch To High Contrast | Situation B: text is as least 18 point if not bold and at least 14 point if bold G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text G148: Not specifying background color, not specifying text color, and not using technology features that change those defaults G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast SL13: Providing A Style Switcher To Switch To High Contrast | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F24.html">F24: Failure of Success Criterion 1.4.3, 1.4.6 and 1.4.8 due to specifying foreground colors without specifying background colors or vice versa </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F83.html">F83: Failure of Success Criterion 1.4.3 and 1.4.6 due to using background images that do not provide sufficient contrast with foreground text (or images of text) </a> | <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G156.html">G156: Using a technology that has commonly-available user agents that can change the foreground and background of blocks of text </a> | |||||
| 1.4.7 Low or No Background AudioLevel AAA | For prerecorded audio-only content that (1) contains primarily speech in the foreground, (2) is not an audio CAPTCHA or audio logo, and (3) is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true: Show Hide full descriptionNo Background: The audio does not contain background sounds.Turn Off: The background sounds can be turned off.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. Per the definition of "decibel," background sound that meets this requirement will be approximately four times quieter than the foreground speech content. | |||||||||
| 1.4.8 Visual PresentationLevel AAA | For the visual presentation of blocks of text, a mechanism is available to achieve the following: Show Hide full descriptionForeground and background colors can be selected by the user.Width is no more than 80 characters or glyphs (40 if CJK).Text is not justified (aligned to both the left and the right margins).Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing.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. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F24.html">F24: Failure of Success Criterion 1.4.3, 1.4.6 and 1.4.8 due to specifying foreground colors without specifying background colors or vice versa </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F88.html">F88: Failure of Success Criterion 1.4.8 due to using text that is justified (aligned to both the left and the right margins) </a> | ||||||||
| 1.4.9 Images of Text (No Exception)Level AAA | Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed.Note 1: Logotypes (text that is part of a logo or brand name) are considered essential. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C12.html">C12: Using percent for font sizes </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C13.html">C13: Using named font sizes </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C14.html">C14: Using em units for font sizes </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C8.html">C8: Using CSS letter-spacing to control spacing within a word </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C6.html">C6: Positioning content based on structural markup </a> | ||||||||
| 1.4.10 ReflowLevel AA(Added in 2.1) | Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: Show Hide full descriptionVertical scrolling content at a width equivalent to 320 CSS pixels;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. | @@ Using fixed sized containers and fixed position content (CSS) @@ (HTML) Using preformatted text or excluding preformatting text as an exception to no two dimensional scrolling. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C34.html">C34: Using media queries to un-fixing sticky headers / footers </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C37.html">C37: Using CSS max-width and height to fit images </a> @@ CSS, Reflowing simple data tables. @@ CSS, Fitting data cells within the width of the viewport. @@ Mechanism to allow mobile view at any time | |||||||
| 1.4.11 Non-text ContrastLevel AA(Added in 2.1) | The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s): Show Hide full descriptionUser Interface Components: Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F78.html">F78: Failure of Success Criterion 2.4.7 due to styling element outlines and borders in a way that removes or renders non-visible the visual focus indicator </a> | <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G183.html">G183: Using a contrast ratio of 3:1 with surrounding text and providing additional visual cues on focus for links or controls where color alone is used to identify them </a> | |||||||
| 1.4.12 Text SpacingLevel AA(Added in 2.1) | In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: Show Hide full descriptionLine height (line spacing) to at least 1.5 times the font size;Spacing following paragraphs to at least 2 times the font size;Letter spacing (tracking) to at least 0.12 times the font size;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. | Failure of Success Criterion 1.4.12 due to not allowing for spacing override. (Future technique) | <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C8.html">C8: Using CSS letter-spacing to control spacing within a word </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C21.html">C21: Specifying line spacing in CSS </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C28.html">C28: Specifying the size of text containers using em units </a> | |||||||
| 1.4.13 Content on Hover or FocusLevel AA(Added in 2.1) | Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true: Show Hide full descriptionDismissible: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;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. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F95.html">F95: Failure of Success Criterion 1.4.13 due to content shown on hover not being hoverable </a> @@ Failure to make content dismissable without moving pointer hover or keyboard focus @@ Failure to meet by content on hover or focus not remaining visible until dismissed or invalid | ||||||||
| 2.1.1 KeyboardLevel A | 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. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F54.html">F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F55.html">F55: Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F42.html">F42: Failure of Success Criteria 1.3.1, 2.1.1, 2.1.3, or 4.1.2 when emulating links </a> | <a href="https://www.w3.org/WAI/WCAG21/Techniques/client-side-script/SCR29.html">SCR29: Adding keyboard-accessible actions to static HTML elements </a> | |||||||
| 2.1.2 No Keyboard TrapLevel A | 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 1: 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. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F10.html">F10: Failure of Success Criterion 2.1.2 and Conformance Requirement 5 due to combining multiple content formats in a way that traps users inside one format type </a> | ||||||||
| 2.1.3 Keyboard (No Exception)Level AAA | All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. | |||||||||
| 2.1.4 Character Key ShortcutsLevel A(Added in 2.1) | If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true: Show Hide full descriptionTurn off: A mechanism is available to turn the shortcut off;Remap: A mechanism is available to remap the shortcut to include one or more non-printable keyboard keys (e.g., Ctrl, Alt);Active only on focus: The keyboard shortcut for a user interface component is only active when that component has focus. | Failure of Success Criteria 2.1.4 due to a webpage or web app that includes single-key shortcuts not including a control that allows users to turn the shortcuts off or a control that allows users to change the shortcuts to key combinations that include keys that are not upper or lower-case letters, punctuation, number, or symbol characters. | ||||||||
| 2.2.1 Timing AdjustableLevel A | For each time limit that is set by the content, at least one of the following is true: Show Hide full descriptionTurn off: The user is allowed to turn off the time limit before encountering it; orAdjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; orExtend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example,"press the space bar"), and the user is allowed to extend the time limit at least ten times; orReal-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; orEssential Exception: The time limit is essential and extending it would invalidate the activity; or20 Hour Exception: The time limit is longer than 20 hours. | Situation A: If there are session time limits: G133: Providing a checkbox on the first page of a multipart form that allows users to ask for longer session time limit or no session time limit G198: Providing a way for the user to turn the time limit off | Situation B: If a time limit is controlled by a script on the page: G198: Providing a way for the user to turn the time limit off G180: Providing the user with a means to set the time limit to 10 times the default time limit SCR16: Providing a script that warns the user a time limit is about to expire AND SCR1: Allowing the user to extend the default time limit FLASH19: Providing a script that warns the user a time limit is about to expire and provides a way to extend it FLASH24: Allowing the user to extend the default time limit SL21: Replacing A Silverlight Timed Animation With a Nonanimated Element | Situation C: If there are time limits on reading: G4: Allowing the content to be paused and restarted from where it was paused G198: Providing a way for the user to turn the time limit off SCR33: Using script to scroll content, and providing a mechanism to pause it SCR36: Providing a mechanism to allow users to display moving, scrolling, or auto-updating text in a static window or area | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F40.html">F40: Failure of Success Criterion 2.2.1 and 2.2.4 due to using meta redirect with a time limit </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F41.html">F41: Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh to reload the page </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F58.html">F58: Failure of Success Criterion 2.2.1 due to using server-side techniques to automatically redirect pages after a time-out </a> | |||||
| 2.2.2 Pause, Stop, HideLevel A | For moving, blinking, scrolling, or auto-updating information, all of the following are true: Show Hide full descriptionMoving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; andAuto-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. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F16.html">F16: Failure of Success Criterion 2.2.2 due to including scrolling content where movement is not essential to the activity without also including a mechanism to pause and restart the content </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F47.html">F47: Failure of Success Criterion 2.2.2 due to using the blink element </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F4.html">F4: Failure of Success Criterion 2.2.2 due to using text-decoration:blink without a mechanism to stop it in less than five seconds </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F50.html">F50: Failure of Success Criterion 2.2.2 due to a script that causes a blink effect without a mechanism to stop the blinking at 5 seconds or less </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F7.html">F7: Failure of Success Criterion 2.2.2 due to an object or applet, such as Java or Flash, for more than five seconds </a> | ||||||||
| 2.2.3 No TimingLevel AAA | 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. | |||||||||
| 2.2.4 InterruptionsLevel AAA | Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F40.html">F40: Failure of Success Criterion 2.2.1 and 2.2.4 due to using meta redirect with a time limit </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F41.html">F41: Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh to reload the page </a> | ||||||||
| 2.2.5 Re-authenticatingLevel AAA | When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F12.html">F12: Failure of Success Criterion 2.2.5 due to having a session time limit without a mechanism re-authentication </a> | ||||||||
| 2.2.6 TimeoutsLevel AAA(Added in 2.1) | 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. | |||||||||
| 2.3.1 Three Flashes or Below ThresholdLevel A | 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 1: 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. | |||||||||
| 2.3.2 Three FlashesLevel AAA | Web pages do not contain anything that flashes more than three times in any one second period. | |||||||||
| 2.3.3 Animation from InteractionsLevel AAA(Added in 2.1) | Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed. | |||||||||
| 2.4.1 Bypass BlocksLevel A | A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C6.html">C6: Positioning content based on structural markup </a> | ||||||||
| 2.4.2 Page TitledLevel A | Web pages have titles that describe topic or purpose. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F25.html">F25: Failure of Success Criterion 2.4.2 due to the title of a Web page not identifying the contents </a> | <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G127.html">G127: Identifying a Web page's relationship to a larger collection of Web pages </a> | |||||||
| 2.4.3 Focus OrderLevel A | 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. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F44.html">F44: Failure of Success Criterion 2.4.3 due to using tabindex to create a tab order that does not preserve meaning and operability </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F85.html">F85: Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order </a> | ||||||||
| 2.4.4 Link Purpose (In Context)Level A | 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. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F63.html">F63: Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F89.html">F89: Failure of Success Criteria 2.4.4, 2.4.9 and 4.1.2 due to not providing an accessible name for an image which is the only content in a link </a> | <a href="https://www.w3.org/WAI/WCAG21/Techniques/html/H2.html">H2: Combining adjacent image and text links for the same resource </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/flash/FLASH5.html">FLASH5: Combining adjacent image and text buttons for the same resource </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/html/H80.html">H80: Identifying the purpose of a link using link text combined with the preceding heading element </a> | |||||||
| 2.4.5 Multiple WaysLevel AA | 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. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/html/H59.html">H59: Using the link element and navigation tools </a> | ||||||||
| 2.4.6 Headings and LabelsLevel AA | Headings and labels describe topic or purpose. | |||||||||
| 2.4.7 Focus VisibleLevel AA | Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F55.html">F55: Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F78.html">F78: Failure of Success Criterion 2.4.7 due to styling element outlines and borders in a way that removes or renders non-visible the visual focus indicator </a> | ||||||||
| 2.4.8 LocationLevel AAA | Information about the user's location within a set of Web pages is available. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/pdf/PDF14.html">PDF14: Providing running headers and footers in PDF documents </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/pdf/PDF17.html">PDF17: Specifying consistent page numbering for PDF documents </a> | ||||||||
| 2.4.9 Link Purpose (Link Only)Level AAA | 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. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F84.html">F84: Failure of Success Criterion 2.4.9 due to using a non-specific link such as "click here" or "more" without a mechanism to change the link text to specific text. </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F89.html">F89: Failure of Success Criteria 2.4.4, 2.4.9 and 4.1.2 due to not providing an accessible name for an image which is the only content in a link </a> | <a href="https://www.w3.org/WAI/WCAG21/Techniques/html/H2.html">H2: Combining adjacent image and text links for the same resource </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/flash/FLASH5.html">FLASH5: Combining adjacent image and text buttons for the same resource </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/html/H33.html">H33: Supplementing link text with the title attribute </a> | |||||||
| 2.4.10 Section HeadingsLevel AAA | 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. | |||||||||
| 2.5.1 Pointer GesturesLevel A(Added in 2.1) | 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. | Functionality can be operated by pointer input but not with single-point activation alone | ||||||||
| 2.5.2 Pointer CancellationLevel A(Added in 2.1) | For functionality that can be operated using a single pointer, at least one of the following is true: Show Hide full descriptionNo Down-Event: The down-event of the pointer is not used to execute any part of the function;Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;Up Reversal: The up-event reverses any outcome of the preceding down-event;Essential: Completing the function on the down-event is essential. | @@ Failure of SC 2.5.3 due to activating a button on initial touch location rather than the final touch location. | ||||||||
| 2.5.3 Label in NameLevel A(Added in 2.1) | For user interface components with labels that include text or images of text, the name contains the text that is presented visually. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F96.html">F96: Failure due to the accessible name not containing the visible label text </a> @@ Accessible name contains the visible label text, but the words of the visible label are not in the same order as they are in the visible label text @@ Accessible name contains the visible label text, but one or more other words are interspersed in the label | @@ If an icon has no accompanying text, consider using its hover text as its accessible name | |||||||
| 2.5.4 Motion ActuationLevel A(Added in 2.1) | Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when: Show Hide full descriptionSupported Interface: The motion is used to operate functionality through an accessibility supported interface;Essential: The motion is essential for the function and doing so would invalidate the activity. | FXXX: Failure of Success Criterion 2.5.4 due to functionality that can only be activated via devicemotion events (e.g., shaking or tilting) FXXX: Failure of Success Criterion 2.5.4 due to an inability to disable motion actuation FXXX: Failure of Success Criterion 2.5.4 due to disrupting or disabling system level features which allow the user to disable motion actuation | ||||||||
| 2.5.5 Target SizeLevel AAA(Added in 2.1) | The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when: Show Hide full descriptionEquivalent: The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels;Inline: The target is in a sentence or block of text;User Agent Control: The size of the target is determined by the user agent and is not modified by the author;Essential: A particular presentation of the target is essential to the information being conveyed. | Failure of success criterion 2.5.3 due to target size being less than 44 by 44 CSS pixels. Failure of success criterion 2.5.3 due to target size of a paragraph that is also a link being less than 44 x 44 CSS pixels. | Ensuring inline links provide sufficiently large activation target. | |||||||
| 2.5.6 Concurrent Input MechanismsLevel AAA(Added in 2.1) | 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. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F98.html">F98: Failure due to interactions being limited to touch-only on touchscreen devices </a> | ||||||||
| 3.1.1 Language of PageLevel A | The default human language of each Web page can be programmatically determined. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/server-side-script/SVR5.html">SVR5: Specifying the default language in the HTTP header </a> | ||||||||
| 3.1.2 Language of PartsLevel AA | 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. | a href="https://www.w3.org/WAI/WCAG21/Techniques/silverlight/SL27.html">SL27: Using Language/Culture Properties as Exposed by Silverlight Applications and Assistive Technologies </a> | ||||||||
| 3.1.3 Unusual WordsLevel AAA | A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. | Situation A: If the word or phrase has a unique meaning within the Web page: G101: Providing the definition of a word or phrase used in an unusual or restricted way G55: Linking to definitions H40: Using description lists H60: Using the link element to link to a glossary G112: Using inline definitions H54: Using the dfn element to identify the defining instance of a word G101: Providing the definition of a word or phrase used in an unusual or restricted way G55: Linking to definitions H40: Using description lists H60: Using the link element to link to a glossary G62: Providing a glossary G70: Providing a function to search an online dictionary | Situation B: If the word or phrase means different things within the same Web page: G101: Providing the definition of a word or phrase used in an unusual or restricted way G55: Linking to definitions H40: Using description lists H60: Using the link element to link to a glossary G112: Using inline definitions H54: Using the dfn element to identify the defining instance of a word | |||||||
| 3.1.4 AbbreviationsLevel AAA | A mechanism for identifying the expanded form or meaning of abbreviations is available. | Situation A: If the abbreviation has only one meaning within the Web page: G102: Providing the expansion or explanation of an abbreviation G97: Providing the first use of an abbreviation immediately before or after the expanded form G55: Linking to definitions H28: Providing definitions for abbreviations by using the abbr element PDF8: Providing definitions for abbreviations via an E entry for a structure element G102: Providing the expansion or explanation of an abbreviation G55: Linking to definitions G62: Providing a glossary H60: Using the link element to link to a glossary G70: Providing a function to search an online dictionary H28: Providing definitions for abbreviations by using the abbr element PDF8: Providing definitions for abbreviations via an E entry for a structure element | Situation B: If the abbreviation means different things within the same Web page: G102: Providing the expansion or explanation of an abbreviation G55: Linking to definitions H28: Providing definitions for abbreviations by using the abbr element PDF8: Providing definitions for abbreviations via an E entry for a structure element | |||||||
| 3.1.5 Reading LevelLevel AAA | 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. | |||||||||
| 3.1.6 PronunciationLevel AAA | A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation. | |||||||||
| 3.2.1 On FocusLevel A | When any user interface component receives focus, it does not initiate a change of context. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F55.html">F55: Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received </a> | <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G200.html">G200: Opening new windows and tabs from a link only when necessary </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G201.html">G201: Giving users advanced warning when opening a new window </a> | |||||||
| 3.2.2 On InputLevel A | 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. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F36.html">F36: Failure of Success Criterion 3.2.2 due to automatically submitting a form and given a value </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F37.html">F37: Failure of Success Criterion 3.2.2 due to launching a new window without prior warning when the selection of a radio button, check box or select list is changed </a> | <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G201.html">G201: Giving users advanced warning when opening a new window </a> | |||||||
| 3.2.3 Consistent NavigationLevel AA | 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. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F66.html">F66: Failure of Success Criterion 3.2.3 due to presenting navigation links in a different relative order on different pages </a> | <a href="https://www.w3.org/WAI/WCAG21/Techniques/pdf/PDF14.html">PDF14: Providing running headers and footers in PDF documents </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/pdf/PDF17.html">PDF17: Specifying consistent page numbering for PDF documents </a> | |||||||
| 3.2.4 Consistent IdentificationLevel AA | Components that have the same functionality within a set of Web pages are identified consistently. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F31.html">F31: Failure of Success Criterion 3.2.4 due to using two different labels for the same function on different Web pages within a set of Web pages </a> | ||||||||
| 3.2.5 Change on RequestLevel AAA | Changes of context are initiated only by user request or a mechanism is available to turn off such changes. | Situation A: If the Web page allows automatic updates: G76: Providing a mechanism to request an update of the content instead of updating automatically | Situation B: If automatic redirects are possible: SVR1: Implementing automatic redirects on the server side instead of on the client side G110: Using an instant client-side redirect H76: Using meta refresh to create an instant client-side redirect | Situation C: If the Web page uses pop-up windows: Including pop-up windows using one of the following techniques: H83: Using the target attribute to open a new window on user request and indicating this in link text SCR24: Using progressive enhancement to open new windows on user request | Situation D: If using an onchange event on a select element: SCR19: Using an onchange event on a select element without causing a change of context | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F60.html">F60: Failure of Success Criterion 3.2.5 due to launching a new window when a user enters text into an input field </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F61.html">F61: Failure of Success Criterion 3.2.5 due to complete change of main content through an automatic update that the user cannot disable from within the content </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F9.html">F9: Failure of Success Criterion 3.2.5 due to changing the context when the user removes focus from a form element </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F22.html">F22: Failure of Success Criterion 3.2.5 due to opening windows that are not requested by the user </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F52.html">F52: Failure of Success Criterion 3.2.1 and 3.2.5 due to opening a new window as soon as a new page is loaded </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F41.html">F41: Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh to reload the page </a> | <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G200.html">G200: Opening new windows and tabs from a link only when necessary </a> | |||
| 3.3.1 Error IdentificationLevel A | 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. | Situation A: If a form contains fields for which information from the user is mandatory. G83: Providing text descriptions to identify required fields that were not completed ARIA21: Using Aria-Invalid to Indicate An Error Field SCR18: Providing client-side validation and alert PDF5: Indicating required form controls in PDF forms SL35: Using the Validation and ValidationSummary APIs to Implement Client Side Forms Validation in Silverlight | Situation B: If information provided by the user is required to be in a specific data format or of certain values. ARIA18: Using aria-alertdialog to Identify Errors ARIA19: Using ARIA role=alert or Live Regions to Identify Errors ARIA21: Using Aria-Invalid to Indicate An Error Field G84: Providing a text description when the user provides information that is not in the list of allowed values G85: Providing a text description when user input falls outside the required format or values SCR18: Providing client-side validation and alert SCR32: Providing client-side validation and adding error text via the DOM FLASH12: Providing client-side validation and adding error text via the accessible description PDF22: Indicating when user input falls outside the required format or values in PDF forms SL35: Using the Validation and ValidationSummary APIs to Implement Client Side Forms Validation in Silverlight | <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G139.html">G139: Creating a mechanism that allows users to jump to errors </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G199.html">G199: Providing success feedback when data is submitted successfully </a> | ||||||
| 3.3.2 Labels or InstructionsLevel A | Labels or instructions are provided when content requires user input. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F82.html">F82: Failure of Success Criterion 3.3.2 by visually formatting a set of phone number fields but not including a text label </a> | <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G13.html">G13: Describing what will happen before a change to a form control that causes a change of context to occur is made </a> a href="https://www.w3.org/WAI/WCAG21/Techniques/silverlight/SL19.html">SL19: Providing User Instructions With AutomationProperties.HelpText in Silverlight </a> | |||||||
| 3.3.3 Error SuggestionLevel AA | 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. | Situation A: If a mandatory field contains no information: G83: Providing text descriptions to identify required fields that were not completed ARIA2: Identifying a required field with the aria-required property PDF5: Indicating required form controls in PDF forms SL35: Using the Validation and ValidationSummary APIs to Implement Client Side Forms Validation in Silverlight | Situation B: If information for a field is required to be in a specific data format: ARIA18: Using aria-alertdialog to Identify Errors G85: Providing a text description when user input falls outside the required format or values G177: Providing suggested correction text SCR18: Providing client-side validation and alert SCR32: Providing client-side validation and adding error text via the DOM FLASH12: Providing client-side validation and adding error text via the accessible description PDF22: Indicating when user input falls outside the required format or values in PDF forms | Situation C: Information provided by the user is required to be one of a limited set of values: ARIA18: Using aria-alertdialog to Identify Errors G84: Providing a text description when the user provides information that is not in the list of allowed values G177: Providing suggested correction text SCR18: Providing client-side validation and alert SCR32: Providing client-side validation and adding error text via the DOM FLASH12: Providing client-side validation and adding error text via the accessible description PDF22: Indicating when user input falls outside the required format or values in PDF forms | <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G139.html">G139: Creating a mechanism that allows users to jump to errors </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G199.html">G199: Providing success feedback when data is submitted successfully </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/client-side-script/SCR18.html">SCR18: Providing client-side validation and alert </a> | |||||
| 3.3.4 Error Prevention (Legal, Financial, Data)Level AA | For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: Show Hide full descriptionReversible: Submissions are reversible.Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. | Situation A: If an application causes a legal transaction to occur, such as making a purchase or submitting an income tax return: G164: Providing a stated time within which an online request (or transaction) may be amended or canceled by the user after making the request G98: Providing the ability for the user to review and correct answers before submitting G155: Providing a checkbox in addition to a submit button | Situation B: If an action causes information to be deleted: G99: Providing the ability to recover deleted information G168: Requesting confirmation to continue with selected action G155: Providing a checkbox in addition to a submit button | Situation C: If the Web page includes a testing application: G98: Providing the ability for the user to review and correct answers before submitting G168: Requesting confirmation to continue with selected action | <a href="https://www.w3.org/WAI/WCAG21/Techniques/client-side-script/SCR18.html">SCR18: Providing client-side validation and alert </a> a href="https://www.w3.org/WAI/WCAG21/Techniques/silverlight/SL35.html">SL35: Using the Validation and ValidationSummary APIs to Implement Client Side Forms Validation in Silverlight </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G199.html">G199: Providing success feedback when data is submitted successfully </a> | |||||
| 3.3.5 HelpLevel AAA | Context-sensitive help is available. | Situation A: If a form requires text input: G71: Providing a help link on every Web page G193: Providing help by an assistant in the Web page G194: Providing spell checking and suggestions for text input G184: Providing text instructions at the beginning of a form or set of fields that describes the necessary input | Situation B: If a form requires text input in an expected data format: G89: Providing expected data format and example G184: Providing text instructions at the beginning of a form or set of fields that describes the necessary input | <a href="https://www.w3.org/WAI/WCAG21/Techniques/html/H89.html">H89: Using the title attribute to provide context-sensitive help </a> | ||||||
| 3.3.6 Error Prevention (All)Level AAA | For Web pages that require the user to submit information, at least one of the following is true: Show Hide full descriptionReversible: Submissions are reversible.Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. | |||||||||
| 4.1.1 ParsingLevel A | 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: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete. | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F70.html">F70: Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F77.html">F77: Failure of Success Criterion 4.1.1 due to duplicate values of type ID </a> | ||||||||
| 4.1.2 Name, Role, ValueLevel A | 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 1: 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. | Situation A: If using a standard user interface component in a markup language (e.g., HTML): ARIA14: Using aria-label to provide an invisible label where a visible label cannot be used ARIA16: Using aria-labelledby to provide a name for user interface controls G108: Using markup features to expose the name and role, allow user-settable properties to be directly set, and provide notification of changes H91: Using HTML form controls and links H44: Using label elements to associate text labels with form controls H64: Using the title attribute of the frame and iframe elements H65: Using the title attribute to identify form controls when the label element cannot be used H88: Using HTML according to spec | Situation B: If using script or code to re-purpose a standard user interface component in a markup language: Exposing the names and roles, allowing user-settable properties to be directly set, and providing notification of changes using one of the following techniques: ARIA16: Using aria-labelledby to provide a name for user interface controls | Situation C: If using a standard user interface component in a programming technology: G135: Using the accessibility API features of a technology to expose names and notification of changes FLASH32: Using auto labeling to associate text labels with form controls FLASH29: Setting the label property for form components FLASH30: Specifying accessible names for image buttons PDF10: Providing labels for interactive form controls in PDF documents PDF12: Providing name, role, value information for form fields in PDF documents SL26: Using LabeledBy to Associate Labels and Targets in Silverlight SL32: Using Silverlight Text Elements for Appropriate Accessibility Role | Situation D: If creating your own user interface component in a programming language: G10: Creating components using a technology that supports the accessibility notification of changes ARIA4: Using a WAI-ARIA role to expose the role of a user interface component ARIA5: Using WAI-ARIA state and property attributes to expose the state of a user interface component ARIA16: Using aria-labelledby to provide a name for user interface controls SL6: Defining a UI Automation Peer for a Custom Silverlight Control SL18: Providing Text Equivalent for Nontext Silverlight Controls With AutomationProperties.Name SL20: Relying on Silverlight AutomationPeer Behavior to Set AutomationProperties.Name SL30: Using Silverlight Control Compositing and AutomationProperties.Name | <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F59.html">F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML without providing a role for the control </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F15.html">F15: Failure of Success Criterion 4.1.2 due to implementing custom controls that do not use an accessibility API for the technology, or do so incompletely </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F20.html">F20: Failure of Success Criterion 1.1.1 and 4.1.2 due to not updating text alternatives when changes to non-text content occur </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F68.html">F68: Failure of Success Criterion 4.1.2 due to a user interface control not having a programmatically determined name </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F79.html">F79: Failure of Success Criterion 4.1.2 due to the focus state of a user interface component not being programmatically determinable or no notification of change of focus state available </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F86.html">F86: Failure of Success Criterion 4.1.2 due to not providing names for each part of a multi-part form field, such as a US telephone number </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F89.html">F89: Failure of Success Criteria 2.4.4, 2.4.9 and 4.1.2 due to not providing an accessible name for an image which is the only content in a link </a> | ||||
| 4.1.3 Status MessagesLevel AA(Added in 2.1) | 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. | Situation A: If a status message advises on the success or results of an action, or the state of an application: ARIA22: Using role=status to present status messages G199: Providing success feedback when data is submitted successfully | Situation B: If a status message conveys a suggestion, or a warning on the existence of an error: ARIA19: Using ARIA role=alert or Live Regions to Identify Errors G83: Providing text descriptions to identify required fields that were not completed G84: Providing a text description when the user provides information that is not in the list of allowed values G85: Providing a text description when user input falls outside the required format or values G177: Providing suggested correction text G194: Providing spell checking and suggestions for text input | Situation C: If a status message conveys information on the progress of a process: ARIA23: Using role=log to identify sequential information updates Using role="progressbar" (future link) ARIA22: Using role=status to present status messages AND G193: Providing help by an assistant in the Web page | Using role="alert" or aria-live="assertive" on content which is not important and time-sensitive (future link) Using a visibilitychange event to hide or display a document without switching the document's live regions between active and inactive (future link) | Using aria-live regions with chat clients (future link) Using role="marquee" (future link) Using role="timer" (future link) <a href="https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA18.html">ARIA18: Using aria-alertdialog to Identify Errors </a> <a href="https://www.w3.org/WAI/WCAG21/Techniques/client-side-script/SCR14.html">SCR14: Using scripts to make nonessential alerts optional </a> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment