- From: Jim Allan <jimallan@tsbvi.edu>
- Date: Thu, 8 Mar 2012 14:20:54 -0600
- To: WAI-ua <w3c-wai-ua@w3.org>
from http://www.w3.org/2012/03/08-ua-minutes.html
User Agent Accessibility Guidelines Working Group Teleconference
08 Mar 2012
See also: IRC log http://www.w3.org/2012/03/08-ua-irc
Attendees
Present
kim, jim, kelly, jeanne, greg
Regrets
Simon, Mark, Wayne
Chair
JimAllan, KellyFord
Scribe
jallan
Contents
Topics
Action-708
Action-707
Action-700
Summary of Action Items
<trackbot> Date: 08 March 2012
regrets, MarkH, SimonH
<jeanne> http://www.w3.org/WAI/UA/2012/ED-UAAG20-20120306/
<scribe> scribe: jallan
reviewed the new document
all are pleased
js: please close any action items you know should be closed
<jeanne> http://www.w3.org/WAI/UA/2012/ED-UAAG20-20120306/
jeanne: explaining how ATAG work, keep local copy then email completed
version to Jeanne publishing.
Action-708
<jeanne> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012JanMar/0080.html
<scribe> 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.
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@@
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. Users 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, and 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@@
close Action-708
<trackbot> ACTION-708 Merge intents of 213 and 222 and fix the
summaries of 2.1 and 2.3 closed
Action-707
Since 2.1.4 is deleted the summary for GL 2.1 needs to be rewritten
and GL 2.1 will need to be RENUMBERED.
Summary: Users can operate all functions (2.1.1), and move focus
(2.1.2, 2.1.3) using just the keyboard. Users can activate important
or common features with shortcut keys, (2.1.8), escape keyboard traps
(2.1.5), specify that selecting an item in a dropdown list or menues
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 section on 214@@
<scribe> New Summary for GL 2.3 @@newstuff@@
Summary: Users can navigate directly (e.g. keyboard shortcuts) to
important elements (2.3.1) with the option of immediate activation of
the operable elements (2.3.3). Display commands with the elements to
make it easier for users to discover the commands (2.3.2 & 2.3.4). The
user can remap @@and save the user interface and content@@ direct
commands to their needs (2.3.5).
The user can remap and save direct commands to their needs (2.3.5).
The user can remap and save direct commands (2.3.5).
<scribe> New Summary for GL 2.3
Summary: Users can navigate directly (e.g. keyboard shortcuts) to
important elements (2.3.1) with the option of immediate activation of
the operable elements (2.3.3). Display commands with the elements to
make it easier for users to discover the commands (2.3.2 & 2.3.4). The
user can remap and save direct commands (2.3.5).
<scribe> new first paragraph for intent of 235
Intent of Success Criterion 2.3.5
Some users may be able to hit certain keys on the keyboard with
greater ease than others. Assistive technology software typically has
extensive keyboard commands as well. The goal of this SC is to enable
the user to be in control of what happens when a given key is pressed
and use the keyboard commands that meet his or her needs, and the
ability to save the modifications.@@added from 214@@
close Action-708
<trackbot> ACTION-708 Merge intents of 213 and 222 and fix the
summaries of 2.1 and 2.3 closed
http://lists.w3.org/Archives/Public/w3c-wai-ua/2011AprJun/0082.html
https://www.w3.org/WAI/UA/tracker/actions/583
<jeanne> http://www.w3.org/2002/09/wbs/36791/20110706/results
<jeanne> http://www.w3.org/2011/07/07-ua-minutes.html#action02
The author may have provided synchronized alternatives for the media.
Users should be able to easily discover the synchronized alternatives
provided, and have them render synchronously with the default media.
There are times when a user cannot gain meaningful information from a
non-time-based media element (images, charts, graphs, etc.). The
author may have provided alternatives for this....
scribe: The user should be able to easily discover the alternatives
provided, and have them render in place of the default media.
<jeanne> There are times when a user cannot gain meaningful
information from time-based (video, audio) or non-time-based media
elements (images, charts, graphs, etc.). The author may have provided
alternatives for this. The user should be able to easily discover the
alternatives provided, and have them render in place of the default
media.
close Action-583
<trackbot> ACTION-583 Update 1.1.2 with updated text from the survey
http://www.w3.org/2002/09/wbs/36791/20110706/results closed
close Action-573
<trackbot> ACTION-573 Try again with 1.1.2 Indicate Unrendered
Alternative Content - presentation, along with closed
Action-700
http://lists.w3.org/Archives/Public/w3c-wai-ua/2012JanMar/0003.html
<Greg> Existing 2.1.6: 2.1.6 Separate Selection from Activation
(former 2.1.4): The user can specify that selection is separate from
activation (e.g. navigating through a set of radio buttons without
changing which is the active/selected option). (Level A)
<Greg> Existing 3.4.2: 3.4.2 Avoid Side Effects of Navigation [former
1.9.1, before that 3.11.11, changed]: The user can move the keyboard
focus without causing the user agent to take any further action, other
than the presentation of information (e.g. scrolling or pop-ups that
do not change the focus or selection). (Level A)
<Greg> Jan's proposed combination: 2.1.6 Navigation Without Side
Effects: The user can specify that focus and selection can be moved
without causing side effects (further changes in focus, selection or
the state of controls) by either the user agent or author content.
(Level A)
jim, kim +1
gl: lost the caveat that help text and pop ups are ok
... this will fail all UAs. when you tab to a link the url shows on
the status line
<Greg> I think we need to keep the "other than the presentation of
information (e.g. scrolling or pop-ups that do not change the focus or
selection)" so that browsers don't fail for showing you the URL a link
points to, etc.
<Greg> Or something to that effect.
Navigation Without Side Effects: The user can specify that focus and
selection can be moved without causing further changes in focus,
selection or the state of controls, by either the user agent or author
content.
http://lists.w3.org/Archives/Public/w3c-wai-ua/2012JanMar/0003.html
kp: this is ok, radio button not seen as a big issue
js: deleting 342
close Action-700
<trackbot> ACTION-700 Continue to work on the combined 2.1.6
Navigation Without Side Effects to make it clear that some transient
side effects are ok closed
kf: what is the indicator for being DONE with gl SC, etc
kp: henni did a great presentation at csun about mobile will try to
get the reaources
close Action-577
<trackbot> ACTION-577 Update 2.3.5 with text from survey with the
edits from Kim as noted in the minutes below. closed
close Action-633
<trackbot> ACTION-633 change the wording of 1.4.1 to be - The user can
globally set any or all of the following characteristics of visually
rendered text content, overriding any specified by the author or user
agent defaults: closed
close Action-632
<trackbot> ACTION-632 Add (d) line spacing, and (e) character spacing
to 1.4.1 closed
close Action-608
<trackbot> ACTION-608 Look at splitting up 1.6.1-3. closed
close issue-69
<trackbot> ISSUE-69 Guidelines for keyboard and mouse navigation in
complex, nested scrollable areas and content closed
<jeanne> close Action-517
<trackbot> ACTION-517 Rewrite 1.8.5 using simons stuff, gregs
comments, and include whole toolbars as well as components closed
Summary of Action Items
[End of minutes]
--
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 20:21:26 UTC