Everything You Should Know About Accessibility Testing

by Yana Bozhko | August 18, 2021 8:11 am

The most famous and bright example of why content accessibility testing should be done happened with the popular anime Pokemon: over 685 victims.

The Pokemon feels sorry for harming children

So, on December 16, 1997, all the children of Japan were eagerly sitting in front of the TV screen and waiting for the anime to begin. That episode was viewed in over 26.9 million homes that day. According to the plot, Pikachu uses “Lightning Strike” and an explosion occurs. It was accompanied by a change of two contrasting colors – red and blue at a frequency of 12 hertz. As a result, 685 people (mostly children) across Japan were taken by ambulance with various symptoms: headache, dizziness, seizures, nausea. Later, about 12,000 more children complained about similar symptoms (most of which were refuted and associated with mass hysteria).

It was found that the cause of the seizures was the so-called photosensitive epilepsy, which was triggered by bright color flashes.

As a result:

And since then, several new rules for creating custom content have appeared.

For example:

Contrast and blinking frequency are still checked at one of the Accessibility Testing stages.

Why does a business need accessibility?

2022 will see a jump of the companies investing in accessibility testing to improve their customer experience. Information technologies have become an integral part of our life, and making them available to as many people as possible is a must.

Accessibility Testing is defined as a type of Software Testing performed to ensure that the site, application, or operating system being tested is usable by people with disabilities like hearing, color blindness, old age, and other disadvantaged groups. It is a subset of Usability Testing[1]. 

At the moment, more than one billion people (15% of the total population) are people with disabilities or special needs. 

About 8% of men and 0.4% of women suffer from various types of color blindness – not so little! Of course, this is not a disability, but unusual color perception can significantly interfere with the perception of information and create a number of difficulties, for example, when driving a car or making online purchases. As a result, many solutions from online stores to games are losing users because of ignoring the improvement and testing their accessibility.

Analytical studies show that available sites combined with good design have a larger audience and better results in search engine rankings. They work well with SEO because they are usually fast and easy to use. And this is already a business component. 

Another reason is that companies with inclusive sites are increasing their profits.  For example, the world-famous retailer Tesco has made its website accessible in 2019. And it helped to increase profits by 13 million pounds. As it turned out, everyone loved easy navigation and easy access, not just users with special needs.

To which users of your product it may concern?

How can we understand what requirements must be met?

There is no need to reinvent a wheel. Сontent accessibility legislation with a certain level of standards[2] (WCAG) has been officially adopted in 25 countries. 

WCAG at a glance

WCAG at a glance

The WCAG standard is divided into four key sections:

How to make your resource Accessible?

To make sure that your site is comfortable, simple, and accessible for all users, you need to go through this checklist: 

People with disabilities will be able to receive non-textual information using alternative means, such as Braille or speech.

Presenting information through sign language will greatly facilitate the understanding of the content for people with hearing impairments.

Content should not lose its meaning when presented in different forms. It should be remembered that sometimes the meaning of the information can change with the change in the sequence of the arrangement of the content. Therefore, it is important to set the required order of information blocks in advance.

For example, text-to-speech software interprets an HTML page as a sequence of text, rather than a collection of blocks of information. Therefore, the order of such blocks should be strictly observed in the source code of the page.

It is necessary to facilitate the perception of content as much as possible by separating the main and secondary parts.

For example, you can make the content easier to view by increasing the text size to 200%.

And if there are banners with voice acting on the page, it is worth giving the user the opportunity to mute the sound on the current page.

In this case, it is important that all basic actions on the page can be performed using the keyboard. Especially when it comes to fairly popular one-page sites today.

For example, the user has the ability to re-authorize and at the same time completely save all the entered data.

Do not use items that flash constantly or flash more than 3 times per 1 second.. This can adversely affect the health of users.

Navigation should help the user navigate the application. For example, having several ways to find the desired page will simplify and speed up your work.

For example, this can include decoding abbreviations or using a tool that allows you to listen to the pronunciation of words when it is decisive in understanding the meaning.

It will be easier for the user to navigate if the order of the navigation elements on the page group is the same.

It will be easier for people with disabilities to enter information if they receive prompts in a timely manner in case of incorrect spelling of words.

The content must be fully compatible with modern applications, including assistive technologies. 

Examples of such software are:

[6]

How to conduct accessibility testing?

To conduct this type of testing, first of all, it is needed to select points from the WCAG, which must be adhered while developing the application. The first step is testing for compliance with automatic tools and browser extensions such as Lighthouse[7], Wave[8], aXe[9], NoCoffee[10], ChromeLens[11]. Once checked, these tools will generate gross inconsistencies and recommendations for improvement.

But automatic tools can’t catch everything, so it is advisable to support them with auto manual testing.

Another way you need to test for accessibility is to use Screen Readers. These are applications that sound to the user what is happening on the screen. It’s hard enough to understand whether the voice acting will actually be produced correctly and available to users without those tools.

After testing, all found bugs and inconsistencies are sent to the bugfix and the attached recommendations for improvement.

What do we think about this?

Individuals who have disabilities are relying on digital services more than ever before for everyday activities (remote work, education, healthcare, banking, shopping, etc.). The accessibility implementation is a great addition to any site or application. And it is very pleasant to work, realizing that this can significantly facilitate someone’s life from the one side and receive more profit from another.

To stay around accessibility testing you can follow the next experts: Crystal Preston-Watson[12], Marie Drake[13], Aparna Gopalakrishnan[14], and Manoj Kumar[15].

To find out whether your solution corresponds to WCAG and is accessible for users, contact us[16] for help. 

Learn more from QATestLab

Related Posts:

Endnotes:
  1. Usability Testing: https://qatestlab.com/services/manual-testing/ux-usability-testing/
  2. Сontent accessibility legislation with a certain level of standards: https://www.w3.org/WAI/standards-guidelines/wcag/
  3. Speech Recognition Anywhere: https://chrome.google.com/webstore/detail/speech-recognition-anywhe/kdnnmhpmcakdilnofmllgcigkibjonof?
  4. Dalton for Google Chrome: https://chrome.google.com/webstore/detail/colorblind-dalton-for-goo/afcafnelafcgjinkaeohkalmfececool?
  5. Snap and Read Universal: https://chrome.google.com/webstore/detail/snapread-universal/mloajfnmjckfjbeeofcdaecbelnblden?
  6. [Image]: https://qatestlab.com/solutions/by-focus-area/web-application-testing/?utm_source=Blog&utm_medium=Post&utm_campaign=web-application-testing
  7. Lighthouse: https://chrome.google.com/webstore/detail/lighthouse/blipmdconlkpinefehnmjammfjpmpbjk?hl=ru
  8. Wave: https://chrome.google.com/webstore/detail/wave-evaluation-tool/jbbplnpkjmmeebjpijfedlgcdilocofh
  9. aXe: https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd
  10. NoCoffee: https://chrome.google.com/webstore/detail/nocoffee/jjeeggmbnhckmgdhmgdckeigabjfbddl
  11. ChromeLens: https://chrome.google.com/webstore/detail/chromelens/idikgljglpfilbhaboonnpnnincjhjkd
  12. Crystal Preston-Watson: https://twitter.com/ScopicEngineer
  13. Marie Drake: https://twitter.com/mcruzdrake
  14. Aparna Gopalakrishnan: https://twitter.com/aparna2019
  15. Manoj Kumar: https://twitter.com/manoj9788
  16. contact us: https://qatestlab.com/company/contact-us/
  17. What you should know about testing your E-learning platform: https://blog.qatestlab.com/2021/05/05/e-learning-software-testing/
  18. Why not to Rely on Tools during Accessibility Testing: https://blog.qatestlab.com/2016/04/05/accessibility-testing-tools/
  19. GUI Testing vs Usability Testing: https://blog.qatestlab.com/2015/10/21/gui-usability-testing/

Source URL: https://blog.qatestlab.com/2021/08/18/accessibility-testing/