Monday, 22 October 2018

Testing For Digital Accessibility

'Learned the difference between usability and accessibility testing' is what the co-learners shared with us as one of the feedback for the accessibility testing workshop conducted on 23rd September.
This workshop was hosted by Manumantraa and presented by Ajay Balamurugadas and myself. 

In my humble knowing, this confusion between usability and accessibility can occur if/when the focus is not on testing but on imposing testers to learn about the process and not about testing at an/y organization. The ecosystem makes you believe as a new tester, that knowing about testing fundamentals is not necessary but knowing the process is quiet essential. The training program is designed in this way too. As Sanath puts it 'lie' is at the center of the word 'believe'.

Any belief about software testing needs to be formed by a tester and by deep diving to know and learn and mustn't be a blindly followed borrowed belief system. When we learn from the unlearned it impacts us and the next generations of testers know-how as this, in turn, gets passed down as software testing knowledge.
So do *participate, discuss, talk and be involved in the learning that is happening around you, in your team, at your organization. *Participate - Take part assertively and effectively to contribute for the greater good.

Testers who are on a learning path of a11y testing can find some of the below collated a11y testing tools useful and for reference only.































For the ease of developing a11y tools for testing and for a deeper understanding a11y testing is broadly categorized into Visual, Cognitive, Speech, Mobility and Hearing impairment. 

Some of the a11y testing tools developed to aid testing for the above categories are collated in a visual representation below:


















One of the key takeaway for all the co-learners was/is:
Accessibility, testing for accessibility is not for a category of people who are specially-abled but it is for all the users.
Real users feedback is of prime importance to build accessibile solutions.
It is essential to code for a11y using some of the a11y developer tools mentioned above into the software solution early on instead of thinking of it as a necessity to save the business from a lawsuit.
There is no alternate solution but having accessibility built into the software is the solution.

Please feel free to suggest, correct, review the above work.

No comments: