Operable Flashcards
Operable
User interface components and navigation must be operable.
- Users must be able to operate the interface which cannot require an interaction the user cannot perform.
Success Criteria (SC) 2.1.1
Ensure all functionality available through a pointing device can also be accessed and executed using only a physical keyboard or keyboard interface.
Shortcut Keys
- Implemented to directly access application functions.
- Application-specific shortcut keys must not interfere with these standard shortcuts
Exception for SC 2.1.1
- When the underlying function requires input that depends on the path of the user’s movement and not just the end points.
- Distinguishes actions that cannot be controlled with a keyboard.
- The path is irrelevant
SC 2.12
All users must be able to navigate to use websites, documents, and applications.
Keyboard Trap
Occurs when a person who uses a keyboard cannot move focus away from an interactive element or control using the keyboard.
2.4.7 Focus Visible
Any keyboard-operable user interface has a mode of operation where the keyboard focus indicator is visible
SC 2.4.3 Focus Order
- Provides a method for users with disabilities to navigate information on a web page sequentially and logically using a keyboard
SC 2.1.2 No Key Board Trap
Allowing keyboard navigation from the first element to the last element on a web page and back to the first element
- Ensure users with disabilities are able to interact with the whole web page.
SC 2.1.1 Keyboard
Operable, by ensuring that all functionality can be accessed and activated by keyboard with requiring special timing of individual keystrokes.
SC 2.4.3 Focus Order
Without Vision or with limited vision
- With limited manipulation
- With limited language, cognitive, and learning abilities
SC 2.4.7 Focus Visible
Allow keyboard users to land on hidden elements between areas of visible focus.
SC 2.4.3 Focus Order
Create a logical tab order through links, form controls, and objects.
Disabilities Impacted by Nonconformance with SC 2.1.2 No Keyboard Trap
- With limited vision
- With limited manipulation
- With limited reach and strength
- With limited language, Cognitive, and learn abilities
Disabilities Impacted by Nonconformance with SC 2.1.1 Keyboard
- Without Vision or With Limited Vision
- With Limited Manipulation
- With Limited Reach and Strength
Principle & Intent of SC 2.4.7 Focus Visible
Operable, to ensure keyboard users know which element has the keyboard focus.
2.4.4 Link Purpose (In Context)
Purpose of each link can be determined from the link text alone or from the link text together with it programmatically determined link context
SC 2.4.4 Link Purpose (In Context)
- Supports the principle of Operable because it impacts a user’s ability to navigate content by understanding what the link is for and where it will take the user.
SC 2.4.1 Bypass Blocks
All users must be able to navigate the web site, including bypassing repetitive information in order to get to the the main content
Intent of SC 2.4.1 Bypass Block
- Ensures a method is provided to skip blocks of repeated content so that the user can go to the main content without having to hear or tab through repetitive information.
Repeated Blocks of Content
Content that appears on the other pages within a website prior to the main page content itself.
SC 2.4.5 Multiple Ways
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 in a step in, a process
Disabilities Impacted by Nonconformance with SC 2.4.6 Headings and Labels
- Without Vision or With Limited Vision
- With Limited Manipulation; With Limited Reach and Strength
- With Limited Language, Cognitive and Learning Abilities
2.4.5 Multiple Ways Does Not Apply
When the Web Page being shown is a result of a task or a step in a process
