You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 01Keyboard.md
+25-12Lines changed: 25 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -25,31 +25,44 @@ Limitations, Assumptions, or Exceptions
25
25
------------------------------------
26
26
**Baseline Test ID:** 1.1-KeyboardAccess
27
27
### Identify Content
28
-
All functionality of the content that is available by mouse control must be keyboard accessible. Determine the functionality of visible and hidden interactive interface components (links, form fields, drop down menus, show/hide content, tree views, pop ups/light boxes, iframes, etc.) available using a mouse (hover and/or click).
28
+
<pid="IC">All functionality of the content that is available by mouse control must be keyboard accessible. Determine the functionality of visible and hidden interactive interface components (links, form fields, drop down menus, show/hide content, tree views, pop ups/light boxes, iframes, etc.) available using a mouse (hover and/or click).</p>
29
29
30
30
### Test Instructions
31
-
1. Check that all functionality can be accessed and executed using only the keyboard. [SC 2.1.1]
32
-
1. Use the keyboard to perform functions available by mouse (including drop-down menus, form fields, revealing/hiding content, tooltips, AND all interactive interface components).
33
-
1. If an interactive interface component is not available by keyboard, check if another control is provided on the page with the same functionality which is available by keyboard. (All functionality must meet this requirement.)
34
-
2. Check that individual keystrokes do not require specific timings for activation.[SC 2.1.1]
35
-
1. If operation requires specific timings of individual keystrokes, check if another control is provided on the page with the same functionality which does not require specific timings for operation. (All functionality must be available without requiring specific timings for individual keystrokes to operate.)
31
+
<olid="1TI">
32
+
<liid="1TI-1">Check that all functionality can be accessed and executed using only the keyboard. [SC 2.1.1]</li>
33
+
<ol>
34
+
<li id="1TI-1i">Use the keyboard to perform functions available by mouse (including drop-down menus, form fields, revealing/hiding content, tooltips, AND all interactive interface components).</li>
35
+
<ol>
36
+
<li id="1TI-1ia">If an interactive interface component is not available by keyboard, check if another control is provided on the page with the same functionality which is available by keyboard. (All functionality must meet this requirement.)</li>
37
+
</ol>
38
+
</ol>
39
+
<liid="1TI-2">Check that individual keystrokes do not require specific timings for activation.[SC 2.1.1]</li>
40
+
<ol>
41
+
<li id="1TI-2i">If operation requires specific timings of individual keystrokes, check if another control is provided on the page with the same functionality which does not require specific timings for operation. (All functionality must be available without requiring specific timings for individual keystrokes to operate.)</li>
42
+
</ol>
43
+
</ol>
36
44
37
45
### Test Results
38
-
If any of the above checks fail, then Baseline Test 1.1-KeyboardAccess fails.
46
+
<pid="1TR">If any of the above checks fail, then Baseline Test 1.1-KeyboardAccess fails.</p>
39
47
40
48
1.2 Test Procedure for No Keyboard Trap
41
49
--------------------------------------------
42
50
**Baseline Test ID:** 1.2-NoKeyboardTrap
43
51
### Identify Content
44
-
Components that receive keyboard focus.
52
+
<pid="2IC">Components that receive keyboard focus.</p>
45
53
46
54
### Test Instructions
47
-
1. Check that focus can be moved away from the component. There must be NO “TRAP” that disrupts keyboard navigation.[SC 2.1.2, Conformance Requirement 5]
48
-
1. If a keyboard trap is found, inspect any help (contextual help, or application help) and documentation for notification of available alternate keyboard commands (e.g., non-standard keyboard controls, access keys, hotkeys).
49
-
2. If nonstandard keyboard commands are required to navigate away from a component or set of components, check that the commands work.
55
+
<olid="2TI">
56
+
<liid="2TI-1">Check that focus can be moved away from the component. There must be NO “TRAP” that disrupts keyboard navigation.[SC 2.1.2, Conformance Requirement 5]</li>
57
+
<ol>
58
+
<li id="2TI-1i">If a keyboard trap is found, inspect any help (contextual help, or application help) and documentation for notification of available alternate keyboard commands (e.g., non-standard keyboard controls, access keys, hotkeys).</li>
59
+
<li id="2TI-1ii">If nonstandard keyboard commands are required to navigate away from a component or set of components, check that the commands work.</li>
60
+
</ol>
61
+
</ol>
50
62
51
63
### Test Results
52
-
If the above check fails, then Baseline Test 1.2-NoKeyboardTrap fails.
64
+
<pid="2TR">If the above check fails, then Baseline Test 1.2-NoKeyboardTrap fails.
Copy file name to clipboardExpand all lines: 02FocusVisible.md
+35-22Lines changed: 35 additions & 22 deletions
Original file line number
Diff line number
Diff line change
@@ -36,50 +36,63 @@ Limitations, Assumptions, or Exceptions
36
36
**Baseline Test ID:** 2.1-FocusVisible
37
37
38
38
### Identify Content
39
-
40
-
Keyboard accessible interface components (e.g., links, form fields, drop down menus, show/hide content, tree views, pop ups/light boxes, frames, iframes).
39
+
<pid="1IC">Keyboard accessible interface components (e.g., links, form fields, drop down menus, show/hide content, tree views, pop ups/light boxes, frames, iframes).</p>
41
40
42
41
### Tests Instructions
43
-
1. Use the keyboard to navigate through each interface component.
44
-
2. Check that a visible indication of focus is provided when focus is on the interface component.[SC 2.4.7]
42
+
<olid="1TI">
43
+
<li id="1TI-1">Use the keyboard to navigate through each interface component.</li>
44
+
<li id="1TI-2">Check that a visible indication of focus is provided when focus is on the interface component.[SC 2.4.7]</li>
45
+
</ol>
45
46
46
47
### Test Results
47
-
-If any of the above checks fail, then Baseline Test 2.1-FocusVisible fails.
48
+
<pid="1TR">If any of the above checks fail, then Baseline Test 2.1-FocusVisible fails.</p>
48
49
49
50
2.2 Test Procedure for Focus Order
50
51
---------------------------------------
51
52
**Baseline Test ID:** 2.2-FocusOrder
52
53
### Identify Content
53
-
Keyboard accessible interface components (links, form fields, drop down menus, show/hide content, tree views, pop ups/light boxes, frames, iframes, etc.) that have a meaningful sequence of navigation.
54
+
<pid="2IC">Keyboard accessible interface components (links, form fields, drop down menus, show/hide content, tree views, pop ups/light boxes, frames, iframes, etc.) that have a meaningful sequence of navigation.</p>
54
55
55
56
### Test Instructions
56
-
1. Use the keyboard to navigate through interface components.
57
-
1. Use the keyboard to activate trigger controls that reveal hidden content (menus, dialogs, expandable tree list, etc.).
58
-
1. Check that the revealed focusable content is included in the focus order. [SC 2.4.3]
59
-
2. Advance the focus through the revealed content.
60
-
1. Use the keyboard to close/hide the revealed content.
61
-
1. Check that focus is returned to the trigger control. (It is acceptable to Shift+ TAB once or use an arrow key to move the focus backward to the trigger control. [SC 2.4.3]
62
-
2. Check that the focus order preserves the meaning and usability of the page. [SC 2.4.3]
57
+
<olid="2TI">
58
+
<li id="2TI-1">Use the keyboard to navigate through interface components.</li>
59
+
<ol>
60
+
<li id="2TI-1i">Use the keyboard to activate trigger controls that reveal hidden content (menus, dialogs, expandable tree list, etc.).</li>
61
+
<ol>
62
+
<li id="2TI-1ia">Check that the revealed focusable content is included in the focus order. [SC 2.4.3]</li>
63
+
<li id="2TI-1ib">Advance the focus through the revealed content.</li>
64
+
</ol>
65
+
<li id="2TI-1ii">Use the keyboard to close/hide the revealed content.</li>
66
+
<ol>
67
+
<li id="2TI-1iia">Check that focus is returned to the trigger control. (It is acceptable to Shift+ TAB once or use an arrow key to move the focus backward to the trigger control. [SC 2.4.3]</li>
68
+
</ol>
69
+
</ol>
70
+
<li id="2TI-2">Check that the focus order preserves the meaning and usability of the page. [SC 2.4.3]</li>
71
+
</ol>
63
72
64
73
### Test Results
65
-
If any of the above checks fail, then Baseline Test 2.2-FocusOrder fails.
74
+
<pid="2TR">If any of the above checks fail, then Baseline Test 2.2-FocusOrder fails.</p>
66
75
67
76
2.3 Test Procedure for On Focus
68
77
------------------------------------
69
78
**Baseline Test ID:** 2.3-OnFocus
70
79
### Identify Content
71
-
Keyboard accessible interface components (links, form fields, drop down menus, show/hide content, tree views, pop ups/light boxes, frames, iframes, etc.).
80
+
<pid="3IC">Keyboard accessible interface components (links, form fields, drop down menus, show/hide content, tree views, pop ups/light boxes, frames, iframes, etc.).</p>
72
81
73
82
### Test Instructions
74
-
1. Use the keyboard to move focus to and navigate through each interactive interface component (including form drop-down lists and form fields).
75
-
2. Check that when an interface component receives focus, it does not initiate an unexpected change of context. [SC 3.2.1]
76
-
1. Examples of a change of context include:
77
-
- Forms submitted automatically when a component receives focus
78
-
- New windows launched when a component receives focus
79
-
- Focus is moved to another component
83
+
<olid="3TI">
84
+
<li id="3TI-1">Use the keyboard to move focus to and navigate through each interactive interface component (including form drop-down lists and form fields).</li>
85
+
<li id="3TI-2">Check that when an interface component receives focus, it does not initiate an unexpected change of context. [SC 3.2.1]<br>
86
+
Examples of a change of context include:</li>
87
+
<ul>
88
+
<li>Forms submitted automatically when a component receives focus</li>
89
+
<li>New windows launched when a component receives focus</li>
90
+
<li>Focus is moved to another component</li>
91
+
</ul>
92
+
</ol>
80
93
81
94
### Test Results
82
-
If any of the above checks fail, then Baseline Test 2.3-OnFocus fails.
95
+
<pid="3TR">If any of the above checks fail, then Baseline Test 2.3-OnFocus fails.</p>
Copy file name to clipboardExpand all lines: 04RepetitiveContent.md
+24-16Lines changed: 24 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -22,44 +22,52 @@ To enable equitable use by keyboard-only users, there must be a keyboard-accessi
22
22
-----------------------------------------
23
23
**Baseline Test ID:** 4.1-BypassBlocks
24
24
### Identify Content
25
-
Blocks of content that are repeated on multiple pages, including navigation links, page headers, and banners.
25
+
<pid="1IC">Blocks of content that are repeated on multiple pages, including navigation links, page headers, and banners.</p>
26
26
27
27
### Test Instructions
28
-
1. Use standard keyboard commands to navigate forward to repetitive blocks of content. Some bypass functions may not be visible until they receive focus.
29
-
2. Check that a keyboard-accessible method is provided to bypass repetitive content. [SC 2.4.1]
30
-
3. Use the keyboard to activate the bypass method and verify the functionality of the bypass function.
31
-
4. Check that the method works as intended. [SC 2.4.1]
32
-
1. For example:
33
-
- The block of repeated content is hidden, closed or skipped.
34
-
- If the method is intended to skip, check that the focus is shifted past the repetitive content only. Content that is not repetitive should not be skipped. If there is only text/no interactive component to receive the shift of focus, it may not be evident that a focus shift occurred.
28
+
<olid="1TI">
29
+
<li id="1TI-1">Use standard keyboard commands to navigate forward to repetitive blocks of content. Some bypass functions may not be visible until they receive focus.</li>
30
+
<li id="1TI-2">Check that a keyboard-accessible method is provided to bypass repetitive content. [SC 2.4.1]</li>
31
+
<li id="1TI-3">Use the keyboard to activate the bypass method and verify the functionality of the bypass function.</li>
32
+
<li id="1TI-4">Check that the method works as intended. [SC 2.4.1]<br>
33
+
For example:</li>
34
+
<ul>
35
+
<li>The block of repeated content is hidden, closed or skipped.</li>
36
+
<li>If the method is intended to skip, check that the focus is shifted past the repetitive content only. Content that is not repetitive should not be skipped. If there is only text/no interactive component to receive the shift of focus, it may not be evident that a focus shift occurred.</li>
37
+
</ul>
38
+
</ol>
35
39
36
40
### Test Results
37
-
If any of the above checks fail, then Baseline Test 4.1-BypassBlocks fails.
41
+
<pid="1TR">If any of the above checks fail, then Baseline Test 4.1-BypassBlocks fails.</p>
38
42
39
43
4.2 Test Procedure for Consistent Navigation
40
44
-------------------------------------------------
41
45
**Baseline Test ID:** 4.2-ConsistentNavigation
42
46
### Identify Content
43
-
Navigational mechanisms that are repeated on multiple pages (which may or may not be contained within a block of content).
47
+
<pid="2IC">Navigational mechanisms that are repeated on multiple pages (which may or may not be contained within a block of content).</p>
44
48
45
49
### Test Instructions
46
-
1. Review multiple Web pages. Do not initiate changes to the content.
47
-
2. Check that each repeated navigational mechanism is in the same relative order as other repeated interface components on each Web page where it appears. [SC 3.2.3]
50
+
<olid="2TI">
51
+
<li id="2TI-1">Review multiple Web pages. Do not initiate changes to the content.</li>
52
+
<li id="2TI-2">Check that each repeated navigational mechanism is in the same relative order as other repeated interface components on each Web page where it appears. [SC 3.2.3]</li>
53
+
</ol>
48
54
49
55
### Test Results
50
-
If any of the above checks fail, then Baseline Test 4.2-ConsistentNavigation fails.
56
+
<pid="2TR">If any of the above checks fail, then Baseline Test 4.2-ConsistentNavigation fails.</p>
**Baseline Test ID:** 4.3-ConsistentIdentification
55
61
### Identify Content
56
-
Components that have the same functionality within a set of Web pages.
62
+
<pid="3IC">Components that have the same functionality within a set of Web pages.</p>
57
63
58
64
### Test Instructions
59
-
1. Check that associated text (e.g., label, name, or text alternative) for identified content is identical for each instance where they perform the same function. [SC 3.2.4]
65
+
<olid="3TI">
66
+
<li id="3TI-1">Check that associated text (e.g., label, name, or text alternative) for identified content is identical for each instance where they perform the same function. [SC 3.2.4] </li>
67
+
</ol>
60
68
61
69
### Test Results
62
-
If any of the above checks fail, then Baseline Test 4.3-ConsistentIdentification fails.
70
+
<pid="3TR">If any of the above checks fail, then Baseline Test 4.3-ConsistentIdentification fails.</p>
Copy file name to clipboardExpand all lines: 05Changing.md
+30-16Lines changed: 30 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -20,26 +20,40 @@ Limitations, Assumptions, or Exceptions
20
20
---------------------------------------------
21
21
**Baseline Test ID:** 5.1-ChangeContent
22
22
### Identify Content
23
-
Identify changes in presented content (both user driven and automatic). Examples include changes to images, navigation trees, data table sort controls, automatic information updates, form elements, revealed content, etc.
24
-
- It may be necessary to use the mouse to determine whether state changes occur on hover or on click.
25
-
- Depending on the component, a change of state may be triggered by various actions, such as changing values or states of other components, toggling a function, entering data in the component, mouseover, etc.
23
+
<olid="1IC">
24
+
<liid="1IC-1">Identify changes in presented content (both user driven and automatic). Examples include changes to images, navigation trees, data table sort controls, automatic information updates, form elements, revealed content, etc.</li>
25
+
<ul>
26
+
<li>It may be necessary to use the mouse to determine whether state changes occur on hover or on click.</li>
27
+
<li>Depending on the component, a change of state may be triggered by various actions, such as changing values or states of other components, toggling a function, entering data in the component, mouseover, etc.</li>
28
+
</ul>
29
+
</ol>
26
30
27
31
### Test Instructions
28
-
29
-
1. Check that the page provides a notification of the change in content programmatically. [SC 4.1.2]
30
-
* Programmatic event notifications include alert dialogs, focus shifts to the content that changed, and ARIA live regions.
31
-
1. For each change in content, check that the combination of name, role, state, and value of the changed content is accurate. [SC 4.1.2]
32
-
* Name: the name is accurate after a change.
33
-
* Apply the [accessible name and description computation](https://www.w3.org/TR/html-aam-1.0/#accessible-name-and-description-computation), if applicable.
34
-
35
-
* Role: the role accurately describes the purpose of the element after a change, if applicable.
36
-
* Consider ARIA role, element type, and other descriptive text.
37
-
* State: the state of the element is accurate after a change, if applicable
38
-
* Evaluate ARIA and element-specific attributes (e.g., `<option selected=”true”>`)
39
-
* Value: the value is updated after a change, if applicable.
32
+
<olid="1TI">
33
+
<liid="1TI-1">Check that the page provides a notification of the change in content programmatically. [SC 4.1.2]</li>
34
+
<ul>
35
+
<li>Programmatic event notifications include alert dialogs, focus shifts to the content that changed, and ARIA live regions.</li>
36
+
</ul>
37
+
<liid="1TI-2">For each change in content, check that the combination of name, role, state, and value of the changed content is accurate. [SC 4.1.2]</li>
38
+
<ol>
39
+
<li id="1TI-2i">Name: the name is accurate after a change. </li>
40
+
<ul>
41
+
<li>Apply the <a href="https://www.w3.org/TR/html-aam-1.0/#accessible-name-and-description-computation">accessible name and description computation</a>, if applicable.</li>
42
+
</ul>
43
+
<li id="1TI-2ii">Role: the role accurately describes the purpose of the element after a change, if applicable.</li>
44
+
<ul>
45
+
<li>Consider ARIA role, element type, and other descriptive text.</li>
46
+
</ul>
47
+
<li id="1TI-2iii">State: the state of the element is accurate after a change, if applicable.</li>
48
+
<ul>
49
+
<li>Evaluate ARIA and element-specific attributes (e.g., <code><option selected=”true”></code>).</li>
50
+
</ul>
51
+
<li id="1TI-2iv">Value: the value is updated after a change, if applicable.</li>
52
+
</ol>
53
+
</ol>
40
54
41
55
### Test Results
42
-
-If any of the above checks fail, then Baseline Test 5.1-ChangeContent fails.
56
+
<pid="1TR">If any of the above checks fail, then Baseline Test 5.1-ChangeContent fails.</p>
0 commit comments