From MemberWiki
OAA Rules Home |
WCAG 2.0 Summary of Rules |
Rule Category Summary of Rules |
Abbreviation Rules |
Audio Rules |
Color Rules |
Embedded Application Rules |
Form Control Rules |
Heading Rules |
Image Rules |
Landmark Rules |
Language Rules |
Layout Rules |
List Rules |
Link Rules |
Page Navigation Rules |
Scripting Rules |
Table Rules |
Timing Rules |
Title Rules |
Video Rules |
Widget Rules
Heading Rule Details
Heading Rule 1: Page must/should have h1 element
| Property
| Value(s)
| Up To Date
|
| Definition
| Each page must/should contain at least one H1 element and each H1 element must have content
| yes
|
| Summary
| Page must/should have H1 element
| yes
|
| Purpose
|
- Headings provide a navigation point for users of asssitive technologies to the main content and help users understand the main content of the page
| yes
|
| Rule ID
| HEADING_1
| yes
|
| NLS Rule ID
| Heading Rule 1
| yes
|
| Techniques
|
- Include an H1 element at the begining of the main content
- The text content of the H1 element should describe the main content of the page
- The H1 element should be visible graphically and to assistive technologies, do not hide using CSS techniques
| yes
|
| Manual Checks
| none
| yes
|
| Scope
| Page
| yes
|
| WCAG 2.0 Primary
| 2.4.1
| yes
|
| WCAG 2.0 Related
|
| yes
|
| Language Dependency
| empty string
| yes
|
| Rule Category
| Heading
| yes
|
| Target Resources
|
| yes
|
| Target Resources Description
| H1 and BODY elements
| yes
|
| Resource Properties
|
- tag_name
- name
- name_length
| yes
|
Heading Rule 1: Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| Page contains a least one H1 element
| yes
|
| All Pass: Plural
| empty string
| yes
|
| Manual Check: Singular
| empty string
| yes
|
| Manual Check: Plural
| empty string
| yes
|
| Some Fail
| empty string
| yes
|
| All Fail: Singular
| Page does not contain an H1 element
| yes
|
| All Fail: Plural
| empty string
| yes
|
| Corrective Action: Singular
| Add a H1 element at the begining of the main content of the page
| yes
|
| Corrective Action: Plural
| empty string
| yes
|
| Not Applicable
| empty string
| yes
|
Heading Rule 1: Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| Page has H1 element
| yes
|
| Pass 2
| empty string
| yes
|
| Pass 3
| empty string
| yes
|
| Manual Check 1
| empty string
| yes
|
| Manual Check 2
| empty string
| yes
|
| Manual Check 3
| empty string
| yes
|
| Corrective Action 1
| Add a H1 element at the begining of the main content of the page
| yes
|
| Corrective Action 2
| Add content to the H1 element, the content should describe the content or the purpose of the page or main section
| yes
|
| Corrective Action 3
| empty string
| yes
|
| Hidden (i.e. thru css)
| H1 element is not available to assistive technologies.
| yes
|
| Presentation (i.e. role=presentation)
| empty string
| yes
|
| Other
| empty string
| yes
|
Heading Rule 2: h1 must/should be in main landmark
| Property
| Value(s)
| Up To Date
|
| Definition
| If the page contains both a MAIN landmark and an H1 element, the H1 element must/should be a child of the main landmark.
| yes
|
| Summary
| H1 must/should be in MAIN landmark
| yes
|
| Purpose
|
- Headings provide a navigation point for users of assistive technologies to the primary content and help users understand understand that content
- Including both MAIN landmarks and H1 elements provides a redundent way for users of assistive technology to find the main topics of a web page
| yes
|
| Rule ID
| HEADING_2
| yes
|
| NLS Rule ID
| Heading Rule 2
| yes
|
| Techniques
|
- Include an H1 element at the beginning of each MAIN landmark
- If there is more than one MAIN landmark, use ARIA-LABELLEDBY on the MAIN landmark to reference the H1 element as a name for MAIN landmark
| yes
|
| Manual Checks
| none
| yes
|
| Scope
| Element
| yes
|
| WCAG 2.0 Primary
| 2.4.6
| yes
|
| WCAG 2.0 Related
|
| yes
|
| Language Dependency
| empty string
| yes
|
| Rule Category
| Heading
| yes
|
| Target Resources
|
| yes
|
| Target Resources Description
| H1 elements and elements with ARIA attribute ROLE="MAIN"
| yes
|
| Resource Properties
|
- tag_name
- id
- name
- main_landmark
| yes
|
Heading Rule 2: Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| H1 element is a child of a MAIN landmark
| yes
|
| All Pass: Plural
| %N_P H1 elements ara a child of a MAIN landmark
| yes
|
| Manual Check: Singular
| empty string
| yes
|
| Manual Check: Plural
| empty string
| yes
|
| Some Fail
| %N_F of %N_T %ELEM_T are NOT child of a MAIN landmark
| yes
|
| All Fail: Singular
| H1 element is NOT a child of a MAIN landmark
| yes
|
| All Fail: Plural
| All %N_F H1 elements are NOT a child of a MAIN landmark
| yes
|
| Corrective Action: Singular
| either move the H1 element to the begining of a MAIN landmark or change the H1 element to another heading level
| yes
|
| Corrective Action: Plural
| either move the %N_F H1 elements to the begining of a MAIN landmark or change the H1 element to another heading level
| yes
|
| Not Applicable
| No MAIN landmark and/or H1 elements in this page
| yes
|
Heading Rule 2: Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| H1 is a child element of a MAIN landmark
| yes
|
| Pass 2
| empty string
| yes
|
| Pass 3
| empty string
| yes
|
| Manual Check 1
| empty string
| yes
|
| Manual Check 2
| empty string
| yes
|
| Manual Check 3
| empty string
| yes
|
| Corrective Action 1
| Position the H1 element as one of the first descendant elements of a MAIN landmark
| yes
|
| Corrective Action 2
| empty string
| yes
|
| Corrective Action 3
| empty string
| yes
|
| Hidden (i.e. thru css)
| H1 element is hidden from asssistive technologies.
| yes
|
| Presentation (i.e. role=presentation)
| empty string
| yes
|
| Other
| empty string
| yes
|
Heading Rule 3: Sibling headings must/should be unique
| Property
| Value(s)
| Up To Date
|
| Definition
| Sibling heading elements must/should should be unique
| yes
|
| Summary
| Sibling headings must/should be unique
| yes
|
| Purpose
|
- If section headings that share the same parent heading are NOT unique users of assistive technology will not be able to descern the differences between sibling secitons of the web resource
| yes
|
| Rule ID
| HEADING_3
| yes
|
| NLS Rule ID
| Heading Rule 3
| yes
|
| Techniques
|
- Make sure the content of sibling headings that share the same parent heading help users understand the unique content of each section they describe
| yes
|
| Manual Checks
| none
| yes
|
| Scope
| Element
| yes
|
| WCAG 2.0 Primary
| 2.4.6
| yes
|
| WCAG 2.0 Related
|
| yes
|
| Language Dependency
| empty string
| yes
|
| Rule Category
| Heading
| yes
|
| Target Resources
|
| yes
|
| Target Resources Description
| Heading elements
| yes
|
| Resource Properties
|
| yes
|
Heading Rule 3: Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| empty string
| yes
|
| All Pass: Plural
| All %N_P sibling headings elements of the same level have unique text content
| yes
|
| Manual Check: Singular
| empty string
| yes
|
| Manual Check: Plural
| empty string
| yes
|
| Some Fail
| %N_F of %N_T sibling heading elements of the same level do NOT have unique text content
| yes
|
| All Fail: Singular
| empty string
| yes
|
| All Fail: Plural
| All %N_F sibling heading elements do NOT have unique text content
| yes
|
| Corrective Action: Singular
| empty string
| yes
|
| Corrective Action: Plural
| update the text content of the %N_F sibling heading elements of the same level to be unique
| yes
|
| Not Applicable
| No sibling heading elements of the same level in this page
| yes
|
Heading Rule 3: Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| %1 heading content is unique among sibling headings
| yes
|
| Pass 2
| empty string
| yes
|
| Pass 3
| empty string
| yes
|
| Manual Check 1
| empty string
| yes
|
| Manual Check 2
| empty string
| yes
|
| Manual Check 3
| empty string
| yes
|
| Corrective Action 1
| Change %1 heading content to describe the differences sibling sections
| yes
|
| Corrective Action 2
| empty string
| yes
|
| Corrective Action 3
| empty string
| yes
|
| Hidden (i.e. thru css)
| %1 element is hidden from asssistive technologies.
| yes
|
| Presentation (i.e. role=presentation)
| empty string
| yes
|
| Other
| empty string
| yes
|
Heading Rule 4: Headings must/should be descriptive
| Property
| Value(s)
| Up To Date
|
| Definition
| Heading elements must/should describe the sections they label
| yes
|
| Summary
| Headings must/should be descriptive
| yes
|
| Purpose
|
- If headings are NOT descriptive or unique they will confuse users of assistive technology
| yes
|
| Rule ID
| HEADING_4
| yes
|
| NLS Rule ID
| Heading Rule 4
| yes
|
| Techniques
|
- Include headings elements at the proper level for each section of a web page
- Use headings as labels for ARIA landmarks to provide redundent page navigation capabilities for users of assistive technologies
- Check headings against other headings in the document to make sure the headings uniquely describe content of each section of the web page
- If headings are too similar to each other users of assistive technology will not be able to use them to understand the differences between different sections of the web page
| yes
|
| Manual Checks
| none
| yes
|
| Scope
| Element
| yes
|
| WCAG 2.0 Primary
| 2.4.6
| yes
|
| WCAG 2.0 Related
|
| yes
|
| Language Dependency
| empty string
| yes
|
| Rule Category
| Heading
| yes
|
| Target Resources
|
| yes
|
| Target Resources Description
| Heading elements
| yes
|
| Resource Properties
|
| yes
|
Heading Rule 4: Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| empty string
| yes
|
| All Pass: Plural
| empty string
| yes
|
| Manual Check: Singular
| Verify the heading element describes the content following the heading element
| yes
|
| Manual Check: Plural
| Verify the %N_MC heading elements describes the content following each heading element
| yes
|
| Some Fail
| empty string
| yes
|
| All Fail: Singular
| Add text content to heading
| yes
|
| All Fail: Plural
| Add text content to %N_F heading elements with no text content
| yes
|
| Corrective Action: Singular
| empty string
| yes
|
| Corrective Action: Plural
| empty string
| yes
|
| Not Applicable
| No heading elements on this page
| yes
|
Heading Rule 4: Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| empty string
| yes
|
| Pass 2
| empty string
| yes
|
| Pass 3
| empty string
| yes
|
| Manual Check 1
| Check %1 element to make sure it describes the section it labels
| yes
|
| Manual Check 2
| empty string
| yes
|
| Manual Check 3
| empty string
| yes
|
| Corrective Action 1
| Add text content to %1 element that describes the section it labels or remove it from the page if it is not needed
| yes
|
| Corrective Action 2
| empty string
| yes
|
| Corrective Action 3
| empty string
| yes
|
| Hidden (i.e. thru css)
| %1 element is hidden from asssistive technologies.
| yes
|
| Presentation (i.e. role=presentation)
| empty string
| yes
|
| Other
| empty string
| yes
|
Heading Rule 5: Headings must/should be properly nested
| Property
| Value(s)
| Up To Date
|
| Definition
| Heading elements must/should be properly nested
| yes
|
| Summary
| Headings must/should be properly nested
| yes
|
| Purpose
|
- Head elements that are properly nested help users of assistive technology understand the structure of the information on the web page
| yes
|
| Rule ID
| HEADING_5
| yes
|
| NLS Rule ID
| Heading Rule 5
| yes
|
| Techniques
|
- Include headings elements at the proper level for each section of a web page
- Use headings as labels for ARIA landmarks to provide redundent page navigation capabilities for users of assistive technologies
- Check headings against other headings in the document to make sure the headings uniquely describe content of each section of the web page
- If headings are too similar to each other users of assistive technology will not be able to use them to understand the differences between different sections of the web page
| yes
|
| Manual Checks
| none
| yes
|
| Scope
| Page
| yes
|
| WCAG 2.0 Primary
| 2.4.6
| yes
|
| WCAG 2.0 Related
|
| yes
|
| Language Dependency
| empty string
| yes
|
| Rule Category
| Heading
| yes
|
| Target Resources
|
| yes
|
| Target Resources Description
| Heading elements
| yes
|
| Resource Properties
|
| yes
|
Heading Rule 5: Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| empty string
| yes
|
| All Pass: Plural
| All %N_P heading elements are properly nested
| yes
|
| Manual Check: Singular
| empty string
| yes
|
| Manual Check: Plural
| empty string
| yes
|
| Some Fail
| %N_F out of %N_T heading elements are NOT properly nested
| yes
|
| All Fail: Singular
| empty string
| yes
|
| All Fail: Plural
| None of the %N_F heading elements are properly nested
| yes
|
| Corrective Action: Singular
| empty string
| yes
|
| Corrective Action: Plural
| empty string
| yes
|
| Not Applicable
| No or only one heading elements on this page, so nesting rule does not apply
| yes
|
Heading Rule 5: Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| %1 element is properly nested
| yes
|
| Pass 2
| All heading elements are properly nested
| yes
|
| Pass 3
| empty string
| yes
|
| Manual Check 1
| empty string
| yes
|
| Manual Check 2
| empty string
| yes
|
| Manual Check 3
| empty string
| yes
|
| Corrective Action 1
| Change %1 element or other heading elements
| yes
|
| Corrective Action 2
| Add text content to %1 element that describes the section it labels or remove it from the page if it is not needed
| yes
|
| Corrective Action 3
| One heading element is not prperly nested, check all heading elements to make sure they are properly nested, and describe the structure and the sections of the web pag
| yes
|
| Hidden (i.e. thru css)
| %1 element is hidden from asssistive technologies and is not included in nesting.
| yes
|
| Presentation (i.e. role=presentation)
| empty string
| yes
|
| Other
| empty string
| yes
|
new rule nls id : new rule summary
| Property
| Value(s)
| Up To Date
|
| Definition
| definition
| NO
|
| Summary
| summary
| NO
|
| Purpose
|
- purpose 1
- purpose 2
- purpose 3
- purpose 4
| NO
|
| Rule ID
| rule id
| NO
|
| NLS Rule ID
| rule nls id
| NO
|
| Techniques
|
- technique 1
- technique 1 url
- technique 2
- technique 2 url
- technique 3
- technique 3 url
- technique 4
- technique 4 url
| NO
|
| Manual Checks
|
- manual check 1
- manual 1 url
- manual check 2
- manual 2 url
- manual check 3
- manual 3 url
- manual check 4
- manual 4 url
| NO
|
| Scope
| Element or Page
| NO
|
| WCAG 2.0 Primary
| X.X.X
| NO
|
| WCAG 2.0 Related
|
| NO
|
| Language Dependency
| empty string
| NO
|
| Rule Category
| Heading
| NO
|
| Target Resources
|
| NO
|
| Target Resources Description
| target resource nls description
| NO
|
| Resource Properties
|
| NO
|
new rule nls id : Rule Result Messages
| Property
| Value(s)
| Up To Date
|
| All Pass: Singular
| empty string
| NO
|
| All Pass: Plural
| empty string
| NO
|
| Manual Check: Singular
| empty string
| NO
|
| Manual Check: Plural
| empty string
| NO
|
| Some Fail
| empty string
| NO
|
| All Fail: Singular
| empty string
| NO
|
| All Fail: Plural
| empty string
| NO
|
| Corrective Action: Singular
| empty string
| NO
|
| Corrective Action: Plural
| empty string
| NO
|
| Not Applicable
| empty string
| NO
|
new rule nls id : Node Result Messages
| Property
| Value(s)
| Up To Date
|
| Pass 1
| empty string
| NO
|
| Pass 2
| empty string
| NO
|
| Pass 3
| empty string
| NO
|
| Manual Check 1
| empty string
| NO
|
| Manual Check 2
| empty string
| NO
|
| Manual Check 3
| empty string
| NO
|
| Corrective Action 1
| empty string
| NO
|
| Corrective Action 2
| empty string
| NO
|
| Corrective Action 3
| empty string
| NO
|
| Hidden (i.e. thru css)
| empty string
| NO
|
| Presentation (i.e. role=presentation)
| empty string
| NO
|
| Other
| empty string
| NO
|
