WCAG 2.0 Principle 3 Understandable Rules
From MemberWiki
Rules Home | Principle 1 Pervceivable | Principle 2 Operable | Principle 3 Understandable | Principle 4 Robust
Contents |
Page is Deprecated
WCAG Guideline 3.1 Readable: Make text content readable and understandable.
Requirement 3.1.1 Language of Page
The default human language of each Web page can be programmatically determined. (Level A)
ID | Implemented | Priority | ARIA Transitional Ruleset | ARIA Strict Ruleset | IITAA 2.0 Ruleset | Rule Description |
---|---|---|---|---|---|---|
LANGUAGE_1 | No | P1 | Violation | Violation | Violation | LANGUAGE 1: Each page must have a lang attribute on its html element.
WCAG Sufficient Techniques: |
LANGUAGE_2 | No | P1 | Violation | Violation | Violation | LANGUAGE 2: lang attribute on html element must have a valid two-character language code.
WCAG Sufficient Techniques: |
Requirement 3.1.2 Language of Parts
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)
ID | Implemented | Priority | ARIA Transitional Ruleset | ARIA Strict Ruleset | IITAA 2.0 Ruleset | Rule Description |
---|---|---|---|---|---|---|
none | no rule | Rules under development |
Requirement 3.1.3 Unusual Words
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)
ID | Implemented | Priority | ARIA Transitional Ruleset | ARIA Strict Ruleset | IITAA 2.0 Ruleset | Rule Description |
---|---|---|---|---|---|---|
none | no rule | Rules under development |
Requirement 3.1.4 Abbreviations
A mechanism for identifying the expanded form or meaning of abbreviations is available. (Level AAA)
ID | Implemented | Priority | ARIA Transitional Ruleset | ARIA Strict Ruleset | IITAA 2.0 Ruleset | Rule Description |
---|---|---|---|---|---|---|
none | no rule | Rules under development |
Requirement 3.1.5 Reading Level
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)
ID | Implemented | Priority | ARIA Transitional Ruleset | ARIA Strict Ruleset | IITAA 2.0 Ruleset | Rule Description |
---|---|---|---|---|---|---|
none | no rule | Rules under development |
Requirement 3.1.6 Pronunciation
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)
ID | Implemented | Priority | ARIA Transitional Ruleset | ARIA Strict Ruleset | IITAA 2.0 Ruleset | Rule Description |
---|---|---|---|---|---|---|
none | no rule | Rules under development |
WCAG Guideline 3.2 Predictable: Make Web pages appear and operate in predictable ways.
Requirement 3.2.1 On Focus
When any component receives focus, it does not initiate a change of context. (Level A)
ID | Implemented | Priority | ARIA Transitional Ruleset | ARIA Strict Ruleset | IITAA 2.0 Ruleset | Rule Description |
---|---|---|---|---|---|---|
none | no rule | Rules under development |
Requirement 3.2.2 On Input
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)
ID | Implemented | Priority | ARIA Transitional Ruleset | ARIA Strict Ruleset | IITAA 2.0 Ruleset | Rule Description |
---|---|---|---|---|---|---|
none | no rule | Rules under development |
Requirement 3.2.3 Consistent Navigation
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)
ID | Implemented | Priority | ARIA Transitional Ruleset | ARIA Strict Ruleset | IITAA 2.0 Ruleset | Rule Description |
---|---|---|---|---|---|---|
none | no rule | Rules under development |
Requirement 3.2.4 Consistent Identification
Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)
ID | Implemented | Priority | ARIA Transitional Ruleset | ARIA Strict Ruleset | IITAA 2.0 Ruleset | Rule Description |
---|---|---|---|---|---|---|
LANDMARK 8 | No | P1 | Manual Check | Manual Check | Manual Check | LANDMARK 8: Landmarks and their labels should be used consistently between pages
WCAG Sufficient and Failure Techniques: |
Requirement 3.2.5 Change on Request
Changes of context are initiated only by user request or a mechanism is available to turn off such changes. (Level AAA)
ID | Implemented | Priority | ARIA Transitional Ruleset | ARIA Strict Ruleset | IITAA 2.0 Ruleset | Rule Description |
---|---|---|---|---|---|---|
none | no rule | Rules under development |
WCAG Guideline 3.3 Input Assistance: Help users avoid and correct mistakes.
Requirement 3.3.1 Error Identification
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)
ID | Implemented | Priority | ARIA Transitional Ruleset | ARIA Strict Ruleset | IITAA 2.0 Ruleset | Rule Description |
---|---|---|---|---|---|---|
none | no rule | Rules under development |
Requirement 3.3.2 Labels or Instructions
Labels or instructions are provided when content requires user input. (Level A)
ID | Implemented | Priority | ARIA Transitional Ruleset | ARIA Strict Ruleset | IITAA 2.0 Ruleset | Rule Description |
---|---|---|---|---|---|---|
CONTROL_1 | Yes | P1 | Violation | Violation | Violation | CONTROL 1: Each textarea element; select element and input element of type text, password, checkbox, radio or file must have an associated text label
PURPOSE: Form controls with labels enable people using screen readers to identify the purpose of each form control Techniques rule supports for identifying a text label for a form control:
WCAG Sufficient Techniques: |
CONTROL_2 | Yes | P1 | Violation | Violation | Violation | CONTROL 2: Every input type image must have an alt attribute with content
PURPOSE: Without alt text description people using speech will not be to identify the purpose of the button WCAG Sufficient Techniques: |
CONTROL_3 | Yes | P1 | Violation | Violation | Violation | CONTROL 3: Groups of radio buttons should be labeled with a grouping label like fieldset/legend or aria labeling technique
PURPOSE: Without legend or other type of grouping label people using speech may not be to identify the purpose of the radio button button group NOTE:
WCAG Sufficient Techniques: Examples: Rule Implementation Notes:
|
CONTROL_3A | Yes | P1 | Violation | Violation | Violation | CONTROL 3A: If checkboxes share the same name value or there is a sequence of more than 2 checkboxes the checkboxes, must be labeled with a grouping label like fieldset/legend or aria labeling technique
PURPOSE: Without legend or other type of grouping label people using speech may not be to identify the purpose of the checkboxes controls NOTES:
WCAG Sufficient Techniques: |
CONTROL_3B | Yes | P1 | Violation | Violation | Violation | CONTROL 3B: If two or more form controls of the same type and have the same label value, but differ in the value of the name attribute, they must be labeled with a grouping label like fieldset/legend or aria labeling technique
PURPOSE: Without legend or other type of grouping label people using speech may not be to identify the purpose of the checkboxes controls NOTES:
WCAG Sufficient Techniques: |
CONTROL_4 | Yes | P2 | Violation | Violation | Violation | CONTROL 4: Button elements must have text content and input type button must have a value attribute with content
PURPOSE: Form controls without text labels are confusing all users, but especially to people with disabilities WCAG Sufficient Techniques: |
CONTROL_5 | Yes | P1 | Violation | Violation | Violation | CONTROL 5: Textarea, select, input and button elements with id attributes, must have unique id values on the page
PURPOSE: WCAG Sufficient Techniques: |
CONTROL_6 | Yes | P1 | Violation | Violation | Violation | CONTROL 6: Label with a for attribute reference does not reference a form control
WCAG Sufficient Techniques:
|
CONTROL_7 | Yes | P1 | Violation | Violation | Violation | CONTROL 7: Label or legend element should contain content
WCAG Sufficient Techniques:
|
CONTROL_8 | Yes | P1 | Violation | Violation | Violation | CONTROL 8: Fieldset should contain exactly one legend element
WCAG Sufficient Techniques:
|
CONTROL_9 | Yes | P1 | Recommendation | Recommendation | Violation | CONTROL 9: Avoid using the title attribute as label, use a LABEL element or ARIA technique
WCAG Sufficient Techniques:
|
Requirement 3.3.3 Error Suggestion
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)
ID | Implemented | Priority | ARIA Transitional Ruleset | ARIA Strict Ruleset | IITAA 2.0 Ruleset | Rule Description |
---|---|---|---|---|---|---|
none | no rule | Rules under development |
Requirement 3.3.4 Error Prevention (Legal, Financial, Data)
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)
- 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.
ID | Implemented | Priority | ARIA Transitional Ruleset | ARIA Strict Ruleset | IITAA 2.0 Ruleset | Rule Description |
---|---|---|---|---|---|---|
none | no rule | Rules under development |
Requirement 3.3.5 Help
Context-sensitive help is available. (Level AAA)
ID | Implemented | Priority | ARIA Transitional Ruleset | ARIA Strict Ruleset | IITAA 2.0 Ruleset | Rule Description |
---|---|---|---|---|---|---|
none | no rule | Rules under development |
Requirement 3.3.6 Error Prevention (All)
For Web pages that require the user to submit information, at least one of the following is true: (Level AAA)
- 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.
ID | Implemented | Priority | ARIA Transitional Ruleset | ARIA Strict Ruleset | IITAA 2.0 Ruleset | Rule Description |
---|---|---|---|---|---|---|
none | no rule | Rules under development |