The goal of this guide is to help create a shared set of test cases — with clear, step-by-step instructions — to support QAs and developers in performing keyboard accessibility tests with confidence.
By following these structured steps, teams can consistently identify and fix issues that affect keyboard navigation, ensuring that we're building websites that are accessible to everyone.
Create a practical guide focused on keyboard accessibility testing. This guide will include:
- The WCAG 2.2 Success Criterion being validated
- The acceptance criteria for passing that Success Criterion
- A set of test cases, with step-by-step instructions, that must be performed to ensure the website meets the requirements of the specific Success Criterion
The goal is to make it easier for teams to integrate accessibility checks into their regular QA process, helping to ensure that Drupal websites are usable for keyboard-only users.
Active
New documentation
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
On this link https://www.drupal.org/docs/getting-started/accessibility/how-to-do-an-a... → i'd like to have a new link to address to a new page
Sounds useful. I'd love to see some proposed language here.