One thing very specifically noted in the case of accessibility testing is that it is much focused on the use of screen readers and ensuring compliance. However, it is necessary for this to be screen reader-focused, or if there are other aspects of accessibility to be checked. As screen readers are mostly for people with visual disabilities, so whether accessibility needs to take a broader perspective to ensure compliance? From the accessibility testing point of view, we are trying to answer some of such questions here.
AccessiBe Q&A
Can accessibility testing be performed without the use of screen readers?
Yes, it is absolutely possible. We can run accessibility testing without using screen readers. In terms of testing, a screen reader is just one of the tools for finding any bugs manually. Through automation, capturing many of the accessibility issues can be easier. However, AccessiBe experts recommend that manual audit and visual inspection is the best way for testing. Apart from screen readers, using a keyboard and a manual review of the code are also ways to identify accessibility vulnerabilities.
Is it possible to scale up accessibility without screen readers?
This can be achieved if the one who performs accessibility testing is well versed in reviewing the code fast to find bugs. However, these types of skills are not so easy to find in average testers. So, it is possible to do accessibility testing without the device, but the testers should be highly experienced and knowledgeable in the same.
What are the skills needed to conduct accessibility testing manually without using a screen reader?
The testers need to have good knowledge of HTML and CSS. They must know JavaScript and also the ARIA landmarks to be followed. It is essential to have in-depth knowledge of WCAG guidelines also to evaluate accessibility compliance. As the testing involves manually checking the code and noting down the bugs, one should also be proficient in code checking skills.
How long will it take to run accessibility testing?
With the use of screen readers, it may take about three hours on average to complete testing a medium to a complex web page. It may take another hour or so to log and document the bugs. However, an expert tester may take only lesser time for the same. Without a screen reader, order to complete the test fully manually, it may take double the same. For example, an average to a complex web page may take 8 hours or more for the same without screen readers.
Benefits of screen readers
- Using screen readers will help testers identify many accessibility failures even without coding knowledge.
- Vulnerabilities in dynamic content updates and status messages will be exposed.
- Group label association of form controls can be identified with screen readers.
- Screen readers can also identify reading order, eye focus order, etc., can also be identified with screen readers.
- With a screen reader, it is also checked for meaningful alt texts and link descriptions.
Even though it is possible to run the test without screen readers, AccessiBe recommends that it is ideal to have a screen reader for testing for the above reasons.
Comments