- From: Christophe Strobbe <strobbe@hdm-stuttgart.de>
- Date: Fri, 11 Oct 2013 19:35:56 +0200
- To: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Hi, Am Fr, 11.10.2013, 14:21 schrieb Homme, James: > In case I'm reading the guidelines incorrectly, I wanted to ask this > question. I was reminded of it because in Chrome, you can press a button > that brings up an apps page that contains menu items. With a screen reader > you can arrow to them. As far as I can tell, the keyboard access does not depend on a screen reader; I can also arrow to them without a screen reader. (Sidenote: Visually, the apps list appears as set of big icons, not as a menu.) > If you are using NVDA, you can turn on Focus mode > and use right and left arrows to go to the menu items. Here's the > question. If someone has a motor disability, is the developer required to > make it so that people with disabilities must be able to use the TAB key, > arrow keys, both TAB and arrows, or one or the other to navigate among > items they can interact with? Keyboard access to the items on the apps page is covered by checkpoint 1.1 in the User Agent Accessibility Guidelines (UAAG) 1.0 <http://www.w3.org/TR/UAAG10/uaag10.html#tech-device-independent-ui> and by guideline 2.1 in the current draft of UAAG 2.0: <http://www.w3.org/TR/UAAG20/#gl-keyboard-access>. These guidelines require that keyboard access is supported but they don't dictate which keys should be used. For comparison: many browsers support the TAB key to navigate through links and form elements, but Opera uses the key 'A' to cycle through links. As far as I know, both methods are valid ways to provide keyboard access to links. Does this help? Best regards, Christophe Strobbe -- Christophe Strobbe Akademischer Mitarbeiter Adaptive User Interfaces Research Group Hochschule der Medien Nobelstraße 10 70569 Stuttgart Tel. +49 711 8923 2749
Received on Friday, 11 October 2013 17:36:24 UTC