WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Testing for accessibility compliance


From: Hoffman, Allen
Date: Apr 27, 2010 1:21PM

I recommend:

1. Consider using automated tools for the easy stuff--flag images
without alternate text, flag form fields without alternate text, flag
tables which need scope and/or ID tagging, flag pages without skip-nave
standard doing, flag content which requires accessible plug-ins, flag
server-side image maps for removal or redundant text inclusion, flag
usemaps for alternate text, etc. Then consider using the web
accessibility toolbar for manual testing of pages for color usage,
dependency upon .css, flicker usage, etc. No tools really test for
keyboard access or time outs well to my knowledge, so manual testing is

2. Develop 508 test procedures, teach them, and use them.

3. Consider using Object Inspector or other "object" inspection tools
for more interactive aspects of software testing to ensure that
interface elements have name, role, and state provided.

4. Develop coding standards, teach them, use them. This will drive the
"right" way to code home to your developers. Use templates which
include the right way to code things and leave them alone accept when
you must change correct coding.

I hope this helps.

-----Original Message-----
From: Mark Guisinger [mailto: <EMAIL REMOVED> ]
Sent: Tuesday, April 27, 2010 1:50 PM
Subject: [WebAIM] Testing for accessibility compliance

I'm working for a large company that is beginning to go down the road to
making there website accessible. I'm starting to wonder about testing,
as I'm not a tester. Do larger companies testing their websites for
accessibility have a group of testers reviewing their pages with screen
readers (one or more)? Or do they just validate that the code created
is to spec? What tools are other companies using to test their websites
for accessibility? Any guidance will be greatly appreciated.