At the end of the call last week Peter was asking about the keyboard requirements of UAAG 1.0. Here are some of the main requirements: UAAG Keyboard Requirements Checkpoint 1.1 Full Keyboard Access http://www.w3.org/TR/UAAG/guidelines.html#tech-device-independent-ui\ Checkpoint 1.2 Keyboard access to scripting event handlers http://www.w3.org/TR/UAAG/guidelines.html#tech-device-independent-handlers Most of the checkpoints in Guideline 9 Guideline 9. Provide navigation mechanisms http://www.w3.org/TR/UAAG/guidelines.html#gl-navigation NOTE: What we do not require is that there be a cursor that moves character by character through a web resource. Although to implement a sub-selection of rendered conent feature through the keyboard, this would probably be the way to implement it. Note we do not require that a browser implement a sub-selection of content feature, but most graphical browsers do implemnt this. Jon Jon Gunderson, Ph.D., ATP Coordinator of Assistive Communication and Information Technology Division of Rehabilitation - Education Services MC-574 College of Applied Life Studies University of Illinois at Urbana/Champaign 1207 S. Oak Street, Champaign, IL 61820 Voice: (217) 244-5870 Fax: (217) 333-0248 E-mail: jongund@uiuc.edu WWW: http://cita.rehab.uiuc.edu/ WWW: http://www.staff.uiuc.edu/~jongundReceived on Monday, 16 August 2004 16:14:55 GMT
This archive was generated by hypermail 2.2.0 + w3c-0.29 : Thursday, 13 January 2005 12:11:11 GMT