Body
What Is a Quick Test?
A quick test is a streamlined accessibility check that typically takes 15 to 20 minutes. It’s designed to answer one key question:
Can the major use cases of this product be completed using only a keyboard, without a mouse?
This question is essential because many users with disabilities rely on keyboard navigation due to motor impairments, vision loss, or other conditions that make mouse use difficult or impossible.
Quick tests are not a substitute for full accessibility evaluations, but they are an effective way to identify some blockers – issues that prevent users from completing tasks – and barriers – issues that make tasks frustrating or inefficient.
What Are Use Cases?
Use cases are short, task-based scenarios that describe what different user populations need to do within a product. They help focus the test on real-world functionality.
For example, if you’re evaluating assessment software, major use cases might include:
- A student taking an exam
- An instructor creating an exam
- A staff member generating reports
Devices and Platforms You Can Test
Quick tests can be performed on computers, phones, and tablets for a wide range of platforms:
- Web-based applications
- Mobile apps
- Desktop software
All you need is a keyboard. For mobile and tablet testing, connect a physical keyboard to the device using Bluetooth or a USB cable.
Keyboard Navigation Basics
If you’re new to keyboard testing, here are some essential tips:
- Tab key: Moves focus forward to the next interactive element (e.g., buttons, links, form fields).
- Shift + Tab: Moves focus backward.
- Arrow keys: Used to navigate within groups of elements (e.g., radio buttons, menus).
- F6 key: Often used to switch between sections in desktop applications.
- Enter key: Activates the focused element (e.g., clicks a button).
- Space bar: Often used to check checkboxes or toggle switches.
- Escape key: Closes pop-up boxes or menus.
Not all elements on the screen will receive focus; that’s expected. Only interactive elements should be focusable.
If you are testing a desktop application, search “product name keyboard shortcuts” for a full list of actions you can take using the keyboard.
What to Check During a Quick Test
As you perform the test, evaluate the product against four key criteria:
- Keyboard Functionality
Can all mouse-based actions be performed using only the keyboard?
- Logical Focus Order
Does the keyboard focus move through the page in a logical, predictable order, or does it jump around unexpectedly?
- Visible Focus Indicator
Does every element that receives keyboard focus have a visible indicator that is easy to see and stands out clearly from the background and nearby content?
- Escape Mechanism
If a pop-up box appears or focus gets stuck somewhere, can you get out of it using only the Escape key or a keyboard-accessible close button?
Encountering Blockers
- Blockers are critical failures. They prevent users from completing tasks. A lack of keyboard functionality or escape mechanisms are blockers.
- Barriers are frustrating but not insurmountable. Users may be able to work around them, but they still impact accessibility. Illogical focus order or a lack of visible focus indicators are barriers.
If you encounter a blocker, stop testing the product and perform quick tests on alternative products. If an alternative product exists that both meets your business or instructional needs and does not have blockers, you must select that product for purchase. An accommodation-based exception cannot be granted if more accessible products are available.
If all alternatives also have blockers, complete the quick test on your choice of product and work with your unit’s Accessibility Coordinator to file an accommodation-based exception request.
Documenting Your Findings
Use the Quick Test Evaluation Template (docx) to record:
- The product name and version
- The accessibility risk rating
- Each use case tested
- Any blockers or barriers found
- Screenshots or notes to support your findings
If the selected product has blockers or barriers, work with your unit’s Accessibility Coordinator to file an accommodation-based exception request. Include your quick test report as supporting documentation.
Final Thoughts
Quick tests are a fast, effective way to identify major accessibility issues, especially blockers that prevent users with disabilities from completing tasks. They help units make informed decisions and prioritize accessibility early in the procurement process.
If you need help performing a quick test or exploring alternative products, contact your unit’s Accessibility Coordinator.