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
2-operable/2.1.1-keyboard.md
+53
View File
@@ -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)
2-operable/2.1.2-no-keyboard-trap.md
+37
View File
@@ -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)
2-operable/2.1.3-keyboard-no-exception.md
+28
View File
@@ -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)
2-operable/2.1.4-character-key-shortcuts.md
+39
View File
@@ -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)
2-operable/2.2.1-timing-adjustable.md
+58
View File
@@ -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)
2-operable/2.2.2-pause-stop-hide.md
+53
View File
@@ -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)
2-operable/2.2.3-no-timing.md
+28
View File
@@ -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)
2-operable/2.2.4-interruptions.md
+36
View File
@@ -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)
2-operable/2.2.5-re-authenticating.md
+34
View File
@@ -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)
2-operable/2.2.6-timeouts.md
+34
View File
@@ -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)
2-operable/2.3.1-three-flashes-or-below-threshold.md
+34
View File
@@ -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)
2-operable/2.3.2-three-flashes.md
+28
View File
@@ -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)
2-operable/2.3.3-animation-from-interactions.md
+30
View File
@@ -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)
2-operable/2.4.1-bypass-blocks.md
+40
View File
@@ -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)
2-operable/2.4.10-section-headings.md
+34
View File
@@ -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)
2-operable/2.4.11-focus-not-obscured-minimum.md
+38
View File
@@ -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)
2-operable/2.4.12-focus-not-obscured-enhanced.md
+34
View File
@@ -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)
2-operable/2.4.13-focus-appearance.md
+53
View File
@@ -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)
2-operable/2.4.2-page-titled.md
+40
View File
@@ -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)
2-operable/2.4.3-focus-order.md
+39
View File
@@ -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)
2-operable/2.4.4-link-purpose-in-context.md
+55
View File
@@ -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)
2-operable/2.4.5-multiple-ways.md
+37
View File
@@ -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)
2-operable/2.4.6-headings-and-labels.md
+29
View File
@@ -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)
2-operable/2.4.7-focus-visible.md
+40
View File
@@ -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)
2-operable/2.4.8-location.md
+36
View File
@@ -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)
2-operable/2.4.9-link-purpose-link-only.md
+47
View File
@@ -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)
2-operable/2.5.1-pointer-gestures.md
+38
View File
@@ -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)
2-operable/2.5.2-pointer-cancellation.md
+48
View File
@@ -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)
2-operable/2.5.3-label-in-name.md
+46
View File
@@ -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)
2-operable/2.5.4-motion-actuation.md
+39
View File
@@ -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)
2-operable/2.5.5-target-size-enhanced.md
+45
View File
@@ -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)
2-operable/2.5.6-concurrent-input-mechanisms.md
+34
View File
@@ -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)
2-operable/2.5.7-dragging-movements.md
+37
View File
@@ -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)
2-operable/2.5.8-target-size-minimum.md
+43
View File
@@ -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)
2-operable/index.md
+64
View File
@@ -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)