angus/WCAG
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit

Browse Source
This commit is contained in:
Angus Kola
2025-12-22 00:21:10 -05:00
commit 2bd947dfe5
91 changed files with 3819 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
3-understandable/3.1.1-language-of-page.md
+34
View File
@@ -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)
3-understandable/3.1.2-language-of-parts.md
+29
View File
@@ -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)
3-understandable/3.1.3-unusual-words.md
+34
View File
@@ -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)
3-understandable/3.1.4-abbreviations.md
+37
View File
@@ -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)
3-understandable/3.1.5-reading-level.md
+32
View File
@@ -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)
3-understandable/3.1.6-pronunciation.md
+32
View File
@@ -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)
3-understandable/3.2.1-on-focus.md
+38
View File
@@ -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)
3-understandable/3.2.2-on-input.md
+43
View File
@@ -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)
3-understandable/3.2.3-consistent-navigation.md
+38
View File
@@ -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)
3-understandable/3.2.4-consistent-identification.md
+34
View File
@@ -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)
3-understandable/3.2.5-change-on-request.md
+49
View File
@@ -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)
3-understandable/3.2.6-consistent-help.md
+46
View File
@@ -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)
3-understandable/3.3.1-error-identification.md
+43
View File
@@ -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)
3-understandable/3.3.2-labels-or-instructions.md
+50
View File
@@ -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)
3-understandable/3.3.3-error-suggestion.md
+39
View File
@@ -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)
3-understandable/3.3.4-error-prevention-legal-financial-data.md
+43
View File
@@ -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)
3-understandable/3.3.5-help.md
+36
View File
@@ -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)
3-understandable/3.3.6-error-prevention-all.md
+34
View File
@@ -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)
3-understandable/3.3.7-redundant-entry.md
+42
View File
@@ -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)
3-understandable/3.3.8-accessible-authentication-minimum.md
+50
View File
@@ -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)
3-understandable/3.3.9-accessible-authentication-enhanced.md
+41
View File
@@ -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)
3-understandable/index.md
+41
View File
@@ -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)