This presentation was used for the Quality Software Australia - QSA conference in Melbourne for the talk titled "Automated Accessibility testing"

1. MANOJ KUMAR KUMAR
ACCESSIBILITY TESTING

2. ABOUT ME
▸ Open source enthusiast
▸ Selenium member
▸ Author assertselenium.com
▸ Organizer seleniumconf.com
▸ Tweets: @manoj9788 | LinkedIn: manojkumar9788
▸ Accessibility enthusiast

3. WHAT’S IN STORE?
▸ What and Why of Accessibility testing
▸ Overview accessibility standards
▸ Usability and Accessibility
▸ How and When’s of Testing for Accessibility
▸ AxTaaS (Accessibility Testing As A Service)
▸ a11y in Action
3

4. ‣ About 15% of the world's population lives with some form of disability
‣ About 18-20% of Australians have disability (4.3 million) Almost one in
five
‣ The majority (78.5%) are with physical problems.
‣ The other 21.5% reported mental and behavioural disorders.
SOME STATS
abs.gov.au 2015

5. ACCESSIBILITY
WHAT?
TESTING APPLICATION WHETHER IT IS USABLE BY PEOPLE WITH DISABILITIES
▸ Accessibility is about enabling people
▸ Disability only exists if we don’t provide ways to include people
▸ People have impairments NOT disabilities

6. EXAMPLES

7. BAD

8. BAD

9. BAD

10. GOOD

11. ACCESSIBILITY
IF YOUR APP ISN’T ACCESSIBLE, YOU ARE CREATING BARRIERS &
MAKING THEIR IMPAIRMENT A DISABILITY.

12. ACCESSIBILITY
DISABILITY
≠
PHYSICAL
CONDITION
DISABILITY
=
LIMITED
HUMAN
INTERACTION

13. WHY?
▸ Build things that are accessible to everyone
ACCESSIBILITY
LireoDesign.com

14. WHY?
Better Business: builds apps that are user-friendly and cater to those
20% population
ACCESSIBILITY
summerenglish.berkeley.edu/

15. WHY?
Accessible website yield a good SEO(Search Engine Optimization)
▸ No text in images
▸ Use <H> heading tags
▸ Meaningful contextual links
ACCESSIBILITY
information-technology-directory.co.uk

16. WHY?
Abide by Legal legislation
The Australian Government has also mandated via the Disability Discrimination Act 1992
that all Australian Government websites meet the WCAG accessibility requirements
[Wiki]
ACCESSIBILITY

17. OVERVIEW - ACCESSIBILITY STANDARDS
WCAG 2.0 & GSA SECTION 508
▸ Web Content Accessibility Guidelines
▸ WCAG 1.0: May 1999. Superseded by WCAG 2.0
▸ WCAG 2.0: Dec 2008 - testable, technology agnostic.
▸ General Services Administration Section 508 Standards
▸ United States Federal Act. Published in Dec 2000.

18. WCAG 2.0

19. DESIGN PRINCIPLES OF WEB ACCESSIBILITY
P.O.U.R
▸ Perceivable
▸ Operable
▸ Understandable
▸ Robust

20. LEVELS - A, AA & AAA
▸ Level A - basic web accessibility features
▸ Level AA - deals with the biggest and most common barriers for
disabled users
▸ Level AAA – the highest level of web accessibility
SUCCESS CRITERIA
Refer: https://www.w3.org/WAI/WCAG20/quickref/

21. Web Accessibility Means That People With Disabilities
Can Perceive, Understand, Navigate, And Interact the
web with ease
IN A NUTSHELL

22. ▸ Blind
▸ Low-vision
▸ Colorblind
▸ Deaf
▸ Cognitive/Learning
ABILITIES IN DECLINE
Pic: Usability Matters
Permanent || Situational || Temporary

23. NOW… NOT ONLY THOSE 20%
POPULATION EVEN US… WITH
SITUATIONAL IMPAIRMENT

24. ▸ In reality, web accessibility is a subset of UX focused on making your
websites usable by the widest range of people possible, including those
who have disabilities.
▸ ‘Access’ibility - The Right to use
▸ ‘Use’ability - The ease of use
USABILITY - ACCESSIBILITY

25. QUICK RECAP
▸ What and Why of Accessibility testing
▸ Overview accessibility standards
▸ Usability and Accessibility
▸ How and When’s of Testing for Accessibility
▸ AxTaaS (Accessibility Testing As A Service)
▸ a11y in Action
25

26. TESTING
Manual || Automated

27. There is no substitute for real user feedback.
You need to include people with disabilities to Test.
MANUAL - ACCESSIBILITY TESTING

28. WHAT YOU CAN DO?
‣ Tab through a page with keyboard
DEMO: https://www.nsw.gov.au/
MANUAL - ACCESSIBILITY TESTING

29. ‣ Use screen reader for testing
JAWS, NVDA
VoiceOver
OS X
ChromeVox Speak Screen Talk BackFang’s
WHAT YOU CAN DO?
MANUAL - ACCESSIBILITY TESTING

30. WHAT YOU CAN DO?
▸ Headings and Semantics
▸ Firefox web developer plugin
Screen readers use Heading structures to get an overall understanding of
the page.
PARTLY AUTOMATED - ACCESSIBILITY TESTING

31. Good for checking Headings and Semantic errors

32. Document Outline - assertselenium.com

33. Google - Accessibility Plugin

34. WHAT YOU CAN DO?
▸ Browser Plugins
▸ Chrome Accessibility Inspection
▸ Computed Text
▸ Aria labels
▸ Roles
▸ Form criteria
PARTLY AUTOMATED - ACCESSIBILITY TESTING

35. HOW FAR IS IT HELPFUL ?
Tests can roughly catch 20-30% of a11y issues,
depending on the audit rules.
AUTOMATED ACCESSIBILITY TESTING
*Something is better than Nothing*

36. Tools??

37. ▸ By Addy Osmani
▸ JavaScript module for a11y testing
▸ https://addyosmani.com/a11y/
a11y

38. AXE - ACCESSIBILITY ENGINE
▸ Open source from Deque systems
▸ JavaScript module for a11y testing
▸ Axe-WebDriverJs
AXE -CORE

39. Selenium-WebDriver + aXe
AXE - WEBDRIVERJS

40. ▸ Cucumber-selenium
▸ Capybara
▸ Watir
AXE -MATCHERS

41. AXE -JAVA

42. ▸ Protractor Accessibility Plugin for Angular pages
▸ aXe engine
▸ Accessibility Developer tools
▸ tenon.io
NG-ACCESSIBLITY

43. ‣ Pa11y dashboard => pronounce as ‘pally’
‣ Helps you run Accessibility testing as a service
GNU GPL License
Allowed to share, modify the software.
AUTOMATED ACCESSIBILITY AS A SERVICE

44. Using Pa11y dashboard and Mongodb on a Docker
container
AUTOMATED ACCESSIBILITY TESTING AS A SERVICE

45. PA11Y DASHBOARD
AUTOMATED ACCESSIBILITY TESTING AS A SERVICE

46. ACCESSIBILITY TESTING FOR ANDROID
Espresso is an Android testing library

47. ACCESSIBILITY TESTING FOR ANDROID

48. ‣ Common Issues:
‣ Poor contrast
‣ Unlabeled content
‣ Small touch targets
‣ Incorrect View attributes
ACCESSIBILITY TESTING FOR ANDROID

49. ▸ GOOD
▸ Scans a lot of code
▸ Good starting point of manual review
▸ BAD
▸ False positives
The Good and Bad

50. http://www.washington.edu/accesscomputing/AU/issues.html
LIST OF ACCESSIBILITY ISSUES

51. ▸ https://webaccessibility.withgoogle.com/course
▸ https://addyosmani.com/a11y/
▸ https://www.w3.org/WAI/intro/wcag
▸ https://marcysutton.com/
REFERENCES

52. LET’S TEST AND HELP BUILD A WEB
THAT’S ACCESSIBLE FOR EVERYONE
THANK YOU!
Manoj Kumar
@manoj9788