Initial commit

2025-12-22 00:21:10 -05:00
commit 2bd947dfe5
91 changed files with 3819 additions and 0 deletions
@@ -0,0 +1,87 @@
 [Back to 1 Perceivable index](index.md)
 # 1.1.1 Non-text Content
 - Level: A
 - Guideline: 1.1 Text Alternatives
 - Principle: 1 Perceivable
 ## What it is
 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.
 ## How to test
 - Check: 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.)
 - Check: 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.)
 - Check: 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.
 - Check: 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.
 - Check: 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.
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G94: Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content
 - 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
 - H2: Combining adjacent image and text links for the same resource
 - H37: Using alt attributes on img elements
 - H53: Using the body of the object element
 - H86: Providing text alternatives for emojis, emoticons, ASCII art, and leetspeak
 - PDF1: Applying text alternatives to images with the Alt entry in PDF documents
 - G95: Providing short text alternatives that provide a brief description of the non-text content
 - 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
 - G82: Providing a text alternative that identifies the purpose of the non-text content
 - ARIA9: Using aria-labelledby to concatenate a label from several text nodes
 - 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
 - Providing a descriptive label
 - G68: Providing a short text alternative that describes the purpose of live audio-only and live video-only content
 - G100: Providing a short text alternative which is the accepted name or a descriptive name of the non-text content
 - G143: Providing a text alternative that describes the purpose of the CAPTCHA
 - G144: Ensuring that the web page contains another CAPTCHA serving the same purpose using a different modality
 - Implementing or marking the non-text content so that it will be ignored by assistive technology
 - C9: Using CSS to include decorative images
 - H67: Using null alt text and no title attribute on img elements for images that assistive technology should ignore
 - PDF4: Hiding decorative images with the Artifact tag in PDF documents
 ## Advisory techniques (W3C)
 - C18: Using CSS margin and padding rules instead of spacer images for layout design
 ## Common failures (W3C)
 - F3: Failure of Success Criterion 1.1.1 due to using CSS to include images that convey important information
 - 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
 - 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
 - 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)
 - 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
 - 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
 - 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"
 - 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
 - F71: Failure of Success Criterion 1.1.1 due to using text look-alikes to represent text without providing a text alternative
 - F72: Failure of Success Criterion 1.1.1 due to using ASCII art without providing a text alternative
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#non-text-content
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#non-text-content
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,44 @@
 [Back to 1 Perceivable index](index.md)
 # 1.2.1 Audio-only and Video-only (Prerecorded)
 - Level: A
 - Guideline: 1.2 Time-based Media
 - Principle: 1 Perceivable
 ## What it is
 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:
 - **Prerecorded 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.
 ## How to test
 - Check: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.
 - Check: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G158: Providing an alternative for time-based media for audio-only content
 - 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 (W3C)
 - H96: Using the track element to provide audio descriptions
 ## Common failures (W3C)
 - 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
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#audio-only-and-video-only-prerecorded
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/audio-only-and-video-only-prerecorded.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#audio-only-and-video-only-prerecorded
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,40 @@
 [Back to 1 Perceivable index](index.md)
 # 1.2.2 Captions (Prerecorded)
 - Level: A
 - Guideline: 1.2 Time-based Media
 - Principle: 1 Perceivable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G93: Providing open (always visible) captions
 - 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
 - H95: Using the track element to provide captions
 - Using any readily available media format that has a video player that supports closed captioning
 ## Common failures (W3C)
 - 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
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#captions-prerecorded
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/captions-prerecorded.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#captions-prerecorded
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,44 @@
 [Back to 1 Perceivable index](index.md)
 # 1.2.3 Audio Description or Media Alternative (Prerecorded)
 - Level: A
 - Guideline: 1.2 Time-based Media
 - Principle: 1 Perceivable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - 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
 - 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
 - G226: Providing audio descriptions by incorporating narration in the soundtrack
 - 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
 - G203: Using a static text alternative to describe a talking head video
 ## Advisory techniques (W3C)
 - H96: Using the track element to provide audio descriptions
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#audio-description-or-media-alternative-prerecorded
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/audio-description-or-media-alternative-prerecorded.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#audio-description-or-media-alternative-prerecorded
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,33 @@
 [Back to 1 Perceivable index](index.md)
 # 1.2.4 Captions (Live)
 - Level: AA
 - Guideline: 1.2 Time-based Media
 - Principle: 1 Perceivable
 ## What it is
 Captions are provided for all live audio content in synchronized media.
 ## How to test
 - Check: Captions are provided for all live audio content in synchronized media.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - G9: Creating captions for live synchronized media
 - G93: Providing open (always visible) captions
 - 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
 - Using any readily available media format that has a video player that supports closed captioning
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#captions-live
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/captions-live.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#captions-live
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,46 @@
 [Back to 1 Perceivable index](index.md)
 # 1.2.5 Audio Description (Prerecorded)
 - Level: AA
 - Guideline: 1.2 Time-based Media
 - Principle: 1 Perceivable
 ## What it is
 Audio description is provided for all prerecorded video content in synchronized media.
 ## How to test
 - Check: Audio description is provided for all prerecorded video content in synchronized media.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - 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
 - G226: Providing audio descriptions by incorporating narration in the soundtrack
 - 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
 - G203: Using a static text alternative to describe a talking head video
 ## Advisory techniques (W3C)
 - H96: Using the track element to provide audio descriptions
 ## Common failures (W3C)
 - F113: Failure of Success Criterion 1.2.5 due to not using available pauses in dialogue to provide audio descriptions of important visual content
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#audio-description-prerecorded
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/audio-description-prerecorded.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#audio-description-prerecorded
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,31 @@
 [Back to 1 Perceivable index](index.md)
 # 1.2.6 Sign Language (Prerecorded)
 - Level: AAA
 - Guideline: 1.2 Time-based Media
 - Principle: 1 Perceivable
 ## What it is
 Sign language interpretation is provided for all prerecorded audio content in synchronized media.
 ## How to test
 - Check: Sign language interpretation is provided for all prerecorded audio content in synchronized media.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - 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
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#sign-language-prerecorded
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/sign-language-prerecorded.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#sign-language-prerecorded
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,35 @@
 [Back to 1 Perceivable index](index.md)
 # 1.2.7 Extended Audio Description (Prerecorded)
 - Level: AAA
 - Guideline: 1.2 Time-based Media
 - Principle: 1 Perceivable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - 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 (W3C)
 - H96: Using the track element to provide audio descriptions
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#extended-audio-description-prerecorded
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/extended-audio-description-prerecorded.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#extended-audio-description-prerecorded
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,36 @@
 [Back to 1 Perceivable index](index.md)
 # 1.2.8 Media Alternative (Prerecorded)
 - Level: AAA
 - Guideline: 1.2 Time-based Media
 - Principle: 1 Perceivable
 ## What it is
 An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media.
 ## How to test
 - Check: An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - 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
 - H53: Using the body of the object element
 - G159: Providing an alternative for time-based media for video-only content
 ## Common failures (W3C)
 - 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
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#media-alternative-prerecorded
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/media-alternative-prerecorded.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#media-alternative-prerecorded
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,30 @@
 [Back to 1 Perceivable index](index.md)
 # 1.2.9 Audio-only (Live)
 - Level: AAA
 - Guideline: 1.2 Time-based Media
 - Principle: 1 Perceivable
 ## What it is
 An alternative for time-based media that presents equivalent information for live audio-only content is provided.
 ## How to test
 - Check: An alternative for time-based media that presents equivalent information for live audio-only content is provided.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - 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
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#audio-only-live
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/audio-only-live.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#audio-only-live
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,85 @@
 [Back to 1 Perceivable index](index.md)
 # 1.3.1 Info and Relationships
 - Level: A
 - Guideline: 1.3 Adaptable
 - Principle: 1 Perceivable
 ## What it is
 Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
 ## How to test
 - Check: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - ARIA11: Using ARIA landmarks to identify regions of a page
 - H101: Using semantic HTML elements 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
 - 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"
 - 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
 - H63: Using the scope attribute to associate header cells with data cells in data tables
 - H43: Using id and headers attributes to associate data cells with header cells in data tables
 - 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
 - H71: Providing a description for groups of form controls using fieldset and legend elements
 - 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
 - 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
 - T1: Using standard text formatting conventions for paragraphs
 - T2: Using standard text formatting conventions for lists
 - T3: Using standard text formatting conventions for headings
 ## Advisory techniques (W3C)
 - C22: Using CSS to control visual presentation of text
 - G162: Positioning labels to maximize predictability of relationships
 - ARIA1: Using the aria-describedby property to provide a descriptive label for user interface controls
 - ARIA2: Identifying a required field with the aria-required property
 - G141: Organizing a page using headings
 ## Common failures (W3C)
 - 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
 - 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
 - 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
 - F42: Failure of Success Criteria 1.3.1, 2.1.1, 2.1.3, or 4.1.2 when emulating links
 - F43: Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content
 - F46: Failure of Success Criterion 1.3.1 due to using th elements, caption elements, or non-empty summary attributes in layout tables
 - F48: Failure of Success Criterion 1.3.1 due to using the pre element to markup tabular information
 - F90: Failure of Success Criterion 1.3.1 for incorrectly associating table headers and content via the headers and id attributes
 - F91: Failure of Success Criterion 1.3.1 for not correctly marking up table headers
 - F92: Failure of Success Criterion 1.3.1 due to the use of role presentation on content which conveys semantic information
 - F111: Failure of Success Criteria 1.3.1, 2.5.3, and 4.1.2 due to a control with visible label text but no accessible name
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#info-and-relationships
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#info-and-relationships
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,43 @@
 [Back to 1 Perceivable index](index.md)
 # 1.3.2 Meaningful Sequence
 - Level: A
 - Guideline: 1.3 Adaptable
 - Principle: 1 Perceivable
 ## What it is
 When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
 ## How to test
 - Check: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - 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
 ## Common failures (W3C)
 - 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
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#meaningful-sequence
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/meaningful-sequence.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#meaningful-sequence
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,38 @@
 [Back to 1 Perceivable index](index.md)
 # 1.3.3 Sensory Characteristics
 - Level: A
 - Guideline: 1.3 Adaptable
 - Principle: 1 Perceivable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G96: Providing textual identification of items that otherwise rely only on sensory information to be understood
 ## Common failures (W3C)
 - 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
 ## Notes
 - Note: For requirements related to color, refer to Guideline 1.4.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#sensory-characteristics
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/sensory-characteristics.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#sensory-characteristics
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,38 @@
 [Back to 1 Perceivable index](index.md)
 # 1.3.4 Orientation
 - Level: AA
 - Guideline: 1.3 Adaptable
 - Principle: 1 Perceivable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G214: Using a control to allow access to content in different orientations which is otherwise restricted
 ## Common failures (W3C)
 - 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
 ## Notes
 - Note: Examples where a particular display orientation may be essential are a bank check, a piano application, slides for a projector or television, or virtual reality content where content is not necessarily restricted to landscape or portrait display orientation.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#orientation
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/orientation.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#orientation
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,37 @@
 [Back to 1 Perceivable index](index.md)
 # 1.3.5 Identify Input Purpose
 - Level: AA
 - Guideline: 1.3 Adaptable
 - Principle: 1 Perceivable
 ## What it is
 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.
 ## How to test
 - Check: The input field serves a purpose identified in the Input Purposes for user interface components section; and
 - Check: The content is implemented using technologies with support for identifying the expected meaning for form input data.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - H98: Using HTML autocomplete attributes
 ## Common failures (W3C)
 - F107: Failure of Success Criterion 1.3.5 due to incorrect autocomplete attribute values
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#identify-input-purpose
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/identify-input-purpose.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#identify-input-purpose
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,36 @@
 [Back to 1 Perceivable index](index.md)
 # 1.3.6 Identify Purpose
 - Level: AAA
 - Guideline: 1.3 Adaptable
 - Principle: 1 Perceivable
 ## What it is
 In content implemented using markup languages, the purpose of user interface components, icons, and regions can be programmatically determined.
 ## How to test
 - Check: In content implemented using markup languages, the purpose of user interface components, icons, and regions can be programmatically determined.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - 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 (W3C)
 - 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
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#identify-purpose
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/identify-purpose.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#identify-purpose
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,47 @@
 [Back to 1 Perceivable index](index.md)
 # 1.4.1 Use of Color
 - Level: A
 - Guideline: 1.4 Distinguishable
 - Principle: 1 Perceivable
 ## What it is
 Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
 ## How to test
 - Check: Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - 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
 - G111: Using color and pattern
 ## Advisory techniques (W3C)
 - C15: Using CSS to change the presentation of a user interface component when it receives focus
 ## Common failures (W3C)
 - 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
 ## Notes
 - Note: This success criterion addresses color perception specifically. Other forms of perception are covered in Guideline 1.3 including programmatic access to color and other visual presentation coding.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#use-of-color
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/use-of-color.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#use-of-color
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,61 @@
 [Back to 1 Perceivable index](index.md)
 # 1.4.10 Reflow
 - Level: AA
 - Guideline: 1.4 Distinguishable
 - Principle: 1 Perceivable
 ## What it is
 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.
 ## How to test
 - Check: Vertical scrolling content at a width equivalent to 320 CSS pixels;
 - Check: Horizontal scrolling content at a height equivalent to 256 CSS pixels.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - C32: Using media queries and grid CSS to reflow columns
 - C31: Using CSS Flexbox to reflow content
 - C33: Allowing for Reflow with Long URLs and Strings of Text
 - C38: Using CSS width, max-width and flexbox to fit labels and inputs
 - SCR34: Calculating size and position in a way that scales with text size
 - G206: Providing options within the content to switch to a layout that does not require the user to scroll horizontally to read a line of text
 - G224: Accounting for meaningful text indentation and Reflow
 - G225: Section panels that scroll horizontally are designed to fit within a width of 320 CSS pixels on a vertically scrolling page
 - Using PDF/UA when creating PDFs (Potential future technique)
 ## Advisory techniques (W3C)
 - C34: Using media queries to un-fixing sticky headers / footers
 - C37: Using CSS max-width and height to fit images
 - CSS, Reflowing simple data tables (Potential future technique)
 - CSS, Fitting data cells within the width of the viewport (Potential future technique)
 - Mechanism to allow mobile view at any time (Potential future technique)
 - Alternate view supporting Reflow for otherwise excepted content (Potential future technique)
 ## Common failures (W3C)
 - F102: Failure of Success Criterion 1.4.10 due to content disappearing and not being available when content has reflowed
 ## Notes
 - Note 1: 320 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels wide at 400% zoom. For web content which is designed to scroll horizontally (e.g., with vertical text), 256 CSS pixels is equivalent to a starting viewport height of 1024 CSS pixels at 400% zoom.
 - Note 2: Examples of content which requires two-dimensional layout are images required for understanding (such as maps and diagrams), video, games, presentations, data tables (not individual cells), and interfaces where it is necessary to keep toolbars in view while manipulating content. It is acceptable to provide two-dimensional scrolling for such parts of the content.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#reflow
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/reflow.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#reflow
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,40 @@
 [Back to 1 Perceivable index](index.md)
 # 1.4.11 Non-text Contrast
 - Level: AA
 - Guideline: 1.4 Distinguishable
 - Principle: 1 Perceivable
 ## What it is
 The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):
 - **User 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.
 ## How to test
 - Check: 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;
 - Check: Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G195: Using an author-supplied, visible focus indicator
 - G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast
 - G207: Ensuring that a contrast ratio of 3:1 is provided for icons
 - G209: Provide sufficient contrast at the boundaries between adjoining colors
 ## Common failures (W3C)
 - F78: Failure of Success Criterion 1.4.11, 2.4.7 and 2.4.13 due to styling element outlines and borders in a way that removes or renders non-visible the visual focus indicator
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#non-text-contrast
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/non-text-contrast.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#non-text-contrast
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,55 @@
 [Back to 1 Perceivable index](index.md)
 # 1.4.12 Text Spacing
 - Level: AA
 - Guideline: 1.4 Distinguishable
 - Principle: 1 Perceivable
 ## What it is
 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:
 - Line 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.
 ## How to test
 - Check: Line height (line spacing) to at least 1.5 times the font size;
 - Check: Spacing following paragraphs to at least 2 times the font size;
 - Check: Letter spacing (tracking) to at least 0.12 times the font size;
 - Check: Word spacing to at least 0.16 times the font size.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - C36: Allowing for text spacing override
 - C35: Allowing for text spacing without wrapping
 ## Advisory techniques (W3C)
 - 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
 ## Common failures (W3C)
 - F104: Failure of Success Criterion 1.4.12 due to clipped or overlapped content when text spacing is adjusted
 ## Notes
 - Note 1: Content is not required to use these text spacing values. The requirement is to ensure that when a user overrides the authored text spacing, content or functionality is not lost.
 - Note 2: Writing systems for some languages use different text spacing settings, such as paragraph start indent. Authors are encouraged to follow locally available guidance for improving readability and legibility of text in their writing system.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#text-spacing
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/text-spacing.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#text-spacing
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,51 @@
 [Back to 1 Perceivable index](index.md)
 # 1.4.13 Content on Hover or Focus
 - Level: AA
 - Guideline: 1.4 Distinguishable
 - Principle: 1 Perceivable
 ## What it is
 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.
 ## How to test
 - Check: 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;
 - Check: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;
 - Check: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - 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)
 ## Common failures (W3C)
 - F95: Failure of Success Criterion 1.4.13 due to content shown on hover not being hoverable
 - Failure to make content dismissible 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)
 ## Notes
 - Note 1: Examples of additional content controlled by the user agent include browser tooltips created through use of the HTML title attribute [HTML].
 - Note 2: Custom tooltips, sub-menus, and other nonmodal popups that display on hover and focus are examples of additional content covered by this criterion.
 - Note 3: This criterion applies to content that appears in addition to the triggering component itself. Since hidden components that are made visible on keyboard focus (such as links used to skip to another part of a page) do not present additional content they are not covered by this criterion.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#content-on-hover-or-focus
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/content-on-hover-or-focus.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#content-on-hover-or-focus
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,40 @@
 [Back to 1 Perceivable index](index.md)
 # 1.4.2 Audio Control
 - Level: A
 - Guideline: 1.4 Distinguishable
 - Principle: 1 Perceivable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - 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
 ## Common failures (W3C)
 - 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
 ## Notes
 - Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the web page (whether or not it is used to meet other success criteria) must meet this success criterion. See Conformance Requirement 5: Non-Interference.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#audio-control
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/audio-control.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#audio-control
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,47 @@
 [Back to 1 Perceivable index](index.md)
 # 1.4.3 Contrast (Minimum)
 - Level: AA
 - Guideline: 1.4 Distinguishable
 - Principle: 1 Perceivable
 ## What it is
 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.
 ## How to test
 - Check: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1;
 - Check: 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.
 - Check: Text that is part of a logo or brand name has no contrast requirement.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - 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
 - G145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text
 ## Advisory techniques (W3C)
 - G156: Using a technology that has commonly-available user agents that can change the foreground and background of blocks of text
 ## Common failures (W3C)
 - 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)
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#contrast-minimum
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#contrast-minimum
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,51 @@
 [Back to 1 Perceivable index](index.md)
 # 1.4.4 Resize Text
 - Level: AA
 - Guideline: 1.4 Distinguishable
 - Principle: 1 Perceivable
 ## What it is
 Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.
 ## How to test
 - Check: Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G142: Using a technology that has commonly-available user agents that support zoom
 - Ensuring that text containers resize when the text resizes
 - using measurements that are relative to other measurements in the content
 - C28: Specifying the size of text containers using em units
 - C12: Using percent for font sizes
 - C13: Using named font sizes
 - C14: Using em units for font sizes
 - SCR34: Calculating size and position in a way that scales with text size
 - G146: Using liquid layout
 - G178: Providing controls on the web page that allow users to incrementally change the size of all text on the page up to 200 percent
 - G179: Ensuring that there is no loss of content or functionality when the text resizes and text containers do not change their width
 ## Advisory techniques (W3C)
 - C17: Scaling form elements which contain text
 - C20: Using relative measurements to set column widths so that lines can average 80 characters or less when the browser is resized
 - C22: Using CSS to control visual presentation of text
 ## Common failures (W3C)
 - 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
 - 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%
 - F94: Failure of Success Criterion 1.4.4 due to incorrect use of viewport units to resize text
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#resize-text
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/resize-text.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#resize-text
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,47 @@
 [Back to 1 Perceivable index](index.md)
 # 1.4.5 Images of Text
 - Level: AA
 - Guideline: 1.4 Distinguishable
 - Principle: 1 Perceivable
 ## What it is
 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:
 - **Customizable:** 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.
 ## How to test
 - Check: The image of text can be visually customized to the user's requirements;
 - Check: A particular presentation of text is essential to the information being conveyed.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - 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 (W3C)
 - 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
 ## Notes
 - Note: Logotypes (text that is part of a logo or brand name) are considered essential.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#images-of-text
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/images-of-text.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#images-of-text
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,47 @@
 [Back to 1 Perceivable index](index.md)
 # 1.4.6 Contrast (Enhanced)
 - Level: AAA
 - Guideline: 1.4 Distinguishable
 - Principle: 1 Perceivable
 ## What it is
 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.
 ## How to test
 - Check: Large-scale text and images of large-scale text have a contrast ratio of at least 4.5:1;
 - Check: 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.
 - Check: Text that is part of a logo or brand name has no contrast requirement.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - 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
 - G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text
 ## Advisory techniques (W3C)
 - G156: Using a technology that has commonly-available user agents that can change the foreground and background of blocks of text
 ## Common failures (W3C)
 - 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)
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#contrast-enhanced
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/contrast-enhanced.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#contrast-enhanced
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,38 @@
 [Back to 1 Perceivable index](index.md)
 # 1.4.7 Low or No Background Audio
 - Level: AAA
 - Guideline: 1.4 Distinguishable
 - Principle: 1 Perceivable
 ## What it is
 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.
 ## How to test
 - Check: The audio does not contain background sounds.
 - Check: The background sounds can be turned off.
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - G56: Mixing audio files so that non-speech sounds are at least 20 decibels lower than the speech audio content
 ## Notes
 - Note: Per the definition of "decibel," background sound that meets this requirement will be approximately four times quieter than the foreground speech content.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#low-or-no-background-audio
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/low-or-no-background-audio.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#low-or-no-background-audio
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,68 @@
 [Back to 1 Perceivable index](index.md)
 # 1.4.8 Visual Presentation
 - Level: AAA
 - Guideline: 1.4 Distinguishable
 - Principle: 1 Perceivable
 ## What it is
 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).
 - 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.
 ## How to test
 - Check: Foreground and background colors can be selected by the user.
 - Check: Width is no more than 80 characters or glyphs (40 if CJK).
 - Check: Text is not justified (aligned to both the left and the right margins).
 - Check: 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.
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - C23: Specifying text and background colors of secondary content such as banners, features and navigation in CSS while not specifying text and background colors of the main content
 - C25: Specifying borders and layout in CSS to delineate areas of a web page while not specifying text and text-background colors
 - G156: Using a technology that has commonly-available user agents that can change the foreground and background of blocks of text
 - G148: Not specifying background color, not specifying text color, and not using technology features that change those defaults
 - G175: Providing a multi color selection tool on the page for foreground and background colors
 - G204: Not interfering with the user agent's reflow of text as the viewing window is narrowed
 - C20: Using relative measurements to set column widths so that lines can average 80 characters or less when the browser is resized
 - C19: Specifying alignment either to the left or right in CSS
 - G172: Providing a mechanism to remove full justification of text
 - G169: Aligning text on only one side
 - G188: Providing a button on the page to increase line spaces and paragraph spaces
 - C21: Specifying line spacing in CSS
 - G146: Using liquid layout
 - using measurements that are relative to other measurements in the content
 - C12: Using percent for font sizes
 - C13: Using named font sizes
 - C14: Using em units for font sizes
 - C24: Using percentage values in CSS for container sizes
 - SCR34: Calculating size and position in a way that scales with text size
 - G206: Providing options within the content to switch to a layout that does not require the user to scroll horizontally to read a line of text
 ## Common failures (W3C)
 - 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
 - F88: Failure of Success Criterion 1.4.8 due to using text that is justified (aligned to both the left and the right margins)
 ## Notes
 - Note 1: Content is not required to use these values. The requirement is that a mechanism is available for users to change these presentation aspects. The mechanism can be provided by the browser or other user agent. Content is not required to provide the mechanism.
 - Note 2: Writing systems for some languages use different presentation aspects to improve readability and legibility. If a presentation aspect in this success criterion is not used in a writing system, content in that writing system does not need to use that presentation setting and can conform without it. Authors are encouraged to follow guidance for improving readability and legibility of text in their writing system.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#visual-presentation
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/visual-presentation.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#visual-presentation
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,43 @@
 [Back to 1 Perceivable index](index.md)
 # 1.4.9 Images of Text (No Exception)
 - Level: AAA
 - Guideline: 1.4 Distinguishable
 - Principle: 1 Perceivable
 ## What it is
 Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed.
 ## How to test
 - Check: Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - 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 (W3C)
 - 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
 ## Notes
 - Note: Logotypes (text that is part of a logo or brand name) are considered essential.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#images-of-text-no-exception
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/images-of-text-no-exception.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#images-of-text-no-exception
 [Back to 1 Perceivable index](index.md)
@@ -0,0 +1,54 @@
 # 1 Perceivable
 Information and user interface components must be presentable to users in ways they can perceive.
 ## Guidelines
 ### 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](1.1.1-non-text-content.md) — 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. (Level A)
 ### 1.2 Time-based Media
 Provide alternatives for time-based media.
 - [1.2.1 Audio-only and Video-only (Prerecorded)](1.2.1-audio-only-and-video-only-prerecorded.md) — 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: (Level A)
 - [1.2.2 Captions (Prerecorded)](1.2.2-captions-prerecorded.md) — 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. (Level A)
 - [1.2.3 Audio Description or Media Alternative (Prerecorded)](1.2.3-audio-description-or-media-alternative-prerecorded.md) — 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. (Level A)
 - [1.2.4 Captions (Live)](1.2.4-captions-live.md) — Captions are provided for all live audio content in synchronized media. (Level AA)
 - [1.2.5 Audio Description (Prerecorded)](1.2.5-audio-description-prerecorded.md) — Audio description is provided for all prerecorded video content in synchronized media. (Level AA)
 - [1.2.6 Sign Language (Prerecorded)](1.2.6-sign-language-prerecorded.md) — Sign language interpretation is provided for all prerecorded audio content in synchronized media. (Level AAA)
 - [1.2.7 Extended Audio Description (Prerecorded)](1.2.7-extended-audio-description-prerecorded.md) — 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. (Level AAA)
 - [1.2.8 Media Alternative (Prerecorded)](1.2.8-media-alternative-prerecorded.md) — An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media. (Level AAA)
 - [1.2.9 Audio-only (Live)](1.2.9-audio-only-live.md) — An alternative for time-based media that presents equivalent information for live audio-only content is provided. (Level AAA)
 ### 1.3 Adaptable
 Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
 - [1.3.1 Info and Relationships](1.3.1-info-and-relationships.md) — Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
 - [1.3.2 Meaningful Sequence](1.3.2-meaningful-sequence.md) — When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A)
 - [1.3.3 Sensory Characteristics](1.3.3-sensory-characteristics.md) — 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. (Level A)
 - [1.3.4 Orientation](1.3.4-orientation.md) — 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. (Level AA)
 - [1.3.5 Identify Input Purpose](1.3.5-identify-input-purpose.md) — The purpose of each input field collecting information about the user can be programmatically determined when: (Level AA)
 - [1.3.6 Identify Purpose](1.3.6-identify-purpose.md) — In content implemented using markup languages, the purpose of user interface components, icons, and regions can be programmatically determined. (Level AAA)
 ### 1.4 Distinguishable
 Make it easier for users to see and hear content including separating foreground from background.
 - [1.4.1 Use of Color](1.4.1-use-of-color.md) — Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. (Level A)
 - [1.4.2 Audio Control](1.4.2-audio-control.md) — 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. (Level A)
 - [1.4.3 Contrast (Minimum)](1.4.3-contrast-minimum.md) — The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: (Level AA)
 - [1.4.4 Resize Text](1.4.4-resize-text.md) — Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA)
 - [1.4.5 Images of Text](1.4.5-images-of-text.md) — 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: (Level AA)
 - [1.4.6 Contrast (Enhanced)](1.4.6-contrast-enhanced.md) — The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following: (Level AAA)
 - [1.4.7 Low or No Background Audio](1.4.7-low-or-no-background-audio.md) — 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: (Level AAA)
 - [1.4.8 Visual Presentation](1.4.8-visual-presentation.md) — For the visual presentation of blocks of text, a mechanism is available to achieve the following: (Level AAA)
 - [1.4.9 Images of Text (No Exception)](1.4.9-images-of-text-no-exception.md) — Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed. (Level AAA)
 - [1.4.10 Reflow](1.4.10-reflow.md) — Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: (Level AA)
 - [1.4.11 Non-text Contrast](1.4.11-non-text-contrast.md) — The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s): (Level AA)
 - [1.4.12 Text Spacing](1.4.12-text-spacing.md) — 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: (Level AA)
 - [1.4.13 Content on Hover or Focus](1.4.13-content-on-hover-or-focus.md) — Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true: (Level AA)
@@ -0,0 +1,53 @@
 [Back to 2 Operable index](index.md)
 # 2.1.1 Keyboard
 - Level: A
 - Guideline: 2.1 Keyboard Accessible
 - Principle: 2 Operable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G202: Ensuring keyboard control for all functionality
 - 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 (W3C)
 - Using WAI-ARIA role, state, and value attributes if repurposing static elements as interactive user interface components (future link)
 - SCR29: Adding keyboard-accessible actions to static HTML elements
 ## Common failures (W3C)
 - 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, 2.4.13, 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
 ## Notes
 - 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.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#keyboard
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/keyboard.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#keyboard
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,37 @@
 [Back to 2 Operable index](index.md)
 # 2.1.2 No Keyboard Trap
 - Level: A
 - Guideline: 2.1 Keyboard Accessible
 - Principle: 2 Operable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G21: Ensuring that users are not trapped in content
 ## Common failures (W3C)
 - 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
 ## Notes
 - Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#no-keyboard-trap
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/no-keyboard-trap.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#no-keyboard-trap
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,28 @@
 [Back to 2 Operable index](index.md)
 # 2.1.3 Keyboard (No Exception)
 - Level: AAA
 - Guideline: 2.1 Keyboard Accessible
 - Principle: 2 Operable
 ## What it is
 All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
 ## How to test
 - Check: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - No additional techniques exist for this success criterion. Follow techniques for Success Criterion 2.1.1. If that is not possible because there is a requirement for path-dependent input, then it is not possible to meet this Level AAA success criterion.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#keyboard-no-exception
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/keyboard-no-exception.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#keyboard-no-exception
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,39 @@
 [Back to 2 Operable index](index.md)
 # 2.1.4 Character Key Shortcuts
 - Level: A
 - Guideline: 2.1 Keyboard Accessible
 - Principle: 2 Operable
 ## What it is
 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.
 ## How to test
 - Check: A mechanism is available to turn the shortcut off;
 - Check: A mechanism is available to remap the shortcut to include one or more non-printable keyboard keys (e.g., Ctrl, Alt);
 - Check: The keyboard shortcut for a user interface component is only active when that component has focus.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G217: Providing a mechanism to allow users to remap or turn off character key shortcuts
 ## Common failures (W3C)
 - F99: Failure of Success Criterion 2.1.4 due to implementing character key shortcuts that cannot be turned off or remapped
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#character-key-shortcuts
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/character-key-shortcuts.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#character-key-shortcuts
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,58 @@
 [Back to 2 Operable index](index.md)
 # 2.2.1 Timing Adjustable
 - Level: A
 - Guideline: 2.2 Enough Time
 - Principle: 2 Operable
 ## What it is
 For each time limit that is set by the content, at least one of the following is true:
 - **Turn off:** The user is allowed to turn off the time limit before encountering it; or
 - **Adjust:** 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; or
 - **Extend:** 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; or
 - **Real-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; or
 - **Essential Exception:** The time limit is essential and extending it would invalidate the activity; or
 - **20 Hour Exception:** The time limit is longer than 20 hours.
 ## How to test
 - Check: The user is allowed to turn off the time limit before encountering it; or
 - Check: 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; or
 - Check: 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; or
 - Check: 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; or
 - Check: The time limit is essential and extending it would invalidate the activity; or
 - Check: The time limit is longer than 20 hours.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - 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
 - 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
 - SCR1: Allowing the user to extend the default time limit
 - 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
 - SCR36: Providing a mechanism to allow users to display moving, scrolling, or auto-updating text in a static window or area
 ## Common failures (W3C)
 - 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
 - F58: Failure of Success Criterion 2.2.1 due to using server-side techniques to automatically redirect pages after a time-out
 ## Notes
 - Note: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#timing-adjustable
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/timing-adjustable.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#timing-adjustable
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,53 @@
 [Back to 2 Operable index](index.md)
 # 2.2.2 Pause, Stop, Hide
 - Level: A
 - Guideline: 2.2 Enough Time
 - Principle: 2 Operable
 ## What it is
 For moving, blinking, scrolling, or auto-updating information, all of the following are true:
 - **Moving, 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; and
 - **Auto-updating:** For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.
 ## How to test
 - Check: 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; and
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - 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
 - 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
 ## Common failures (W3C)
 - 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
 - F112: Failure of Success Criterion 2.2.2 due to using blinking content that lasts for more than five seconds without a mechanism to stop it
 - 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 that has blinking content without a mechanism to pause the content that blinks for more than five seconds
 ## Notes
 - 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.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#pause-stop-hide
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/pause-stop-hide.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#pause-stop-hide
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,28 @@
 [Back to 2 Operable index](index.md)
 # 2.2.3 No Timing
 - Level: AAA
 - Guideline: 2.2 Enough Time
 - Principle: 2 Operable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - G5: Allowing users to complete an activity without any time limit
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#no-timing
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/no-timing.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#no-timing
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,36 @@
 [Back to 2 Operable index](index.md)
 # 2.2.4 Interruptions
 - Level: AAA
 - Guideline: 2.2 Enough Time
 - Principle: 2 Operable
 ## What it is
 Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.
 ## How to test
 - Check: Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - 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
 ## Common failures (W3C)
 - 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
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#interruptions
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/interruptions.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#interruptions
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,34 @@
 [Back to 2 Operable index](index.md)
 # 2.2.5 Re-authenticating
 - Level: AAA
 - Guideline: 2.2 Enough Time
 - Principle: 2 Operable
 ## What it is
 When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.
 ## How to test
 - Check: When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - 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
 ## Common failures (W3C)
 - F12: Failure of Success Criterion 2.2.5 due to having a session time limit without a mechanism for saving user's input and re-establishing that information upon re-authentication
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#re-authenticating
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/re-authenticating.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#re-authenticating
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,34 @@
 [Back to 2 Operable index](index.md)
 # 2.2.6 Timeouts
 - Level: AAA
 - Guideline: 2.2 Enough Time
 - Principle: 2 Operable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - Setting a session timeout to occur following at least 20 hours of inactivity
 - Storing user data for more than 20 hours
 - Providing a warning of the duration of user inactivity at the start of a process
 ## Notes
 - Note: Privacy regulations may require explicit user consent before user identification has been authenticated and before user data is preserved. In cases where the user is a minor, explicit consent may not be solicited in most jurisdictions, countries or regions. Consultation with privacy professionals and legal counsel is advised when considering data preservation as an approach to satisfy this success criterion.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#timeouts
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/timeouts.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#timeouts
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,34 @@
 [Back to 2 Operable index](index.md)
 # 2.3.1 Three Flashes or Below Threshold
 - Level: A
 - Guideline: 2.3 Seizures and Physical Reactions
 - Principle: 2 Operable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - 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
 ## Notes
 - Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#three-flashes-or-below-threshold
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/three-flashes-or-below-threshold.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#three-flashes-or-below-threshold
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,28 @@
 [Back to 2 Operable index](index.md)
 # 2.3.2 Three Flashes
 - Level: AAA
 - Guideline: 2.3 Seizures and Physical Reactions
 - Principle: 2 Operable
 ## What it is
 Web pages do not contain anything that flashes more than three times in any one second period.
 ## How to test
 - Check: Web pages do not contain anything that flashes more than three times in any one second period.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - G19: Ensuring that no component of the content flashes more than three times in any 1-second period
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#three-flashes
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/three-flashes.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#three-flashes
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,30 @@
 [Back to 2 Operable index](index.md)
 # 2.3.3 Animation from Interactions
 - Level: AAA
 - Guideline: 2.3 Seizures and Physical Reactions
 - Principle: 2 Operable
 ## What it is
 Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed.
 ## How to test
 - Check: Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - C39: Using the CSS prefers-reduced-motion query to prevent motion
 - SCR40: Using the CSS prefers-reduced-motion query in JavaScript to prevent motion
 - Gx: Allowing users to set a preference that prevents animation
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#animation-from-interactions
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/animation-from-interactions.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#animation-from-interactions
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,40 @@
 [Back to 2 Operable index](index.md)
 # 2.4.1 Bypass Blocks
 - Level: A
 - Guideline: 2.4 Navigable
 - Principle: 2 Operable
 ## What it is
 A mechanism is available to bypass blocks of content that are repeated on multiple web pages.
 ## How to test
 - Check: A mechanism is available to bypass blocks of content that are repeated on multiple web pages.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - 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 block
 - G124: Adding links at the top of the page to each area of the content
 - 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
 - H64: Using the title attribute of the iframe element
 - SCR28: Using an expandable and collapsible menu to bypass block of content
 ## Advisory techniques (W3C)
 - C6: Positioning content based on structural markup
 - H97: Grouping related links using the nav element
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#bypass-blocks
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/bypass-blocks.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#bypass-blocks
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,34 @@
 [Back to 2 Operable index](index.md)
 # 2.4.10 Section Headings
 - Level: AAA
 - Guideline: 2.4 Navigable
 - Principle: 2 Operable
 ## What it is
 Section headings are used to organize the content.
 ## How to test
 - Check: Section headings are used to organize the content.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - G141: Organizing a page using headings
 - H69: Providing heading elements at the beginning of each section of content
 ## Notes
 - 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.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#section-headings
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/section-headings.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#section-headings
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,38 @@
 [Back to 2 Operable index](index.md)
 # 2.4.11 Focus Not Obscured (Minimum)
 - Level: AA
 - Guideline: 2.4 Navigable
 - Principle: 2 Operable
 ## What it is
 When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.
 ## How to test
 - Check: When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - C43: Using CSS scroll-padding to un-obscure content
 ## Common failures (W3C)
 - F110: Failure of Success Criterion 2.4.11 Focus Not Obscured (Minimum) due to a sticky footer or header completely hiding focused elements
 ## Notes
 - Note 1: Where content in a configurable interface can be repositioned by the user, then only the initial positions of user-movable content are considered for testing and conformance of this success criterion.
 - Note 2: Content opened by the user may obscure the component receiving focus. If the user can reveal the focused component without advancing the keyboard focus, the component with focus is not considered visually hidden due to author-created content.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#focus-not-obscured-minimum
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/focus-not-obscured-minimum.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#focus-not-obscured-minimum
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,34 @@
 [Back to 2 Operable index](index.md)
 # 2.4.12 Focus Not Obscured (Enhanced)
 - Level: AAA
 - Guideline: 2.4 Navigable
 - Principle: 2 Operable
 ## What it is
 When a user interface component receives keyboard focus, no part of the component is hidden by author-created content.
 ## How to test
 - Check: When a user interface component receives keyboard focus, no part of the component is hidden by author-created content.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - C43: Using CSS scroll-padding to un-obscure content
 ## Common failures (W3C)
 - An interaction that causes content to appear over the component with keyboard focus, visually covering part of the focus indicator. This behavior might be encountered with advertising or promotional material meant to provide more information about a product as the user navigates through a catalogue.
 - A page has a sticky footer (attached to the bottom of the viewport). When tabbing down the page, a focused item is partially obscured by the footer because content in the viewport scrolls without sufficient scroll padding.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#focus-not-obscured-enhanced
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/focus-not-obscured-enhanced.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#focus-not-obscured-enhanced
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,53 @@
 [Back to 2 Operable index](index.md)
 # 2.4.13 Focus Appearance
 - Level: AAA
 - Guideline: 2.4 Navigable
 - Principle: 2 Operable
 ## What it is
 When the keyboard focus indicator is visible, an area of the focus indicator meets all the following:
 - is at least as large as the area of a 2 CSS pixel thick perimeter of the unfocused component or sub-component, and
 - has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states.
 Exceptions:
 - The focus indicator is determined by the user agent and cannot be adjusted by the author, or
 - The focus indicator and the indicator's background color are not modified by the author.
 ## How to test
 - Check: is at least as large as the area of a 2 CSS pixel thick perimeter of the unfocused component or sub-component, and
 - Check: has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states.
 - Check: The focus indicator is determined by the user agent and cannot be adjusted by the author, or
 - Check: The focus indicator and the indicator's background color are not modified by the author.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G195: Using an author-supplied, visible focus indicator
 - C40: Creating a two-color focus indicator to ensure sufficient contrast with all components
 - C41: Creating a strong focus indicator within the component
 ## Common failures (W3C)
 - F55: Failure of Success Criteria 2.1.1, 2.4.7, 2.4.13, and 3.2.1 due to using script to remove focus when focus is received
 - F78: Failure of Success Criterion 1.4.11, 2.4.7 and 2.4.13 due to styling element outlines and borders in a way that removes or renders non-visible the visual focus indicator
 ## Notes
 - Note 1: What is perceived as the user interface component or sub-component (to determine the perimeter) depends on its visual presentation. The visual presentation includes the component's visible content, border, and component-specific background. It does not include shadow and glow effects outside the component's content, background, or border.
 - Note 2: Examples of sub-components that may receive a focus indicator are menu items in an opened drop-down menu, or focusable cells in a grid.
 - Note 3: Contrast calculations can be based on colors defined within the technology (such as HTML, CSS, and SVG). Pixels modified by user agent resolution enhancements and anti-aliasing can be ignored.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#focus-appearance
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/focus-appearance.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#focus-appearance
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,40 @@
 [Back to 2 Operable index](index.md)
 # 2.4.2 Page Titled
 - Level: A
 - Guideline: 2.4 Navigable
 - Principle: 2 Operable
 ## What it is
 Web pages have titles that describe topic or purpose.
 ## How to test
 - Check: Web pages have titles that describe topic or purpose.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G88: Providing descriptive titles for web pages
 - associating a title with a web page
 - H25: Providing a title using the title element
 - PDF18: Specifying the document title using the Title entry in the document information dictionary of a PDF document
 ## Advisory techniques (W3C)
 - G127: Identifying a web page's relationship to a larger collection of web pages
 ## Common failures (W3C)
 - F25: Failure of Success Criterion 2.4.2 due to the title of a web page not identifying the contents
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#page-titled
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/page-titled.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#page-titled
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,39 @@
 [Back to 2 Operable index](index.md)
 # 2.4.3 Focus Order
 - Level: A
 - Guideline: 2.4 Navigable
 - Principle: 2 Operable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G59: Placing the interactive elements in an order that follows sequences and relationships within the content
 - C27: Making the DOM order match the visual order
 - PDF3: Ensuring correct tab and reading order in PDF documents
 - SCR26: Inserting dynamic content into the Document Object Model immediately following its trigger element
 - H102: Creating modal dialogs with the HTML dialog element
 - SCR27: Reordering page sections using the Document Object Model
 ## Common failures (W3C)
 - F44: Failure of Success Criterion 2.4.3 due to using tabindex to create a tab order that does not preserve meaning and operability
 - 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
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#focus-order
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/focus-order.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#focus-order
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,55 @@
 [Back to 2 Operable index](index.md)
 # 2.4.4 Link Purpose (In Context)
 - Level: A
 - Guideline: 2.4 Navigable
 - Principle: 2 Operable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G91: Providing link text that describes the purpose of a link
 - H30: Providing link text that describes the purpose of a link for anchor elements
 - H24: Providing text alternatives for the area elements of image maps
 - G189: Providing a control near the beginning of the web page that changes the link text
 - SCR30: Using scripts to change the link text
 - G53: Identifying the purpose of a link using link text combined with the text of the enclosing sentence
 - H33: Supplementing link text with the title attribute
 - C7: Using CSS to hide a portion of the link text
 - ARIA7: Using aria-labelledby for link purpose
 - ARIA8: Using aria-label for link purpose
 - H77: Identifying the purpose of a link using link text combined with its enclosing list item
 - H78: Identifying the purpose of a link using link text combined with its enclosing paragraph
 - H79: Identifying the purpose of a link in a data table using the link text combined with its enclosing table cell and associated table header cells
 - H81: Identifying the purpose of a link in a nested list using link text combined with the parent list item under which the list is nested
 - semantically indicating links
 - PDF11: Providing links and link text using the Link annotation and the /Link structure element in PDF documents
 - PDF13: Providing replacement text using the /Alt entry for links in PDF documents
 ## Advisory techniques (W3C)
 - H2: Combining adjacent image and text links for the same resource
 - H80: Identifying the purpose of a link using link text combined with the preceding heading element
 ## Common failures (W3C)
 - F63: Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link
 - 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
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#link-purpose-in-context
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-context.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#link-purpose-in-context
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,37 @@
 [Back to 2 Operable index](index.md)
 # 2.4.5 Multiple Ways
 - Level: AA
 - Guideline: 2.4 Navigable
 - Principle: 2 Operable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - G125: Providing links to navigate to related web pages
 - G64: Providing a Table of Contents
 - G63: Providing a site map
 - G161: Providing a search function to help users find content
 - G126: Providing a list of links to all other web pages
 - G185: Linking to all of the pages on the site from the home page
 ## Advisory techniques (W3C)
 - PDF2: Creating bookmarks in PDF documents
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#multiple-ways
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/multiple-ways.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#multiple-ways
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,29 @@
 [Back to 2 Operable index](index.md)
 # 2.4.6 Headings and Labels
 - Level: AA
 - Guideline: 2.4 Navigable
 - Principle: 2 Operable
 ## What it is
 Headings and labels describe topic or purpose.
 ## How to test
 - Check: Headings and labels describe topic or purpose.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - G130: Providing descriptive headings
 - G131: Providing descriptive labels
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#headings-and-labels
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/headings-and-labels.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#headings-and-labels
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,40 @@
 [Back to 2 Operable index](index.md)
 # 2.4.7 Focus Visible
 - Level: AA
 - Guideline: 2.4 Navigable
 - Principle: 2 Operable
 ## What it is
 Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
 ## How to test
 - Check: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G149: Using user interface components that are highlighted by the user agent when they receive focus
 - C15: Using CSS to change the presentation of a user interface component when it receives focus
 - G165: Using the default focus indicator for the platform so that high visibility default focus indicators will carry over
 - G195: Using an author-supplied, visible focus indicator
 - C40: Creating a two-color focus indicator to ensure sufficient contrast with all components
 - C45: Using CSS :focus-visible to provide keyboard focus indication
 - SCR31: Using script to change the background color or border of the element with focus
 ## Common failures (W3C)
 - F55: Failure of Success Criteria 2.1.1, 2.4.7, 2.4.13, and 3.2.1 due to using script to remove focus when focus is received
 - F78: Failure of Success Criterion 1.4.11, 2.4.7 and 2.4.13 due to styling element outlines and borders in a way that removes or renders non-visible the visual focus indicator
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#focus-visible
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/focus-visible.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#focus-visible
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,36 @@
 [Back to 2 Operable index](index.md)
 # 2.4.8 Location
 - Level: AAA
 - Guideline: 2.4 Navigable
 - Principle: 2 Operable
 ## What it is
 Information about the user's location within a set of web pages is available.
 ## How to test
 - Check: Information about the user's location within a set of web pages is available.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - G65: Providing a breadcrumb trail
 - G63: Providing a site map
 - G128: Indicating current location within navigation bars
 - G127: Identifying a web page's relationship to a larger collection of web pages
 ## Advisory techniques (W3C)
 - PDF14: Providing running headers and footers in PDF documents
 - PDF17: Specifying consistent page numbering for PDF documents
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#location
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/location.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#location
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,47 @@
 [Back to 2 Operable index](index.md)
 # 2.4.9 Link Purpose (Link Only)
 - Level: AAA
 - Guideline: 2.4 Navigable
 - Principle: 2 Operable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - ARIA8: Using aria-label for link purpose
 - G91: Providing link text that describes the purpose of a link
 - H30: Providing link text that describes the purpose of a link for anchor elements
 - H24: Providing text alternatives for the area elements of image maps
 - G189: Providing a control near the beginning of the web page that changes the link text
 - SCR30: Using scripts to change the link text
 - C7: Using CSS to hide a portion of the link text
 - PDF11: Providing links and link text using the Link annotation and the /Link structure element in PDF documents
 - PDF13: Providing replacement text using the /Alt entry for links in PDF documents
 ## Advisory techniques (W3C)
 - H2: Combining adjacent image and text links for the same resource
 - H33: Supplementing link text with the title attribute
 ## Common failures (W3C)
 - 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.
 - 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
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#link-purpose-link-only
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-link-only.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#link-purpose-link-only
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,38 @@
 [Back to 2 Operable index](index.md)
 # 2.5.1 Pointer Gestures
 - Level: A
 - Guideline: 2.5 Input Modalities
 - Principle: 2 Operable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G215: Providing controls to achieve the same result as path based or multipoint gestures
 - G216: Providing single point activation for a control slider
 ## Common failures (W3C)
 - F105: Failure of Success Criterion 2.5.1 due to providing functionality via a path-based gesture without simple pointer alternative
 ## Notes
 - Note: This requirement applies to web content that interprets pointer actions (i.e., this does not apply to actions that are required to operate the user agent or assistive technology).
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#pointer-gestures
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/pointer-gestures.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#pointer-gestures
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,48 @@
 [Back to 2 Operable index](index.md)
 # 2.5.2 Pointer Cancellation
 - Level: A
 - Guideline: 2.5 Input Modalities
 - Principle: 2 Operable
 ## What it is
 For functionality that can be operated using a single pointer, at least one of the following is true:
 - **No 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.
 ## How to test
 - Check: The down-event of the pointer is not used to execute any part of the function;
 - Check: 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;
 - Check: The up-event reverses any outcome of the preceding down-event;
 - Check: Completing the function on the down-event is essential.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G210: Ensuring that drag-and-drop actions can be cancelled
 - G212: Using native controls to ensure functionality is triggered on the up-event.
 - Touch events are only triggered when touch is removed from a control (Potential future technique)
 ## Common failures (W3C)
 - F101: Failure of Success Criterion 2.5.2 due to activating a control on the down-event
 ## Notes
 - Note 1: Functions that emulate a keyboard or numeric keypad key press are considered essential.
 - Note 2: This requirement applies to web content that interprets pointer actions (i.e., this does not apply to actions that are required to operate the user agent or assistive technology).
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#pointer-cancellation
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/pointer-cancellation.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#pointer-cancellation
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,46 @@
 [Back to 2 Operable index](index.md)
 # 2.5.3 Label in Name
 - Level: A
 - Guideline: 2.5 Input Modalities
 - Principle: 2 Operable
 ## What it is
 For user interface components with labels that include text or images of text, the name contains the text that is presented visually.
 ## How to test
 - Check: For user interface components with labels that include text or images of text, the name contains the text that is presented visually.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G208: Including the text of the visible label as part of the accessible name
 - G211: Matching the accessible name to the visible label
 ## Advisory techniques (W3C)
 - G162: Positioning labels to maximize predictability of relationships
 - If an icon has no accompanying text, consider using its hover text as its accessible name (Potential future technique)
 ## Common failures (W3C)
 - F96: Failure due to the accessible name not containing the visible label text
 - F111: Failure of Success Criteria 1.3.1, 2.5.3, and 4.1.2 due to a control with visible label text but no accessible name
 - 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 (Potential future technique)
 - Accessible name contains the visible label text, but one or more other words are interspersed in the label (Potential future technique)
 ## Notes
 - Note: A best practice is to have the text of the label at the start of the name.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#label-in-name
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/label-in-name.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#label-in-name
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,39 @@
 [Back to 2 Operable index](index.md)
 # 2.5.4 Motion Actuation
 - Level: A
 - Guideline: 2.5 Input Modalities
 - Principle: 2 Operable
 ## What it is
 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:
 - **Supported 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.
 ## How to test
 - Check: The motion is used to operate functionality through an accessibility supported interface;
 - Check: The motion is essential for the function and doing so would invalidate the activity.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G213: Provide conventional controls and an application setting for motion activated input
 - GXXX: Supporting system level features which allow the user to disable motion actuation
 ## Common failures (W3C)
 - F106: Failure due to inability to deactivate 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
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#motion-actuation
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/motion-actuation.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#motion-actuation
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,45 @@
 [Back to 2 Operable index](index.md)
 # 2.5.5 Target Size (Enhanced)
 - Level: AAA
 - Guideline: 2.5 Input Modalities
 - Principle: 2 Operable
 ## What it is
 The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when:
 - **Equivalent:** 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.
 ## How to test
 - Check: The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels;
 - Check: The target is in a sentence or block of text;
 - Check: The size of the target is determined by the user agent and is not modified by the author;
 - Check: A particular presentation of the target is essential to the information being conveyed.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - Ensuring that targets are at least 44 by 44 CSS pixels
 ## Advisory techniques (W3C)
 - Ensuring inline links provide sufficiently large activation target
 ## Common failures (W3C)
 - Failure of Success Criterion 2.5.5 due to target being less than 44 by 44 CSS pixels
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#target-size-enhanced
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/target-size-enhanced.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#target-size-enhanced
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,34 @@
 [Back to 2 Operable index](index.md)
 # 2.5.6 Concurrent Input Mechanisms
 - Level: AAA
 - Guideline: 2.5 Input Modalities
 - Principle: 2 Operable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - Only using high-level, input-agnostic event handlers, such as focus, blur, click, in Javascript (Potential future technique)
 - Registering event handlers for keyboard/keyboard-like and pointer inputs simultaneously in Javascript; see Example 1 in Pointer Events Level 2 (Potential future technique)
 ## Common failures (W3C)
 - F98: Failure due to interactions being limited to touch-only on touchscreen devices
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#concurrent-input-mechanisms
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/concurrent-input-mechanisms.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#concurrent-input-mechanisms
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,37 @@
 [Back to 2 Operable index](index.md)
 # 2.5.7 Dragging Movements
 - Level: AA
 - Guideline: 2.5 Input Modalities
 - Principle: 2 Operable
 ## What it is
 All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author.
 ## How to test
 - Check: All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G219: Ensuring that an alternative is available for dragging movements that operate on content
 ## Common failures (W3C)
 - F108: Failure of Success Criterion 2.5.7 Dragging Movements due to not providing a single pointer method that does not require a dragging movement
 ## Notes
 - Note: This requirement applies to web content that interprets pointer actions (i.e., this does not apply to actions that are required to operate the user agent or assistive technology).
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#dragging-movements
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/dragging-movements.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#dragging-movements
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,43 @@
 [Back to 2 Operable index](index.md)
 # 2.5.8 Target Size (Minimum)
 - Level: AA
 - Guideline: 2.5 Input Modalities
 - Principle: 2 Operable
 ## What it is
 The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except when:
 - **Spacing:** Undersized targets (those less than 24 by 24 CSS pixels) are positioned so that if a 24 CSS pixel diameter circle is centered on the bounding box of each, the circles do not intersect another target or the circle for another undersized target;
 - **Equivalent:** The function can be achieved through a different control on the same page that meets this criterion;
 - **Inline:** The target is in a sentence or its size is otherwise constrained by the line-height of non-target 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 or is legally required for the information being conveyed.
 ## How to test
 - Check: Undersized targets (those less than 24 by 24 CSS pixels) are positioned so that if a 24 CSS pixel diameter circle is centered on the bounding box of each, the circles do not intersect another target or the circle for another undersized target;
 - Check: The function can be achieved through a different control on the same page that meets this criterion;
 - Check: The target is in a sentence or its size is otherwise constrained by the line-height of non-target text;
 - Check: The size of the target is determined by the user agent and is not modified by the author;
 - Check: A particular presentation of the target is essential or is legally required for the information being conveyed.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - C42: Using min-height and min-width to ensure sufficient target spacing
 ## Notes
 - Note 1: Targets that allow for values to be selected spatially based on position within the target are considered one target for the purpose of the success criterion. Examples include sliders, color pickers displaying a gradient of colors, or editable areas where you position the cursor.
 - Note 2: For inline targets the line-height should be interpreted as perpendicular to the flow of text. For example, in a language displayed vertically, the line-height would be horizontal.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#target-size-minimum
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#target-size-minimum
 [Back to 2 Operable index](index.md)
@@ -0,0 +1,64 @@
 # 2 Operable
 User interface components and navigation must be operable.
 ## Guidelines
 ### 2.1 Keyboard Accessible
 Make all functionality available from a keyboard.
 - [2.1.1 Keyboard](2.1.1-keyboard.md) — 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. (Level A)
 - [2.1.2 No Keyboard Trap](2.1.2-no-keyboard-trap.md) — 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. (Level A)
 - [2.1.3 Keyboard (No Exception)](2.1.3-keyboard-no-exception.md) — All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. (Level AAA)
 - [2.1.4 Character Key Shortcuts](2.1.4-character-key-shortcuts.md) — 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: (Level A)
 ### 2.2 Enough Time
 Provide users enough time to read and use content.
 - [2.2.1 Timing Adjustable](2.2.1-timing-adjustable.md) — For each time limit that is set by the content, at least one of the following is true: (Level A)
 - [2.2.2 Pause, Stop, Hide](2.2.2-pause-stop-hide.md) — For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A)
 - [2.2.3 No Timing](2.2.3-no-timing.md) — 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. (Level AAA)
 - [2.2.4 Interruptions](2.2.4-interruptions.md) — Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. (Level AAA)
 - [2.2.5 Re-authenticating](2.2.5-re-authenticating.md) — When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. (Level AAA)
 - [2.2.6 Timeouts](2.2.6-timeouts.md) — 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. (Level AAA)
 ### 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](2.3.1-three-flashes-or-below-threshold.md) — 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. (Level A)
 - [2.3.2 Three Flashes](2.3.2-three-flashes.md) — Web pages do not contain anything that flashes more than three times in any one second period. (Level AAA)
 - [2.3.3 Animation from Interactions](2.3.3-animation-from-interactions.md) — Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed. (Level AAA)
 ### 2.4 Navigable
 Provide ways to help users navigate, find content, and determine where they are.
 - [2.4.1 Bypass Blocks](2.4.1-bypass-blocks.md) — A mechanism is available to bypass blocks of content that are repeated on multiple web pages. (Level A)
 - [2.4.2 Page Titled](2.4.2-page-titled.md) — Web pages have titles that describe topic or purpose. (Level A)
 - [2.4.3 Focus Order](2.4.3-focus-order.md) — 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. (Level A)
 - [2.4.4 Link Purpose (In Context)](2.4.4-link-purpose-in-context.md) — 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. (Level A)
 - [2.4.5 Multiple Ways](2.4.5-multiple-ways.md) — 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. (Level AA)
 - [2.4.6 Headings and Labels](2.4.6-headings-and-labels.md) — Headings and labels describe topic or purpose. (Level AA)
 - [2.4.7 Focus Visible](2.4.7-focus-visible.md) — Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)
 - [2.4.8 Location](2.4.8-location.md) — Information about the user's location within a set of web pages is available. (Level AAA)
 - [2.4.9 Link Purpose (Link Only)](2.4.9-link-purpose-link-only.md) — 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. (Level AAA)
 - [2.4.10 Section Headings](2.4.10-section-headings.md) — Section headings are used to organize the content. (Level AAA)
 - [2.4.11 Focus Not Obscured (Minimum)](2.4.11-focus-not-obscured-minimum.md) — When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content. (Level AA)
 - [2.4.12 Focus Not Obscured (Enhanced)](2.4.12-focus-not-obscured-enhanced.md) — When a user interface component receives keyboard focus, no part of the component is hidden by author-created content. (Level AAA)
 - [2.4.13 Focus Appearance](2.4.13-focus-appearance.md) — When the keyboard focus indicator is visible, an area of the focus indicator meets all the following: (Level AAA)
 ### 2.5 Input Modalities
 Make it easier for users to operate functionality through various inputs beyond keyboard.
 - [2.5.1 Pointer Gestures](2.5.1-pointer-gestures.md) — 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. (Level A)
 - [2.5.2 Pointer Cancellation](2.5.2-pointer-cancellation.md) — For functionality that can be operated using a single pointer, at least one of the following is true: (Level A)
 - [2.5.3 Label in Name](2.5.3-label-in-name.md) — For user interface components with labels that include text or images of text, the name contains the text that is presented visually. (Level A)
 - [2.5.4 Motion Actuation](2.5.4-motion-actuation.md) — 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: (Level A)
 - [2.5.5 Target Size (Enhanced)](2.5.5-target-size-enhanced.md) — The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when: (Level AAA)
 - [2.5.6 Concurrent Input Mechanisms](2.5.6-concurrent-input-mechanisms.md) — 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. (Level AAA)
 - [2.5.7 Dragging Movements](2.5.7-dragging-movements.md) — All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author. (Level AA)
 - [2.5.8 Target Size (Minimum)](2.5.8-target-size-minimum.md) — The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except when: (Level AA)
@@ -0,0 +1,34 @@
 [Back to 3 Understandable index](index.md)
 # 3.1.1 Language of Page
 - Level: A
 - Guideline: 3.1 Readable
 - Principle: 3 Understandable
 ## What it is
 The default human language of each web page can be programmatically determined.
 ## How to test
 - Check: The default human language of each web page can be programmatically determined.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - H57: Using the language attribute on the HTML element
 - PDF16: Setting the default language using the /Lang entry in the document catalog of a PDF document
 - PDF19: Specifying the language for a passage or phrase with the Lang entry in PDF documents
 ## Advisory techniques (W3C)
 - SVR5: Specifying the default language in the HTTP header
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#language-of-page
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/language-of-page.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#language-of-page
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,29 @@
 [Back to 3 Understandable index](index.md)
 # 3.1.2 Language of Parts
 - Level: AA
 - Guideline: 3.1 Readable
 - Principle: 3 Understandable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - H58: Using language attributes to identify changes in the human language
 - PDF19: Specifying the language for a passage or phrase with the Lang entry in PDF documents
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#language-of-parts
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/language-of-parts.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#language-of-parts
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,34 @@
 [Back to 3 Understandable index](index.md)
 # 3.1.3 Unusual Words
 - Level: AAA
 - Guideline: 3.1 Readable
 - Principle: 3 Understandable
 ## What it is
 A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.
 ## How to test
 - Check: A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - G101: Providing the definition of a word or phrase used in an unusual or restricted way
 - G55: Linking to definitions
 - H40: Using description lists
 - G112: Using inline definitions
 - H54: Using the dfn element to identify the defining instance of a word
 - G62: Providing a glossary
 - G70: Providing a function to search an online dictionary
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#unusual-words
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/unusual-words.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#unusual-words
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,37 @@
 [Back to 3 Understandable index](index.md)
 # 3.1.4 Abbreviations
 - Level: AAA
 - Guideline: 3.1 Readable
 - Principle: 3 Understandable
 ## What it is
 A mechanism for identifying the expanded form or meaning of abbreviations is available.
 ## How to test
 - Check: A mechanism for identifying the expanded form or meaning of abbreviations is available.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - 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
 - PDF8: Providing definitions for abbreviations via an E entry for a structure element
 - G62: Providing a glossary
 - G70: Providing a function to search an online dictionary
 ## Advisory techniques (W3C)
 - H28: Providing definitions for abbreviations by using the abbr element
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#abbreviations
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/abbreviations.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#abbreviations
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,32 @@
 [Back to 3 Understandable index](index.md)
 # 3.1.5 Reading Level
 - Level: AAA
 - Guideline: 3.1 Readable
 - Principle: 3 Understandable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - G86: Providing a text summary that can be understood by people with lower secondary education level reading ability
 - G103: Providing visual illustrations, pictures, and symbols to help explain ideas, events, and processes
 - G79: Providing a spoken version of the text
 - G153: Making the text easier to read
 - G160: Providing sign language versions of information, ideas, and processes that must be understood in order to use the content
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#reading-level
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/reading-level.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#reading-level
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,32 @@
 [Back to 3 Understandable index](index.md)
 # 3.1.6 Pronunciation
 - Level: AAA
 - Guideline: 3.1 Readable
 - Principle: 3 Understandable
 ## What it is
 A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation.
 ## How to test
 - Check: A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - G120: Providing the pronunciation immediately following the word
 - G121: Linking to pronunciations
 - G62: Providing a glossary
 - G163: Using standard diacritical marks that can be turned off
 - H62: Using the ruby element
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#pronunciation
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/pronunciation.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#pronunciation
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,38 @@
 [Back to 3 Understandable index](index.md)
 # 3.2.1 On Focus
 - Level: A
 - Guideline: 3.2 Predictable
 - Principle: 3 Understandable
 ## What it is
 When any user interface component receives focus, it does not initiate a change of context.
 ## How to test
 - Check: When any user interface component receives focus, it does not initiate a change of context.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G107: Using "activate" rather than "focus" as a trigger for changes of context
 ## Advisory techniques (W3C)
 - G200: Opening new windows and tabs from a link only when necessary
 - G201: Giving users advanced warning when opening a new window
 ## Common failures (W3C)
 - F55: Failure of Success Criteria 2.1.1, 2.4.7, 2.4.13, and 3.2.1 due to using script to remove focus when focus is received
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#on-focus
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/on-focus.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#on-focus
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,43 @@
 [Back to 3 Understandable index](index.md)
 # 3.2.2 On Input
 - Level: A
 - Guideline: 3.2 Predictable
 - Principle: 3 Understandable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G80: Providing a submit button to initiate a change of context
 - H32: Providing submit buttons
 - H84: Using a button with a select element to perform an action
 - PDF15: Providing submit buttons with the submit-form action in PDF forms
 - G13: Describing what will happen before a change to a form control that causes a change of context to occur is made
 - SCR19: Using an onchange event on a select element without causing a change of context
 ## Advisory techniques (W3C)
 - G201: Giving users advanced warning when opening a new window
 ## Common failures (W3C)
 - F36: Failure of Success Criterion 3.2.2 due to automatically submitting a form and presenting new content without prior warning when the last field in the form is given a value
 - 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
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#on-input
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/on-input.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#on-input
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,38 @@
 [Back to 3 Understandable index](index.md)
 # 3.2.3 Consistent Navigation
 - Level: AA
 - Guideline: 3.2 Predictable
 - Principle: 3 Understandable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G61: Presenting repeated components in the same relative order each time they appear
 ## Advisory techniques (W3C)
 - PDF14: Providing running headers and footers in PDF documents
 - PDF17: Specifying consistent page numbering for PDF documents
 ## Common failures (W3C)
 - F66: Failure of Success Criterion 3.2.3 due to presenting navigation links in a different relative order on different pages
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#consistent-navigation
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/consistent-navigation.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#consistent-navigation
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,34 @@
 [Back to 3 Understandable index](index.md)
 # 3.2.4 Consistent Identification
 - Level: AA
 - Guideline: 3.2 Predictable
 - Principle: 3 Understandable
 ## What it is
 Components that have the same functionality within a set of web pages are identified consistently.
 ## How to test
 - Check: Components that have the same functionality within a set of web pages are identified consistently.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G197: Using labels, names, and text alternatives consistently for content that has the same functionality
 - following the sufficient techniques for Success Criterion 1.1.1 and sufficient techniques for Success Criterion 4.1.2 for providing labels, names, and text alternatives
 ## Common failures (W3C)
 - 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
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#consistent-identification
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/consistent-identification.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#consistent-identification
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,49 @@
 [Back to 3 Understandable index](index.md)
 # 3.2.5 Change on Request
 - Level: AAA
 - Guideline: 3.2 Predictable
 - Principle: 3 Understandable
 ## What it is
 Changes of context are initiated only by user request or a mechanism is available to turn off such changes.
 ## How to test
 - Check: Changes of context are initiated only by user request or a mechanism is available to turn off such changes.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G76: Providing a mechanism to request an update of the content instead of updating automatically
 - 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
 - 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
 - SCR19: Using an onchange event on a select element without causing a change of context
 ## Advisory techniques (W3C)
 - G200: Opening new windows and tabs from a link only when necessary
 ## Common failures (W3C)
 - F60: Failure of Success Criterion 3.2.5 due to launching a new window when a user enters text into an input field
 - 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
 - F9: Failure of Success Criterion 3.2.5 due to changing the context when the user removes focus from a form element
 - F22: Failure of Success Criterion 3.2.5 due to opening windows that are not requested by the user
 - F52: Failure of Success Criterion 3.2.5 due to opening a new window as soon as a new page is loaded
 - 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
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#change-on-request
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/change-on-request.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#change-on-request
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,46 @@
 [Back to 3 Understandable index](index.md)
 # 3.2.6 Consistent Help
 - Level: A
 - Guideline: 3.2 Predictable
 - Principle: 3 Understandable
 ## What it is
 If a web page contains any of the following help mechanisms, and those mechanisms are repeated on multiple web pages within a set of web pages, they occur in the same order relative to other page content, unless a change is initiated by the user:
 - Human contact details;
 - Human contact mechanism;
 - Self-help option;
 - A fully automated contact mechanism.
 ## How to test
 - Check: Human contact details;
 - Check: Human contact mechanism;
 - Check: Self-help option;
 - Check: A fully automated contact mechanism.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G220: Provide a contact-us link in a consistent location
 ## Common failures (W3C)
 - Inconsistent Help Location
 ## Notes
 - Note 1: Help mechanisms may be provided directly on the page, or may be provided via a direct link to a different page containing the information.
 - Note 2: For this success criterion, "the same order relative to other page content" can be thought of as how the content is ordered when the page is serialized. The visual position of a help mechanism is likely to be consistent across pages for the same page variation (e.g., CSS break-point). The user can initiate a change, such as changing the page's zoom or orientation, which may trigger a different page variation. This criterion is concerned with relative order across pages displayed in the same page variation (e.g., same zoom level and orientation).
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#consistent-help
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/consistent-help.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#consistent-help
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,43 @@
 [Back to 3 Understandable index](index.md)
 # 3.3.1 Error Identification
 - Level: A
 - Guideline: 3.3 Input Assistance
 - Principle: 3 Understandable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - G83: Providing text descriptions to identify required fields that were not completed
 - ARIA2: Identifying a required field with the aria-required property
 - ARIA21: Using aria-invalid to Indicate An Error Field
 - SCR18: Providing client-side validation and alert
 - PDF5: Indicating required form controls in PDF forms
 - ARIA18: Using aria-alertdialog to Identify Errors
 - ARIA19: Using ARIA role=alert or Live Regions to Identify Errors
 - 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
 - SCR32: Providing client-side validation and adding error text via the DOM
 - PDF22: Indicating when user input falls outside the required format or values in PDF forms
 ## Advisory techniques (W3C)
 - G139: Creating a mechanism that allows users to jump to errors
 - G199: Providing success feedback when data is submitted successfully
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#error-identification
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/error-identification.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#error-identification
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,50 @@
 [Back to 3 Understandable index](index.md)
 # 3.3.2 Labels or Instructions
 - Level: A
 - Guideline: 3.3 Input Assistance
 - Principle: 3 Understandable
 ## What it is
 Labels or instructions are provided when content requires user input.
 ## How to test
 - Check: Labels or instructions are provided when content requires user input.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G131: Providing descriptive labels
 - ARIA1: Using the aria-describedby property to provide a descriptive label for user interface controls
 - ARIA9: Using aria-labelledby to concatenate a label from several text nodes
 - ARIA17: Using grouping roles to identify related form controls
 - 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
 - G162: Positioning labels to maximize predictability of relationships
 - G83: Providing text descriptions to identify required fields that were not completed
 - H90: Indicating required form controls using label or legend
 - PDF5: Indicating required form controls in PDF forms
 - H44: Using label elements to associate text labels with form controls
 - PDF10: Providing labels for interactive form controls in PDF documents
 - H71: Providing a description for groups of form controls using fieldset and legend elements
 - G167: Using an adjacent button to label the purpose of a field
 ## Advisory techniques (W3C)
 - G13: Describing what will happen before a change to a form control that causes a change of context to occur is made
 ## Common failures (W3C)
 - F82: Failure of Success Criterion 3.3.2 by visually formatting a set of phone number fields but not including a text label
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#labels-or-instructions
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/labels-or-instructions.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#labels-or-instructions
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,39 @@
 [Back to 3 Understandable index](index.md)
 # 3.3.3 Error Suggestion
 - Level: AA
 - Guideline: 3.3 Input Assistance
 - Principle: 3 Understandable
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - 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
 - PDF22: Indicating when user input falls outside the required format or values in PDF forms
 - G84: Providing a text description when the user provides information that is not in the list of allowed values
 ## Advisory techniques (W3C)
 - G139: Creating a mechanism that allows users to jump to errors
 - G199: Providing success feedback when data is submitted successfully
 - SCR18: Providing client-side validation and alert
 - SCR32: Providing client-side validation and adding error text via the DOM
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#error-suggestion
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/error-suggestion.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#error-suggestion
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,43 @@
 [Back to 3 Understandable index](index.md)
 # 3.3.4 Error Prevention (Legal, Financial, Data)
 - Level: AA
 - Guideline: 3.3 Input Assistance
 - Principle: 3 Understandable
 ## What it is
 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:
 - **Reversible:** 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.
 ## How to test
 - Check: Submissions are reversible.
 - Check: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
 - Check: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - 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
 - G99: Providing the ability to recover deleted information
 - G168: Requesting confirmation to continue with selected action
 ## Advisory techniques (W3C)
 - SCR18: Providing client-side validation and alert
 - G199: Providing success feedback when data is submitted successfully
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#error-prevention-legal-financial-data
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/error-prevention-legal-financial-data.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#error-prevention-legal-financial-data
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,36 @@
 [Back to 3 Understandable index](index.md)
 # 3.3.5 Help
 - Level: AAA
 - Guideline: 3.3 Input Assistance
 - Principle: 3 Understandable
 ## What it is
 Context-sensitive help is available.
 ## How to test
 - Check: Context-sensitive help is available.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - 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
 - G89: Providing expected data format and example
 ## Advisory techniques (W3C)
 - H89: Using the title attribute to provide context-sensitive help
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#help
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/help.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#help
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,34 @@
 [Back to 3 Understandable index](index.md)
 # 3.3.6 Error Prevention (All)
 - Level: AAA
 - Guideline: 3.3 Input Assistance
 - Principle: 3 Understandable
 ## What it is
 For web pages that require the user to submit information, at least one of the following is true:
 - **Reversible:** 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.
 ## How to test
 - Check: Submissions are reversible.
 - Check: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
 - Check: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - Following the sufficient techniques for Success Criterion 3.3.4 for all forms that require the user to submit information
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#error-prevention-all
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/error-prevention-all.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#error-prevention-all
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,42 @@
 [Back to 3 Understandable index](index.md)
 # 3.3.7 Redundant Entry
 - Level: A
 - Guideline: 3.3 Input Assistance
 - Principle: 3 Understandable
 ## What it is
 Information previously entered by or provided to the user that is required to be entered again in the same process is either:
 - auto-populated, or
 - available for the user to select.
 Except when:
 - re-entering the information is essential,
 - the information is required to ensure the security of the content, or
 - previously entered information is no longer valid.
 ## How to test
 - Check: auto-populated, or
 - Check: available for the user to select.
 - Check: re-entering the information is essential,
 - Check: the information is required to ensure the security of the content, or
 - Check: previously entered information is no longer valid.
 - Use the sufficient techniques below as acceptable methods when applicable.
 ## Sufficient techniques (W3C)
 - G221: Provide data from a previous step in a process
 - Not requesting the same information twice (Potential future technique)
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#redundant-entry
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/redundant-entry.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#redundant-entry
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,50 @@
 [Back to 3 Understandable index](index.md)
 # 3.3.8 Accessible Authentication (Minimum)
 - Level: AA
 - Guideline: 3.3 Input Assistance
 - Principle: 3 Understandable
 ## What it is
 A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following:
 - **Alternative:** Another authentication method that does not rely on a cognitive function test.
 - **Mechanism:** A mechanism is available to assist the user in completing the cognitive function test.
 - **Object Recognition:** The cognitive function test is to recognize objects.
 - **Personal Content:** The cognitive function test is to identify non-text content the user provided to the website.
 ## How to test
 - Check: Another authentication method that does not rely on a cognitive function test.
 - Check: A mechanism is available to assist the user in completing the cognitive function test.
 - Check: The cognitive function test is to recognize objects.
 - Check: The cognitive function test is to identify non-text content the user provided to the website.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G218: Email link authentication
 - H100: Providing properly marked up email and password inputs
 - Providing WebAuthn as an alternative to username/password (Potential future technique)
 - Providing a third-party login using OAuth (Potential future technique)
 - Using two techniques to provide two-factor authentication (Potential future technique)
 ## Common failures (W3C)
 - F109: Failure of Success Criterion 3.3.8 and 3.3.9 due to preventing password or code re-entry in the same format
 ## Notes
 - Note 1: "Object recognition" and "Personal content" may be represented by images, video, or audio.
 - Note 2: Examples of mechanisms that satisfy this criterion include: support for password entry by password managers to reduce memory need, and copy and paste to reduce the cognitive burden of re-typing.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#accessible-authentication-minimum
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/accessible-authentication-minimum.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#accessible-authentication-minimum
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,41 @@
 [Back to 3 Understandable index](index.md)
 # 3.3.9 Accessible Authentication (Enhanced)
 - Level: AAA
 - Guideline: 3.3 Input Assistance
 - Principle: 3 Understandable
 ## What it is
 A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following:
 - **Alternative:** Another authentication method that does not rely on a cognitive function test.
 - **Mechanism:** A mechanism is available to assist the user in completing the cognitive function test.
 ## How to test
 - Check: Another authentication method that does not rely on a cognitive function test.
 - Check: A mechanism is available to assist the user in completing the cognitive function test.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - G218: Email link authentication
 - H100: Providing properly marked up email and password inputs
 - Providing WebAuthn as an alternative to username/password (Potential future technique)
 - Providing a third-party login using OAuth (Potential future technique)
 - Using two techniques to provide two-factor authentication (Potential future technique)
 ## Common failures (W3C)
 - F109: Failure of Success Criterion 3.3.8 and 3.3.9 due to preventing password or code re-entry in the same format
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#accessible-authentication-enhanced
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/accessible-authentication-enhanced.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#accessible-authentication-enhanced
 [Back to 3 Understandable index](index.md)
@@ -0,0 +1,41 @@
 # 3 Understandable
 Information and the operation of the user interface must be understandable.
 ## Guidelines
 ### 3.1 Readable
 Make text content readable and understandable.
 - [3.1.1 Language of Page](3.1.1-language-of-page.md) — The default human language of each web page can be programmatically determined. (Level A)
 - [3.1.2 Language of Parts](3.1.2-language-of-parts.md) — 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. (Level AA)
 - [3.1.3 Unusual Words](3.1.3-unusual-words.md) — A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. (Level AAA)
 - [3.1.4 Abbreviations](3.1.4-abbreviations.md) — A mechanism for identifying the expanded form or meaning of abbreviations is available. (Level AAA)
 - [3.1.5 Reading Level](3.1.5-reading-level.md) — 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. (Level AAA)
 - [3.1.6 Pronunciation](3.1.6-pronunciation.md) — A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation. (Level AAA)
 ### 3.2 Predictable
 Make web pages appear and operate in predictable ways.
 - [3.2.1 On Focus](3.2.1-on-focus.md) — When any user interface component receives focus, it does not initiate a change of context. (Level A)
 - [3.2.2 On Input](3.2.2-on-input.md) — 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. (Level A)
 - [3.2.3 Consistent Navigation](3.2.3-consistent-navigation.md) — 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. (Level AA)
 - [3.2.4 Consistent Identification](3.2.4-consistent-identification.md) — Components that have the same functionality within a set of web pages are identified consistently. (Level AA)
 - [3.2.5 Change on Request](3.2.5-change-on-request.md) — Changes of context are initiated only by user request or a mechanism is available to turn off such changes. (Level AAA)
 - [3.2.6 Consistent Help](3.2.6-consistent-help.md) — If a web page contains any of the following help mechanisms, and those mechanisms are repeated on multiple web pages within a set of web pages, they occur in the same order relative to other page content, unless a change is initiated by the user: (Level A)
 ### 3.3 Input Assistance
 Help users avoid and correct mistakes.
 - [3.3.1 Error Identification](3.3.1-error-identification.md) — 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. (Level A)
 - [3.3.2 Labels or Instructions](3.3.2-labels-or-instructions.md) — Labels or instructions are provided when content requires user input. (Level A)
 - [3.3.3 Error Suggestion](3.3.3-error-suggestion.md) — 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. (Level AA)
 - [3.3.4 Error Prevention (Legal, Financial, Data)](3.3.4-error-prevention-legal-financial-data.md) — 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: (Level AA)
 - [3.3.5 Help](3.3.5-help.md) — Context-sensitive help is available. (Level AAA)
 - [3.3.6 Error Prevention (All)](3.3.6-error-prevention-all.md) — For web pages that require the user to submit information, at least one of the following is true: (Level AAA)
 - [3.3.7 Redundant Entry](3.3.7-redundant-entry.md) — Information previously entered by or provided to the user that is required to be entered again in the same process is either: (Level A)
 - [3.3.8 Accessible Authentication (Minimum)](3.3.8-accessible-authentication-minimum.md) — A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following: (Level AA)
 - [3.3.9 Accessible Authentication (Enhanced)](3.3.9-accessible-authentication-enhanced.md) — A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following: (Level AAA)
@@ -0,0 +1,30 @@
 [Back to 4 Robust index](index.md)
 # 4.1.1 Parsing
 - Level: A
 - Guideline: 4.1 Compatible
 - Principle: 4 Robust
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Validate representative pages with the W3C Markup Validation Service: https://validator.w3.org/.
 ## Notes
 - Note 1: This success criterion should be considered as always satisfied for any content using HTML or XML.
 - Note 2: Since this criterion was written, the HTML Living Standard has adopted specific requirements governing how user agents must handle incomplete tags, incorrect element nesting, duplicate attributes, and non-unique IDs. [HTML]  Although the HTML standard treats some of these cases as non-conforming for authors, it is considered to "allow these features" for the purposes of this success criterion because the specification requires that user agents support handling these cases consistently. In practice, this criterion no longer provides any benefit to people with disabilities in itself.  Issues such as missing roles due to inappropriately nested elements or incorrect states or names due to a duplicate ID are covered by different success criteria and should be reported under those criteria rather than as issues with 4.1.1.
 - Deprecated/obsolete in WCAG 2.2; retained for backward compatibility. See Understanding 4.1.1 for details.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#parsing
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/parsing.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#parsing
 [Back to 4 Robust index](index.md)
@@ -0,0 +1,58 @@
 [Back to 4 Robust index](index.md)
 # 4.1.2 Name, Role, Value
 - Level: A
 - Guideline: 4.1 Compatible
 - Principle: 4 Robust
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - 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 iframe element
 - H65: Using the title attribute to identify form controls when the label element cannot be used
 - H88: Using HTML according to spec
 - G135: Using the accessibility API features of a technology to expose names and roles, to allow user-settable properties to be directly set, and to provide notification of changes
 - PDF10: Providing labels for interactive form controls in PDF documents
 - PDF12: Providing name, role, value information for form fields in PDF documents
 - G10: Creating components using a technology that supports the accessibility API features of the platforms on which the user agents will be run to expose the names and roles, allow user-settable properties to be directly set, and provide 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
 ## Common failures (W3C)
 - 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
 - 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
 - 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
 - F42: Failure of Success Criteria 1.3.1, 2.1.1, 2.1.3, or 4.1.2 when emulating links
 - F68: Failure of Success Criterion 4.1.2 due to a user interface control not having a programmatically determined name
 - 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
 - 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
 - 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
 - F111: Failure of Success Criteria 1.3.1, 2.5.3, and 4.1.2 due to a control with visible label text but no accessible name
 ## Notes
 - Note: This success criterion is primarily for web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification.
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#name-role-value
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#name-role-value
 [Back to 4 Robust index](index.md)
@@ -0,0 +1,53 @@
 [Back to 4 Robust index](index.md)
 # 4.1.3 Status Messages
 - Level: AA
 - Guideline: 4.1 Compatible
 - Principle: 4 Robust
 ## What it is
 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.
 ## How to test
 - Check: 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.
 - Use the sufficient techniques below as acceptable methods when applicable.
 - Confirm none of the common failures apply.
 ## Sufficient techniques (W3C)
 - ARIA22: Using role=status to present status messages
 - G199: Providing success feedback when data is submitted successfully
 - 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
 - ARIA23: Using role=log to identify sequential information updates
 - Using role="progressbar" (future link)
 - G193: Providing help by an assistant in the web page
 ## Advisory techniques (W3C)
 - Using aria-live regions with chat clients (future link)
 - Using aria-live regions to support 1.4.13 Content on Hover or Focus (future link)
 - Using role="marquee" (future link)
 - Using role="timer" (future link)
 - ARIA18: Using aria-alertdialog to Identify Errors
 - SCR14: Using scripts to make nonessential alerts optional
 ## Common failures (W3C)
 - F103: Failure of Success Criterion 4.1.3 due to providing status messages that cannot be programmatically determined through role or properties
 - Using role="alert" or aria-live="assertive" on content which is not important and time-sensitive (future link)
 ## Resources
 - WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#status-messages
 - Understanding: https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html
 - Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#status-messages
 [Back to 4 Robust index](index.md)
@@ -0,0 +1,13 @@
 # 4 Robust
 Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.
 ## Guidelines
 ### 4.1 Compatible
 Maximize compatibility with current and future user agents, including assistive technologies.
 - [4.1.1 Parsing](4.1.1-parsing.md) — 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. (Level A)
 - [4.1.2 Name, Role, Value](4.1.2-name-role-value.md) — 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. (Level A)
 - [4.1.3 Status Messages](4.1.3-status-messages.md) — 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. (Level AA)