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

try at test for ATAG2.0 A.3.1.2 - more work on it needed

From: Boland Jr, Frederick E. <frederick.boland@nist.gov>
Date: Thu, 20 Sep 2012 14:09:33 -0400
To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <D7A0423E5E193F40BE6E94126930C4930BA86CDC3D@MBCLUSTER.xchange.nist.gov>
A Definition/test of keyboard focus used in following steps (from http://www.ehealth.va.gov/508/terms/term_keybfocus.html

"keyboard focus refers to the ability to access and appropriately interact with elements on the screen from the keyboard."

To test whether keyboard focus is on a certain control/"input area", attempt to perform an appropriate action via the keyboard interface and check to determine whether that action has a corresponding appropriate result explicitly associated with that control/"input area".



Another definition of keyboard focus:

http://www.termwiki.com/EN:keyboard_focus



I'm sure there are others out there.. will try to do more work on this but have very limited time currently..



Thanks and best wishes

Tim Boland NIST



----------------------------------begin test procedure--------------------------



Step 0. Document specific platform via which authoring tool will be accessed.  If a keyboard interface does not exist for this platform, this SC is N/A for this authoring tool; go to Step 7.  Otherwise, go to Step 1.



Step 1. Document if keyboard focus is supported by authoring tool as a part of the keyboard interface.  If keyboard focus is not supported, this SC is N/A for this authoring tool; go to Step 7.  Otherwise, go to Step 2.



Step 2. Document all controls for a specific function supported by authoring tool.  For each of these controls, document if there are explicit instructions given to you on how to move keyboard focus to and from that control. If there are no such controls, this SC is N/A for this authoring tool; go to Step 7.  Otherwise, go to Step 3.



Step 3. (loop) For every function control (from Step 2) in the authoring tool, test the ability to move keyboard focus (from Step 1) to this function control by using the keyboard interface from Step 0.  If keyboard focus can be moved to this function control as specified in the previous sentence (by following any instructions documented in Step 2 for this control), then place the control in Group A. Otherwise place the function control in Group B. If upon exiting the loop, there are no function controls in Group A (Group A is empty), then SC is N/A for this authoring tool on this platform; go to Step 7.  Otherwise go to Step 2.



Step 4. (loop) For every function control in Group A, attempt to move keyboard focus from this function control by only using the keyboard interface from Step 0 (and by following any instructions documented for Step 2 for this control).  If for any control, focus cannot be moved away from the control in the fashion from the previous sentence (focus is trapped), then stop; SC fails for this authoring tool on this platform; go to Step 7.  If the previous condition does not apply for any function control in the loop for Group A (focus is not trapped), document the specific keystrokes/exit methods required for said movement for each function control in Group A.  Go to Step 5.



Step 5. Document a list of "standard" or "common" exit methods for this authoring tool (or authoring tools in general).



Step 6. (loop) For every function control in Group A, check to ensure that any exit methods documented for that function control from Step 2 are covered in the list from Step 5.  For any exit methods "outside" this list, check to determine if you are notified of the exit method needed prior to attempting to move keyboard focus from that function control, and if notified exit method works in moving keyboard focus from that control.  If the preceding sentences in Step 6 are all true for all function controls in Group A, then this SC passes for this authoring tool on this platform.  Otherwise, this SC fails for this authoring tool on this platform.  Go to Step 7.

Step 7. End test.

----------------------------------------------------------end test procedure----------------------------------------------------------------------------
Received on Thursday, 20 September 2012 18:09:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 20 September 2012 18:09:58 GMT