Where It's AT – Assistive Technology Blog

Contributed by Stephen Polacek, IT Accessibility Evaluator

10-29 Blog Post – Testing Resources

For those interested in testing, or just want to learn more about accessibility in general, there are plenty of resources available.  It’s probably a good idea to compile a suite of tools you wish to use during your testing process so that you have everything at the ready.  To get you started, here’s a sample of my process for testing, based off of WCAG.  I typically start with manual testing, unlike the recommendations of Deque and the like, because of my position. 

1. Establish the logical structure of the site
   1. Determine what headings exist, what level of heading they are, and any inconsistencies between levels (example: no <h2> on a page with <h1> and <h3> tags; multiple <h1> tags; etc.)
   2. Look for landmark markup (I use NVDA but any screen reader will have an option to pull up the list of landmarks)
   3. Go through the TAB order manually and follow the cursor to determine any inconsistent jumps (example: going from column to column left-to-right instead of reading a whole column first)
2. Check for text alternatives for non-text content
   1. While this can be done by an automated test, I prefer handling it manually so I can determine if the alt text is descriptive enough, especially for images used as links
   2. Because a lot of content from other sites, such as social media, is not totally under the website’s control, having a description or another element with the same information becomes important
   3. Videos and Audio should have captions or a transcript – typically I only look at a single element if multiple are available on the site, as this becomes a serious time commitment
3. Best Practices
   1. Using native HTML elements, especially HTML5 – I will often recommend switching elements that are created via scripting to be switched to HTML5, as this makes accessibility more intrinsic and makes future content easier to make accessible
   2. Skip to Main Content Links – fairly common, but typically are hidden and only viewable to screen readers, Skip to Main Content links actually benefit other users as well, such as those using voice commands or those with physical disabilities; I will recommend making these visible for all users
   3. Responsive Design – making the website respond to different viewports while keeping all content in the same order; this is becoming very important and the standard design format as so many different devices are now used to access websites
4. Automated Testing
   1. Chrome extension aXe (from Deque) or WAVE (from W3C) – These are good for finding code errors or creating more exhaustive lists of errors; make sure to double check issues in case it points out something that is more subjective
   2. Accessible Color Picker (Chrome extension) – not an actual automated tool but useful for double checking color contrast issues listed by aXe or WAVE
   3. Photosensitive Epilepsy Analysis Tool (from the University of Maryland) – only useful in specific instances, but definitely needed to test any content that flashes more than a couple times per second

As I mentioned, this is not a complete process; my job typically requires a cursory review to establish if a website is in need of remediation or not.  A complete testing process will include all of the WCAG guidelines and which standard is to be met.  However, the tools linked for the automated section are good starting points for seeing what needs to be done and for testing your own website. 

If you’re are using a content management system, such as WordPress, you might be limited in what you can do for accessibility.  Remember, do everything you can to ensure your part is done in the process.  With that, you can reach out to the developer of whatever system you’re using and push them to do what needs to be done on their end to reach compliance.

If you’re looking for more accessibility resources, check out our main IT Access Initiative page: http://mdod.maryland.gov/news/Pages/Web-Accessibility.aspx.  We offer a list of resources on accessibility and a schedule of our upcoming training sessions.