W3C home > Mailing lists > Public > w3c-wai-au@w3.org > October to December 2012

first try at ATAG2.0 A.3.1.4 test - more work needed

From: Boland Jr, Frederick E. <frederick.boland@nist.gov>
Date: Tue, 6 Nov 2012 10:41:46 -0500
To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <D7A0423E5E193F40BE6E94126930C4930BAB120B1B@MBCLUSTER.xchange.nist.gov>
1.       Document whether the platform on which the authoring tool runs supports a keyboard interface - if not then SKIP (N/A) - if so then proceed

2.       Document all functions supported by the authoring tool (from authoring tool documentation or author experience)

3.       For each function documented from Step 2 (loop), check that the function works "correctly" (from authoring tool documentation/expected behavior - may involve interaction with content - document rationale for "correctness" determination for each such function) via the keyboard interface from Step 1.  Document any timing issues for keystrokes required to achieve "correctness".   If one or more such functions do not work "correctly", then FAIL.  Otherwise proceed.

4.       Check whether any functions "completed correctly" from Step 3 require specific timings for any individual keystrokes in order to complete correctly (from timing issues documented in Step 3).  If any do, then FAIL.  Otherwise PASS.



ISSUE: Re: timing issues in Step 3, what is a reasonable amount of time to wait for any keystroke to complete correctly in the testing process?   IF the tester waits too short a time, then a keystroke may not have a "reasonable" chance to complete under any circumstance, so may be unfairly penalized.  If the tester waits too long  for a keystroke to complete, then that may be an issue as well (upper limit for keystroke timing - how do you know when you've reached it?  Also, what about a function that requires an excessive number of keystrokes to complete it?



Thanks and best wishes

Tim Boland NIST
Received on Tuesday, 6 November 2012 15:42:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 6 November 2012 15:42:15 GMT