sidereior/wcg-standards-adherence huggingface dataset:
Input Purposes for User Interface Components Permalink Referenced in: § 2.2.6 Timeouts Permalink Referenced in: § 1.2.3 Audio Description or Media Alternative (Prerecorded) § 1.2.5 Audio Description (Prerecorded) § 1.2.7 Extended Audio Description (Prerecorded) § 6. Glossary (2) (3) (4) (5) (6) (7) (8) Permalink Referenced in: § 1.2.1 Audio-only and Video-only (Prerecorded) § 1.2.8 Media Alternative (Prerecorded) Permalink Referenced in: § 6. Glossary Permalink Referenced in: § 1.4.5 Images of Text Permalink Referenced in: § 2.3.1 Three Flashes or Below Threshold § 2.3.2 Three Flashes § 2.4.1 Bypass Blocks § 2.4.2 Page Titled § 2.4.3 Focus Order § 2.4.5 Multiple Ways § 3.1.1 Language of Page § 3.2.3 Consistent Navigation § 3.2.6 Consistent Help § 3.3.4 Error Prevention (Legal, Financial, Data) § 3.3.6 Error Prevention (All) § 5.2.1 Conformance Level § 5.2.2 Full pages § 5.2.3 Complete processes § 5.2.5 Non-Interference § 5.3 Conformance Claims (Optional) § 6. Glossary (2) (3) (4) (5) (6) How to Meet WCAG (Quickref Reference) How to Meet WCAG (Quick Reference) A customizable quick reference to Web Content Accessibility Guidelines (WCAG) 2 requirements (success criteria) and techniques. Show Hide About & How to Use About This tool provides a customizable view of WCAG 2 resources: Web Content Accessibility Guidelines web standard — WCAG 2.2 , WCAG 2.1 , WCAG 2.0 Techniques for WCAG 2 implementation guidance Understanding WCAG 2 supporting information Background on these resources is provided in the WCAG Overview and The WCAG 2 documents .
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. Show Hide in-page navigation and filter options Hide Contents Filter 1. Perceivable 1.1 Text Alternatives 1.1.1 Non-text Content 1.2 Time-based Media 1.2.1 Audio-only and Video-only (Prerecorded) 1.2.2 Captions (Prerecorded) 1.2.3 Audio Description or Media Alternative (Prerecorded) 1.2.4 Captions (Live) 1.2.5 Audio Description (Prerecorded) 1.2.6 Sign Language (Prerecorded) 1.2.7 Extended Audio Description (Prerecorded) 1.2.8 Media Alternative (Prerecorded) 1.2.9 Audio-only (Live) 1.3 Adaptable 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.3.3 Sensory Characteristics 1.3.4 Orientation 1.3.5 Identify Input Purpose 1.3.6 Identify Purpose 1.4 Distinguishable 1.4.1 Use of C
olor 1.4.2 Audio Control 1.4.3 Contrast (Minimum) 1.4.4 Resize Text 1.4.5 Images of Text 1.4.6 Contrast (Enhanced) 1.4.7 Low or No Background Audio 1.4.8 Visual Presentation 1.4.9 Images of Text (No Exception) 1.4.10 Reflow 1.4.11 Non-text Contrast 1.4.12 Text Spacing 1.4.13 Content on Hover or Focus 2. Operable 2.1 Keyboard Accessible 2.1.1 Keyboard 2.1.2 No Keyboard Trap 2.1.3 Keyboard (No Exception) 2.1.4 Character Key Shortcuts 2.2 Enough Time 2.2.1 Timing Adjustable 2.2.2 Pause, Stop, Hide 2.2.3 No Timing 2.2.4 Interruptions 2.2.5 Re-authenticating 2.2.6 Timeouts 2.3 Seizures and Physical Reactions 2.3.1 Three Flashes or Below Threshold 2.3.2 Three Flashes 2.3.3 Animation from Interactions 2.4 Navigable 2.4.1 Bypass Blocks 2.4.2 Page Titled 2.4.3 Focus Order 2.4.4 Link Purpose (In Context) 2.4.5 Multiple Ways 2.4.6 Headings and Labels 2.4.7 Focus Visible 2.4.8 Location 2.4.9 Link Purpose (Link Only) 2.4.10 Section Headings 2.4.11 Focus Not Obscured (Minimum) 2.4.12 Focus Not Obscured (Enhanced) 2.4.13 Focus Appearance 2.5 Input Modalities 2.5.1 Pointer Gestures 2.5.2 Pointer Cancellation 2.5.3 Label in Name 2.5.4 Motion Actuation 2.5.5 Target Size (Enhanced) 2.5.6 Concurrent Input Mechanisms 2.5.7 Dragging Movements 2.5.8 Target Size (Minimum) 3.
Understandable 3.1 Readable 3.1.1 Language of Page 3.1.2 Language of Parts 3.1.3 Unusual Words 3.1.4 Abbreviations 3.1.5 Reading Level 3.1.6 Pronunciation 3.2 Predictable 3.2.1 On Focus 3.2.2 On Input 3.2.3 Consistent Navigation 3.2.4 Consistent Identification 3.2.5 Change on Request 3.2.6 Consistent Help 3.3 Input Assistance 3.3.1 Error Identification 3.3.2 Labels or Instructions 3.3.3 Error Suggestion 3.3.4 Error Prevention (Legal, Financial, Data) 3.3.5 Help 3.3.6 Error Prevention (All) 3.3.7 Redundant Entry 3.3.8 Accessible Authentication (Minimum) 3.3.9 Accessible Authentication (Enhanced) 4. Robust 4.1 Compatible 4.1.1 Parsing 4.1.2 Name, Role, Value 4.1.3 Status Messages Changing filters will change the listed Success Criteria and Techniques. WCAG Version WCAG 2.2 WCAG 2.1 WCAG 2.0 Only 2.2 Added Success Criteria Only 2.1 Added Success Criteria Note: Clear Filters will not change the selected version. Tags Clear tags Developing only Interaction Design only Content Creation only Visual Design only animation audio auto complete autoplay blinking buttons captcha captions carousels changing content color components consistent experience content contrast controls drag and drop errors events fixed flashing focus forms graphical objects headings help hidden content hover icons iframes images images of text interaction keyboard labels language layout links live stream logins markup media queries menus messaging meta tag mobile modals moving content navigation notifications orientation page title pop up positioning progress steps readability reflow regions screen size skip to content sticky streaming structure tab order tables text text alternatives time limits user interface video viewport visual cues zoom Show all tags Levels Select all Level A only Level AA only Level AAA only Techniques Select all Sufficient Techniques only Advisory Techniques only Failures only Technologies Select all HTML only CSS only ARIA only Client-side Scripting only Server-side Scripting only SMIL only PDF only Show Sidebar Loading Loaded Selected Filters: WCAG 2.2: all success criteria and all techniques. (What did the filter remove?) Clear filters Expand all sections Share Link to this view, with the filters you have selected: Shortcut to copy the link: ctrl + C or ⌘ C Close Principle 1 – Perceivable Information and user interface components must be presentable to users in ways they can perceive.
Guideline 1.1 – Text Alternatives Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. 1.1.1 Non-text Content Level 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. Controls, 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. Understanding 1.1.1 Show Hide techniques and failures for 1.1.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.1.1 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Situation A: If the content is prerecorded audio-only: G158: Providing an alternative for time-based media for audio-only content 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 Advisory Techniques for Success Criterion 1.2.1 H96: Using the track element to provide audio descriptions Failures for Success Criterion 1.2.1 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) 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 Back to top 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. Understanding 1.2.2 Show Hide techniques and failures for 1.2.2 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.2.2 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G93: Providing open (always visible) captions G87: Providing closed captions using any readily available media format that has a video player that supports closed captioning G87: Providing closed captions using any of the technology-specific techniques below SM11: Providing captions through synchronized text streams in SMIL 1.0 SM12: Providing captions through synchronized text streams in SMIL 2.0 H95: Using the track element to provide captions Failures for Success Criterion 1.2.2 F8: Failure of Success Criterion 1.2.2 due to captions omitting some dialogue or important sound effects 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 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 Back to top 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. Understanding 1.2.3 Show Hide techniques and failures for 1.2.3 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.2.3 Note: Other techniques may also be sufficient if they meet the success criterion.
See Understanding Techniques. G69: Providing an alternative for time based media using one of the following techniques G58: Placing a link to the alternative for time-based media immediately next to the non-text content Linking to the alternative for time-based media using one of the following techniques H53: Using the body of the object element G78: Providing a second, user-selectable, audio track that includes audio descriptions G173: Providing a version of a movie with audio descriptions SM6: Providing audio description in SMIL 1.0 SM7: Providing audio description in SMIL 2.0 Using any player that supports audio and video G8: Providing a movie with extended audio descriptions SM1: Adding extended audio description in SMIL 1.0 SM2: Adding extended audio description in SMIL 2.0 Using any player that supports audio and video G203: Using a static text alternative to describe a talking head video Advisory Techniques for Success Criterion 1.2.3 H96: Using the track element to provide audio descriptions Back to top 1.2.4 Captions (Live) Level AA Captions are provided for all live audio content in synchronized media. Understanding 1.2.4 Show Hide techniques and failures for 1.2.4 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.2.4 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G9: Creating captions for live synchronized media AND G93: Providing open (always visible) captions G9: Creating captions for live synchronized media AND G87: Providing closed captions G9: Creating captions for live synchronized media SM11: Providing captions through synchronized text streams in SMIL 1.0 SM12: Providing captions through synchronized text streams in SMIL 2.0 AND G87: Providing closed captions SM11: Providing captions through synchronized text streams in SMIL 1.0 SM12: Providing captions through synchronized text streams in SMIL 2.0 Back to top 1.2.5 Audio Description (Prerecorded) Level AA Audio description is provided for all prerecorded video content in synchronized media.
Understanding 1.2.5 Show Hide techniques and failures for 1.2.5 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.2.5 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G78: Providing a second, user-selectable, audio track that includes audio descriptions G173: Providing a version of a movie with audio descriptions SM6: Providing audio description in SMIL 1.0 SM7: Providing audio description in SMIL 2.0 Using any player that supports audio and video G8: Providing a movie with extended audio descriptions SM1: Adding extended audio description in SMIL 1.0 SM2: Adding extended audio description in SMIL 2.0 Using any player that supports audio and video G203: Using a static text alternative to describe a talking head video Advisory Techniques for Success Criterion 1.2.5 H96: Using the track element to provide audio descriptions Back to top 1.2.6 Sign Language (Prerecorded) Level AAA Sign language interpretation is provided for all prerecorded audio content in synchronized media. Understanding 1.2.6 Show Hide techniques and failures for 1.2.6 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.2.6 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
G54: Including a sign language interpreter in the video stream G81: Providing a synchronized video of the sign language interpreter that can be displayed in a different viewport or overlaid on the image by the player SM13: Providing sign language interpretation through synchronized video streams in SMIL 1.0 SM14: Providing sign language interpretation through synchronized video streams in SMIL 2.0 Back to top 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. Understanding 1.2.7 Show Hide techniques and failures for 1.2.7 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.2.7 Note: Other techniques may also be sufficient if they meet the success criterion. See Under
standing Techniques. G8: Providing a movie with extended audio descriptions SM1: Adding extended audio description in SMIL 1.0 SM2: Adding extended audio description in SMIL 2.0 Using any player that supports audio and video Advisory Techniques for Success Criterion 1.2.7 H96: Using the track element to provide audio descriptions Back to top 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. Understanding 1.2.8 Show Hide techniques and failures for 1.2.8 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.2.8 Note: Other techniques may also be sufficient if they meet the success criterion.
See Understanding Techniques. 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 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 Advisory Techniques for Success Criterion 1.2.8 H46: Using noembed with embed Failures for Success Criterion 1.2.8 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 Back to top 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. Understanding 1.2.9 Show Hide techniques and failures for 1.2.9 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.2.9 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G151: Providing a link to a text transcript of a prepared statement or script if the script is followed G150: Providing text based alternatives for live audio-only content G157: Incorporating a live audio captioning service into a Web page Back to top Guideline 1.3 – Adaptable Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
See Understanding Techniques. G57: Ordering the content in a meaningful sequence G57: Ordering the content in a meaningful sequence H34: Using a Unicode right-to-left mark (RLM) or left-to-right mark (LRM) to mix text direction inline H56: Using the dir attribute on an inline element to resolve problems with nested directional runs C6: Positioning content based on structural markup C8: Using CSS letter-spacing to control spacing within a word C27: Making the DOM order match the visual order PDF3: Ensuring correct tab and reading order in PDF documents Failures for Success Criterion 1.3.2 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 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 F32: Failure of Success Criterion 1.3.2 due to using white space characters to control spacing within a word F49: Failure of Success Criterion 1.3.2 due to using an HTML layout table that does not make sense when linearized F1: Failure of Success Criterion 1.3.2 due to changing the meaning of content by positioning information with CSS Back to top 1.3.3 Sensory Characteristics Level 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. Understanding 1.3.3 Show Hide techniques and failures for 1.3.3 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.3.3 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
G96: Providing textual ident
ification of items that otherwise rely only on sensory information to be understood Failures for Success Criterion 1.3.3 F14: Failure of Success Criterion 1.3.3 due to identifying content only by its shape or location F26: Failure of Success Criterion 1.3.3 due to using a graphical symbol alone to convey information Back to top 1.3.4 Orientation Level 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. Understanding 1.3.4 Show Hide techniques and failures for 1.3.4 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.3.4 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G214: Using a control to allow access to content in different orientations which is otherwise restricted Failures for Success Criterion 1.3.4 F97: Failure due to locking the orientation to landscape or portrait view F100: Failure of Success Criterion 1.3.4 due to showing a message asking to reorient device Back to top 1.3.5 Identify Input Purpose Level AA (Added in 2.1) The purpose of each input field collecting information about the user can be programmatically determined when: The input field serves a purpose identified in the Input Purposes for User Interface Components section; and The content is implemented using technologies with support for identifying the expected meaning for form input data. Understanding 1.3.5 Back to top 1.3.6 Identify Purpose Level AAA (Added in 2.1) In content implemented using markup languages, the purpose of user interface components, icons, and regions can be programmatically determined.
Understanding 1.3.6 Show Hide techniques and failures for 1.3.6 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.3.6 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. Programmatically indicating the purpose of icons, regions and user interface components ARIA11: Using ARIA landmarks to identify regions of a page Using microdata to markup user interface components (future link) Advisory Techniques for Success Criterion 1.3.6 Enabling user agents to find the version of the content that best fits their needs Using semantics to identify important features (e.g., coga-simplification="simplest") Using aria-invalid and aria-required Back to top Guideline 1.4 – Distinguishable Make it easier for users to see and hear content including separating foreground from background. 1.4.1 Use of Color Level 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. Understanding 1.4.1 Show Hide techniques and failures for 1.4.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.1 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. 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 hover 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 Advisory Techniques for Success Criterion 1.4.1 C15: Using CSS to change the presentation of a user interface component when it receives focus Failures for Success Criterion 1.4.1 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 F73: Failure of Success Criterion 1.4.1 due to creating links that are not visually evident without color vision F81: Failure of Success Criterion 1.4.1 due to identifying required or error fields using color differences only Back to top 1.4.2 Audio Control Level 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. Understanding 1.4.2 Show Hide techniques and failures for 1.4.2 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.2 Note: Other techniques may also be sufficient if they meet the success criterion.
See Understanding Techniques. G60: Playing a sound that turns off automatically within three seconds G170: Providing a control near the beginning of the Web page that turns off sounds that play automatically G171: Playing sounds only on user request Failures for Success Criterion 1.4.2 F23: Failure of 1.4.2 due to playing a sound longer than 3 seconds where there is no mechanism to turn it off F93: Failure of Success Criterion 1.4.2 for absence of a way to pause or stop an HTML5 media element that autoplays Back to top 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: Large 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. Understanding 1.4.3 Show Hide techniques and failures for 1.4.3 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.3 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
Understanding 1.4.5 Show Hide techniques and failures for 1.4.5 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.5 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. C22: Using CSS to control visual presentation of text C30: Using CSS to replace text with images of text and providing user interface controls to switch G140: Separating information and structure from presentation to enable different presentations PDF7: Performing OCR on a scanned PDF document to provide actual text Advisory Techniques for Success Criterion 1.4.5 C12: Using percent for font sizes C13: Using named font sizes C14: Using em units for font sizes C8: Using CSS letter-spacing to control spacing within a word C6: Positioning content based on structural markup Back to top 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: Large 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. Understanding 1.4.6 Show Hide techniques and failures for 1.4.6 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.6 Note: Other techniques may also be sufficient if they meet the success criterion.
See Understanding Techniques. 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 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 Advisory Techniques for Success Criterion 1.4.6 G156: Using a technology that has commonly-available user agents that can change the foreground and background of blocks of text Failures for Success Criterion 1.4.6 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 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) Back to top 1.4.7 Low or No Background Audio Level 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: No 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.
Understanding 1.4.7 Show Hide techniques and failures for 1.4.7 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.7 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G56: Mixing audio files so that non-speech sounds are at least 20 decibels lower than the speech audio content Back to top 1.4.8 Visual Presentation Level AAA For the visual presentation of blocks of text, a mechanism is available to achieve the following: Foreground 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).
Note 1: Logotypes (text that is part of a logo or brand name) are considered essential. Understanding 1.4.9 Show Hide techniques and failures for 1.4.9 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.9 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. C22: Using CSS to control visual presentation of text C30: Using CSS to replace text with images of text and providing user interface controls to switch G140: Separating information and structure from presentation to enable different presentations PDF7: Performing OCR on a scanned PDF document to provide actual text Advisory Techniques for Success Criterion 1.4.9 C12: Using percent for font sizes C13: Using named font sizes C14: Using em units for font sizes C8: Using CSS letter-spacing to control spacing within a word C6: Positioning content based on structural markup Back to top 1.4.10 Reflow Level AA (Added in 2.1) Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: Vertical 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. Understanding 1.4.10 Show Hide techniques and failures for 1.4.10 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.10 Note: Other techniques may also be sufficient if they meet the success criterion.
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. Understanding 1.4.12 Show Hide techniques and failures for 1.4.12 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.12 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. C36: Allowing for text spacing override C35: Allowing for text spacing without wrapping Advisory Techniques for Success Criterion 1.4.12 C8: Using CSS letter-spacing to control spacing within a word C21: Specifying line spacing in CSS C28: Specifying the size of text containers using em units Failures for Success Criterion 1.4.12 F104: Failure of Success Criterion 1.4.12 due to clipped or overlapped content when text spacing is adjusted Back to top 1.4.13 Content on Hover or Focus Level 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: Dismissible: 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.
Understanding 1.4.13 Show Hide techniques and failures for 1.4.13 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 1.4.13 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. SCR39: Making content on focus or hover hoverable, dismissible, and persistent ARIA: Using role="tooltip" (Potential future technique) CSS: Using hover and focus pseudo classes (Potential future technique) Failures for Success Criterion 1.4.13 F95: Failure of Success Criterion 1.4.13 due to content shown on hover not being hoverable Failure to make content dismissable without moving pointer hover or keyboard focus (Potential future technique) Failure to meet by content on hover or focus not remaining visible until dismissed or invalid (Potential future technique) Back to top Principle 2 – Operable User interface components and navigation must be operable. Guideline 2.1 – Keyboard Accessible Make all functionality available from a keyboard. 2.1.1 Keyboard Level 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. Understanding 2.1.1 Show Hide techniques and failures for 2.1.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.1.1 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
G202: Ensuring keyboard control for all functionality Ensuring keyboard control by using one of the following techniques. H91: Using HTML form controls and links PDF3: Ensuring correct tab and reading order in PDF documents PDF11: Providing links and link text using the Link annotation and the /Link structure element in PDF documents PDF23: Providing interactive form controls in PDF documents G90: Providing keyboard-triggered event handlers SCR20: Using both keyboard and other device-specific functions SCR35: Making actions keyboard accessible by using the onclick event of anchors and buttons SCR2: Using redundant keyboard and mouse event handlers Advisory Techniques for Success Criterion 2.1.1 SCR29: Adding keyboard-accessible actions to static HTML elements Failures for Success Criterion 2.1.1 F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function 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 F42: Failure of Success Criteria 1.3.1, 2.1.1, 2.1.3, or 4.1.2 when emulating links Back to top 2.1.2 No Keyboard Trap Level 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. Understanding 2.1.2 Show Hide techniques and failures for 2.1.2 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.1.2 Note: Other techniques may also be sufficient if they meet the success criterion.
See Understanding Techniques. G21: Ensuring that users are not trapped in content Failures for Success Criterion 2.1.2 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 Back to top 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. Understanding 2.1.3 Back to top 2.1.4 Character Key Shortcuts Level 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: Turn 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. Understanding 2.1.4 Show Hide techniques and failures for 2.1.4 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.1.4 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
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.
Understanding 2.2.2 Show Hide techniques and failures for 2.2.2 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.2.2 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G4: Allowing the content to be paused and restarted from where it was paused SCR33: Using script to scroll content, and providing a mechanism to pause it G11: Creating content that blinks for less than 5 seconds G187: Using a technology to include blinking content that can be turned off via the user agent G152: Setting animated gif images to stop blinking after n cycles (within 5 seconds) SCR22: Using scripts to control blinking and stop it in five seconds or less G186: Using a control in the Web page that stops moving, blinking, or auto-updating content G191: Providing a link, button, or other mechanism that reloads the page without any blinking content Failures for Success Criterion 2.2.2 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 F47: Failure of Success Criterion 2.2.2 due to using the blink element 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 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 F7: Failure of Success Criterion 2.2.2 due to an object or applet for more than five seconds Back to top 2.2.3 No Timing Level 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. Understanding 2.2.3 Show Hide techniques and failures for 2.2.3 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.2.3 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
G5: Allowing users to complete an activity without any time limit Back to top 2.2.4 Interruptions Level AAA Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. Understanding 2.2.4 Show Hide techniques and failures for 2.2.4 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.2.4 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G75: Providing a mechanism to postpone any updating of content G76: Providing a mechanism to request an update of the content instead of updating automatically SCR14: Using scripts to make nonessential alerts optional Failures for Success Criterion 2.2.4 F40: Failure due to using meta redirect with a time limit F41: Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh to reload the page Back to top 2.2.5 Re-authenticating Level AAA When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. Understanding 2.2.5 Show Hide techniques and failures for 2.2.5 Sufficient Advisory<
  /span> Failures Sufficient Techniques for Success Criterion 2.2.5 Note: Other techniques may also be sufficient if they meet the success criterion.
See Understanding Techniques. Providing options to continue without loss of data using one of the following techniques: G105: Saving data so that it can be used after a user re-authenticates G181: Encoding user data as hidden or encrypted data in a re-authorization page Failures for Success Criterion 2.2.5 F12: Failure of Success Criterion 2.2.5 due to having a session time limit without a mechanism re-authentication Back to top 2.2.6 Timeouts Level 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. Understanding 2.2.6 Show Hide techniques and failures for 2.2.6 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.2.6 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. Setting a session timeout to occur following at least 20 hours of inactivity.
Store user data for more than 20 hours. Provide a warning of the duration of user inactivity at the start of a process. Back to top Guideline 2.3 – Seizures and Physical Reactions Do not design content in a way that is known to cause seizures or physical reactions. 2.3.1 Three Flashes or Below Threshold Level 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. Understanding 2.3.1 Show Hide techniques and failures for 2.3.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.3.1 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. G19: Ensuring that no component of the content flashes more than three times in any 1-second period G176: Keeping the flashing area small enough G15: Using a tool to ensure that content does not violate the general flash threshold or red flash threshold Back to top 2.3.2 Three Flashes Level AAA Web pages do not contain anything that flashes more than three times in any one second period. Understanding 2.3.2 Show Hide techniques and failures for 2.3.2 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.3.2 Note: Other techniques may also be sufficient if they meet the success criterion.
See Understanding Techniques. G19: Ensuring that no component of the content flashes more than three times in any 1-second period Back to top 2.3.3 Animation from Interactions Level 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. Understanding 2.3.3 Show Hide techniques and failures for 2.3.3 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.3.3 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. C39: Using the CSS reduce-motion query to prevent motion Gx: Allowing users to set a preference that prevents animation.
Back to top Guideline 2.4 – Navigable Provide ways to help users navigate, find content, and determine where they are. 2.4.1 Bypass Blocks Level A A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. Understanding 2.4.1 Show Hide techniques and failures for 2.4.1 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.4.1 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. Creating links to skip blocks of repeated material using one of the following techniques: G1: Adding a link at the top of each page that goes directly to the main content area G123: Adding a link at the beginning of a block of repeated content to go to the end of the b
  
  
  
  
  lock G124: Adding links at the top of the page to each area of the content Grouping blocks of repeated material in a way that can be skipped, using one of the following techniques: ARIA11: Using ARIA landmarks to identify regions of a page H69: Providing heading elements at the beginning of each section of content PDF9: Providing headings by marking content with heading tags in PDF documents H70: Using frame elements to group blocks of repeated material AND H64: Using the title attribute of the frame and iframe elements SCR28: Using an expandable and collapsible menu to bypass block of content Advisory Techniques for Success Criterion 2.4.1 C6: Positioning content based on structural markup H97: Grouping related links using the nav element Back to top 2.4.2 Page Titled Level A Web pages have titles that describe topic or purpose.