builds, fixes, and triages technology companies and products

Accessibility and Section 508 Compliance for Developers

Posted By on October 13, 2011 in Blog | 0 comments

Here is a brute force approach to getting closer to 508 compliance, if you only have dev resources and don’t have strong UX resources to sort this out for you. Use the following online testing tools:

  1. Hera http://www.sidar.org/hera/
  2. fae http://fae.cita.uiuc.edu/
  3. AChecker http://achecker.ca/checker/
  4. Cynthia http://www.cynthiasays.com/mynewtester/cynthia.exe

Hera and fae give good actionable feedback (IMO), and I like how they present the information for developers. The tools are listed in the order of priority that they should be run against the key public areas of your site. Private areas require more hoops to jump through. The process to identify and resolve accessibility bugs is this:

  1. Go to the first analysis tool
  2. Run the analysis tool on the key public(|private) areas of your site: homepage, profile pages, product pages, and video content pages
  3. Fix major accessibility bugs. Document what you don’t fix
  4. Rereun tool until major bugs are validated as fixed
  5. Load the next analysis tool and go to step 2.

Leave a Reply

Your email address will not be published. Required fields are marked *