WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: testing for keyboard accessibility


From: Tim Harshbarger
Date: Sep 24, 2012 9:03AM

<span id="SCDDmwsp">Home</span>

Like others have said...there probably isn't a fool-proof way for an automated tool to determine that the above is an interactive widget and exactly what keystrokes need to be used.

However, you might be able to devise automated tests that verify that a drop down menu that was included in the design specs is present and works like the design specs say it should.

So you might be able to automate testing that way. Of course, it does mean that accessibility needs to be considered during design and documented well enough to create tests.

-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Howard Kramer
Sent: Friday, September 21, 2012 2:58 PM
To: WebAIM Discussion List
Subject: [WebAIM] testing for keyboard accessibility

Does anyone have suggestions for testing web keyboard accessibility.
Achecker seems to catch certain types of scripts that restrict access to
mouse actions but it doesn't seem to catch everything. The functional
accessibility evaluator seems to also sometimes catch this. Manual tabbing
through a site and testing if a menu item responds to the enter key seems
more reliable. Any suggestions on this is appreciated.


Howard Kramer
AHG Conference Coordinator
Access Specialist