"This world is such a beautiful place to live in." If you can read the first sentence without any screen readers or assistance, you're privileged. As technologists, shouldn’t we be more empathetic towards differently-abled people and make all parts of our website accessible to them? In my humble opinion, the true power of technology can be identified when it reaches out to people of all kinds having different physical or psychological challenges. We not only legally bound to provide Accessibility but also it should be considered as our moral responsibility.

As testers, we have a wonderful opportunity to contribute to Accessibility by ensuring that the site is accessible in many different ways. Although it is impossible to identify all the issues that exist around Accessibility in the world, we are lucky enough to still understand a majority of them. With this understanding, there have been many measures taken in order to make your site accessible. But, don’t forget - we are QA engineers. We got to ensure that the site is accessible as per the standards set by WCAG 2.0 (AA) by testing for accessibility using various tools and techniques.

 
 

Outline/Structure of the Talk

  1. Accessibility in general and how things are made accessible to differently-abled people in the real world
  2. What is Accessibility in the web world and its importance?
  3. Introduction to Accessibility testing
  4. Tools (Open source) and techniques in Accessibility testing
  5. QA checklist for each technique
  6. Demonstration using Keyboard, screen-reader, Colour Contrast Analyzer, and PDF Accessibility

Learning Outcome

As we progress ahead with the session, you will learn about -

  1. Importance of Accessibility
    1. What do you mean by Accessibility in general?
    2. Types of impairments
    3. How are things made accessible in the real world?
  2. Introduction to Accessibility and testing in the web world
  3. Tools and Techniques for Accessibility testing
    1. Bluetooth keyboards
    1. Keyboard testing
    2. Screen reader
    3. Automated evaluation tools which catch around 80% of the issues in the code
    4. Color Contrast Analyzer
    5. Screen magnifier
  4. Mobile Accessibility testing
  5. PDF Accessibility testing
  6. QA checklist for the above techniques

Target Audience

QA/Test Engineers, Frontend developers, Project Managers, Technical Leads

Prerequisites for Attendees

There are no prerequisites for this session.

schedule Submitted 1 week ago

Public Feedback

comment Suggest improvements to the Speaker