W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2012

ACTION-708 - Merge intents of 213 and 222 and fix the summaries of 2.1 and 2.3

From: Jim Allan <jimallan@tsbvi.edu>
Date: Thu, 8 Mar 2012 12:11:08 -0600
Message-ID: <CA+=z1WmNXTSBG8KyAeUQTa0roKE6NF4hzW1PM5g=kH-SEUvmrA@mail.gmail.com>
To: WAI-ua <w3c-wai-ua@w3.org>
merge of 213 and 222
no change for Summary of GL 22

New Summary of gl 2.1
Summary: Users can operate all functions (2.1.1), and move focus
(2.1.2) using just the keyboard. Users can activate important or
common features with shortcut keys, (2.1.8), override keyboard
shortcuts in content and user interface (2.1.4), escape keyboard traps
(2.1.5), specify that selecting an item in a dropdown list or menuoes
not activate that item or move to that new web page (2.1.6) and use
standard keys for that platform (2.1.7).@@removed 2.1.3...just the
numerals no words removed.

merge of 213 and 222

2.2.2 Sequential Navigation Between Viewports [new]:
The user can move the keyboard focus backwards and forwards between
viewports, without having to sequentially navigate all the elements in
a viewport. (Level A)

	Intent of Success Criterion 2.2.2:
It is important for the user to be able to jump directly to the next
or previous viewports without having to visit every element in a
viewport on the way to the next viewport, because that can add an
exorbitant number of navigation commands to operations that should be
both easy and efficient. User need keyboard access to all viewports
and all enabled elements so that they can manipulate them, view them
with screen magnifiers, or have them described by screen readers. The
ability to move both forward and backward through the navigation order
greatly reduces the number of keystrokes and allows the user to more
easily recover from mistakes in overshooting a destination. @@This
navigation can be between viewports within the application, or between
windows or applications. This includes the user agent's user
interface, extensions to the user interface (e.g. add-on), content,
and plug-ins handling content. @@added from 213@@

	Examples of Success Criterion 2.2.2:
o	Sooj cannot use a pointing device, so she moves the keyboard focus
to the next pane by pressing F6 or the previous pane by pressing
Shift+F6. She moves between tabbed document views by pressing Ctrl+Tab
and Shift+Ctrl+Tab.
o	Ruth is working in her web browser, where one document window
(viewport) is active (has the active keyboard focus). When she
switches to her word processor, the web browser's window and its
keyboard focus become inactive, and it hides its cursor. When she
switches back to the browser window, it reactivates that viewport, its
keyboard focus becomes active again, and its cursor reappears in the
same location as when she switched to a different application.
@@added from 213@@
o	A developer creates an extension to a user agent that allows the
user to add notes about each web page being visited. A user can press
a shortcut key to move focus to the user interface of this extension
and interact with the functionality offered by the extension.
Similarly, the user presses another key to move focus back to the main
viewport for the user agent in the same location as when she moved to
the plugin.  @@added from 213@@

	Related Resources for Success Criterion 2.2.2:
o	2.2.1 ensures that the user can navigate to elements within the
viewport. @@added from 213@@
o	See the description of 2.2.1 for background information on the
importance of sequential navigation.

Jim Allan, Accessibility Coordinator & Webmaster
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Thursday, 8 March 2012 18:11:36 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:41 UTC