Principle 2: Operable
Accessibility Guidelines for Higher Education
Users must be able to operate the interface (the interface cannot require interaction that a user cannot perform).
The Guidelines under this Principle state that you should ensure the user interface components and navigation are operable. Create content that is keyboard accessible, gives users enough time to read content and interact with it, does not induce seizures, and be easily navigated.
Is your Content Operable?
The questions below are designed to assist you in determining if your site, application, and/or content is operable to people with disabilities. Each question is linked to in-depth information, resources, and examples of how the guidelines benefit our users.
SUCCESS CRITERION 2.1.1 — LEVEL A
Keyboard
Can all functionality and content be operated through the use of a keyboard or keyboard interface?
SUCCESS CRITERION 2.1.2 — LEVEL A
No Keyboard Trap
Can keyboard users navigate the site or application content and not get “trapped” within components on the page?
SUCCESS CRITERION 2.1.4 — LEVEL A
Character Key Shortcuts
If your site or application provides character key shortcuts (letters, numbers, punctuation, symbols) is there a way for users to turn off or reconfigure the shortcuts?
SUCCESS CRITERION 2.2.1 — LEVEL A
Timing Adjustable
If your site or application uses time limits, are users able to turn off or adjust the limits?
SUCCESS CRITERION 2.2.2 — LEVEL A
Pause, Stop, Hide
Can moving, blinking, scrolling or auto-updating content be paused, stopped or hidden by the user?
SUCCESS CRITERION 2.3.1 — LEVEL A
Three Flashes or Below Threshold
Have you ensured that your site or application does not contain flashing content?
SUCCESS CRITERION 2.4.1 — LEVEL A
Bypass Blocks
Is there a way for users to bypass blocks of content such as setting controls and large navigation areas in order to skip to the main content?
SUCCESS CRITERION 2.4.2 — LEVEL A
Page Titled
Does every page in your site, application or document have a descriptive title?
SUCCESS CRITERION 2.4.3 — LEVEL A
Focus Order
Does the content on your site or application follow a logical order when navigating by keyboard?
SUCCESS CRITERION 2.4.4 — LEVEL A
Link Purpose (In Context)
Does every link in your site or application have text that describes the purpose of the link?
SUCCESS CRITERION 2.4.5 — LEVEL AA
Multiple Ways
Is there more than one way for a user to locate content within your site or application?
SUCCESS CRITERION 2.4.6 — LEVEL AA
Headings and Labels
Are headings and labels in your site or application clear and descriptive?
SUCCESS CRITERION 2.4.7 — LEVEL AA
Focus Visible
In your site or application, do you provide a visual focus indicator for content that can be activated with the keyboard?
SUCCESS CRITERION 2.5.1 — LEVEL A
Pointer Gestures
Does your site or application have an alternative to operate complex screen gestures such as pinch zooming, sliders, and swiping?
SUCCESS CRITERION 2.5.2 — LEVEL A
Pointer Cancellation
Does your site or application have functionality for users to prevent or cancel an operation using a single point of contact (e.g. single taps and clicks, double-taps and clicks, long presses, and path-based gestures)?
SUCCESS CRITERION 2.5.3 — LEVEL A
Label in Name
Does the visual text label (e.g. in menus, links, buttons, and form fields) match the accessible name in your site or application?
SUCCESS CRITERION 2.5.4 — LEVEL A
Motion Actuation
If your application uses motion to operate a component, is there alternative functionality (e.g. button, link) to provide the same result?