Manual accessibility testing
Manual accessibility testing
Introduction
Manual accessibility testing is needed to address the
Deque's
Keyboard-only testing
Keyboard accessibility is one of the most important aspects of accessibility testing and should be carried out frequently during development.
Retrofitting keyboard accessibility can be expensive. This is a problem if libraries and frameworks you use are not accessible, where the options are to fix the component library or swap to a different one.
Some reasons people might rely on a keyboard include:
-
People who are
blind might use a screen reader and are generally unable see the cursor on the screen. -
Users with
motor disabilities may not have the fine motor movements required for using a mouse. -
People with
chronic conditions , such as Repetitive Strain Injury (RSI), may need to avoid using a mouse. -
There are also power users who prefer to use the keyboard commands and shortcuts for speed and efficiency.
WebAIM describes
The
You can read more specific instructions for
Full manual accessibility testing
To fully check for accessibility compliance, you need to work through the WCAG 2.2 Level A and AA criteria.
The WCAG requirements form the basis of the
The Web Accessibility Initative (WAI) has good documentation on
Full manual testing is required on all the main pages of your app. Many apps use templates and common components so these only need to be tested the once with relevant variants to get full coverage.
The Design System recommends the
Testing with assistive technologies