This document discusses automating accessibility testing for websites. It recommends a three step process: 1) Using Tenon.io for fully automated testing to find definite errors across multiple pages, 2) Using the WAVE toolbar for manual testing plus automation to find definite and possible issues, and 3) Doing individual inspections with tools like NVDA and the Chrome Accessibility Inspector. The document also discusses integrating Tenon.io with WordPress using the Access Monitor plugin and the limitations of only being able to test the DOM output, not the source code.
2. Twitter: @joedolson
Hashtag: #wcmpls
Find these slides
These slides are posted at Slideshare:
http://www.slideshare.net/joedolson/automating
-accessibility-wordcamp-minneapolis-2015
3. Twitter: @joedolson
Hashtag: #wcmpls
3 Rules of Automated Testing:
- Some issues can’t be tested automatically.
- Testing tools must test the DOM
- Test early, test often.
4. Twitter: @joedolson
Hashtag: #wcmpls
Automatically test all the things.
...But you won’t find everything.
Easily Testable:
1) <form>
Your Name:
<input type=’text’ name=’name’
id=’name’ value=’’ />
</form>
2) <img src=’src.jpg’ />
Not so testable:
1) Click on the red button:
<button>One</button> <button>Two</button>
2) <img src=’giraffe.jpg’ alt=’Lion’ />
6. Twitter: @joedolson
Hashtag: #wcmpls
Ya gotta test the DOM
- JavaScript changes the DOM
- These changes can fix or break accessibility
http://mothereffingtoolconfuser.com/
10. Twitter: @joedolson
Hashtag: #wcmpls
1)Fully Automated Testing
- Needs to only return definite errors.
- Needs to test multiple pages at a time.
- Needs to tell you where you have issues,
and how to fix them.
Recommendation: Tenon.io
11. Twitter: @joedolson
Hashtag: #wcmpls
Tenon.io
- API driven Accessibility testing service
- Operates a headless browser to generate
the DOM before testing
- Integrates with WordPress using Access
Monitor http://wordpress.org/plugins/access-
monitor
13. Twitter: @joedolson
Hashtag: #wcmpls
2) Manual + Automation
- Returns both definite and possible issues*
- Tells you where the issue is and how to
verify whether it’s an error.
* By now, definite issues should be fixed.
Recommendation: WAVE Toolbar
16. Twitter: @joedolson
Hashtag: #wcmpls
Using Tenon with WordPress
Access Monitor
- Set up a schedule to monitor pages
- Run tests on single or batches of pages
- Test admin & front-end
- Filter out redundant results in batches.
18. Twitter: @joedolson
Hashtag: #wcmpls
Limitations when testing software
- What do you need to test? The DOM
- What do you produce with themes and plug-
ins? CODE
- Need to run before you can test.