W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > October to December 2011

Minutes: User Agent Teleconference for 15 December 2011

From: Jim Allan <jimallan@tsbvi.edu>
Date: Thu, 15 Dec 2011 13:49:48 -0600
Message-ID: <CA+=z1WnnDm3fCUrpDqMLPUVWOR5C_1us1JBjnnVR=mafFbkePg@mail.gmail.com>
To: WAI-ua <w3c-wai-ua@w3.org>
from http://www.w3.org/2011/12/15-ua-minutes.html

- DRAFT - User Agent Accessibility Guidelines Working Group Teleconference 15
Dec 2011

See also: IRC log <http://www.w3.org/2011/12/15-ua-irc>
http://www.w3.org/2011/12/15-ua-irc
Attendees
 Present Jim_Allan, KellyFord, Jeanne, Greg_Lowney, Kim_Patch, Jan,
sharper, Wayne Regrets mark Chair jimallan, kellyford Scribe jallan
Contents

   - Topics <http://www.w3.org/2011/12/15-ua-minutes.html#agenda>
      1. Survey http://www.w3.org/2002/09/wbs/36791/20111130/results
      (2.11.10-12, 2.6.3 is really
2.11.11)<http://www.w3.org/2011/12/15-ua-minutes.html#item01>
      2. 2.11.11 Scale and position alternative media tracks: The user can
      scale and position alternative media tracks independent of base video.
      (Level AAA) <http://www.w3.org/2011/12/15-ua-minutes.html#item02>
      3. 2.11.12 Adjust Playback Contrast and
Brightness<http://www.w3.org/2011/12/15-ua-minutes.html#item03>
      4. meeting on Jan 5?<http://www.w3.org/2011/12/15-ua-minutes.html#item04>
      5. LC push - schedule a couple of marathon
day(s)<http://www.w3.org/2011/12/15-ua-minutes.html#item05>
      6. action-679 <http://www.w3.org/2011/12/15-ua-minutes.html#item06>
      7. action-678 Write a combo of 261-263 to one
SC<http://www.w3.org/2011/12/15-ua-minutes.html#item07>
      8. generated content<http://www.w3.org/2011/12/15-ua-minutes.html#item08>
    - Summary of Action
Items<http://www.w3.org/2011/12/15-ua-minutes.html#ActionSummary>

------------------------------

 Summary of Action Items*[NEW]* *ACTION:* jallan to rewrite IER for 2.11.11
[recorded in http://www.w3.org/2011/12/15-ua-minutes.html#action04]
*[NEW]* *ACTION:* jeanne to add 2.6.x The user can call up a list of input
device event handlers explicitly associated with the keyboard focus
element, and activate any one or more of the event handlers.and IER above
from KIm [recorded in http://www.w3.org/2011/12/15-ua-minutes.html#action07]
*[NEW]* *ACTION:* jeanne to add section at top of document "Applicability
Notes" that includes Modality Independence Principal - Users interacting
with a web browser may do so using one or more input methods including
keyboard, mouse, speech, touch, and gesture. Itís critical that each user
be free to use whatever input method or combination of methods works best
for a given situation. Therefore every... [recorded in
http://www.w3.org/2011/12/15-ua-minutes.html#action06]
*[NEW]* *ACTION:* jeanne to change 2.11.11 "alternative visual media
tracks" to "visual alternative media tracks" [recorded in
http://www.w3.org/2011/12/15-ua-minutes.html#action03]
*[NEW]* *ACTION:* jeanne to change 21112 to 2.11.12 Video Contrast and
Brightness: Users can adjust the contrast and brightness of visual
time-based media. (AAA) [the more user-centric phrasing] and remove
applicability note [recorded in
http://www.w3.org/2011/12/15-ua-minutes.html#action05]
*[NEW]* *ACTION:* jeanne to delete 2.11.10 [recorded in
http://www.w3.org/2011/12/15-ua-minutes.html#action01]
*[NEW]* *ACTION:* jeanne to delete 2.6.1, 2, 3 and replace with 2.6.x
[recorded in http://www.w3.org/2011/12/15-ua-minutes.html#action08]
*[NEW]* *ACTION:* jeanne to make sure that wayne is on the list. still not
getting email [recorded in
http://www.w3.org/2011/12/15-ua-minutes.html#action09]
*[NEW]* *ACTION:* JR to Write proposal for a zoom function SC and another
for a zoom that respects horizontal [recorded in
http://www.w3.org/2011/12/15-ua-minutes.html#action02]


<trackbot> Date: 15 December 2011

<jeanne> http://www.w3.org/WAI/UA/2011/ED-UAAG20-20111213/

<scribe> scribe:jallan
Survey http://www.w3.org/2002/09/wbs/36791/20111130/results (2.11.10-12,
2.6.3 is really 2.11.11)

topic 2.11.10

gl: couldn't parse this, asked questions

https://www.w3.org/2002/09/wbs/36791/20111130/results#xq11

scribe: every media playback may not be a viewport

jr: 'handle' assumes that every player with have handles to change size

js: time based media is an element or an object. and you are changing the
size of the element/object

gl: time-based media will apply to animation, and canvas

jr: time based objects could fly around the screen.
... need to have it bigger than its default.

gl: you can make images and text bigger, how are they different from visual
time based media.
... media is a variation of text and images.

<jeanne> http://www.w3.org/WAI/UA/2011/ED-UAAG20-20111213/

gl: also need to state 'visual' time base media

ja: this is special, ability to make only this instance (video) (element)
larger

gl: so we are talking about a discrete region of the page not some global
animation
... what about reflow?

ja: in implementation

kf: this needs lots of work

gl: already say that every viewport can be resized, but not independently
... viewports have min/max limits

kf: does zoom work on video

ja: yes

jr: UA needs to have a zoom, and can zoom all the content

gl: minimum expectation is to make all content large
... change the size of edit fields.

kf: do we have zoom, see lots of resizing.

jr: 1.4.x scale text, need a dumb zoom to zoom everything.

kf: if we delete 21110, what do folks think

jr: +1 if we have an overall zoom

kf: have a generic zoom feature that covers all content

gl: full zoom, is minimal

<jeanne> *ACTION:* jeanne to delete 2.11.10 [recorded in
http://www.w3.org/2011/12/15-ua-minutes.html#action01]

<trackbot> Created ACTION-689 - Delete 2.11.10 [on Jeanne F Spellman - due
2011-12-22].

<Jan> *ACTION:* JR to Write proposal for a zoom function SC and another for
a zoom that respects horizontal [recorded in
http://www.w3.org/2011/12/15-ua-minutes.html#action02]

<trackbot> Created ACTION-690 - Write proposal for a zoom function SC and
another for a zoom that respects horizontal [on Jan Richards - due
2011-12-22].

gl: optimal is to zoom within window boundary, then discrete zoom
2.11.11 Scale and position alternative media tracks: The user can scale and
position alternative media tracks independent of base video. (Level AAA)

ja: discrete movement of captions to be above, below, beside video

gl: prefer changing to visual media track

<greg> "visual alternative media tracks" rather than "alternative visual
media tracks" but not a big deal, just trying to not break up the phrase
"alternative media".

+1 all around

<sharper> +1

<jeanne> *ACTION:* jeanne to change 2.11.11 "alternative visual media
tracks" to "visual alternative media tracks" [recorded in
http://www.w3.org/2011/12/15-ua-minutes.html#action03]

<trackbot> Created ACTION-691 - Change 2.11.11 "alternative visual media
tracks" to "visual alternative media tracks" [on Jeanne F Spellman - due
2011-12-22].

<scribe> *ACTION:* jallan to rewrite IER for 2.11.11 [recorded in
http://www.w3.org/2011/12/15-ua-minutes.html#action04]

<trackbot> Created ACTION-692 - Rewrite IER for 2.11.11 [on Jim Allan - due
2011-12-22].
2.11.12 Adjust Playback Contrast and Brightness

ja: should be AAA

gl: should clarify, the playback media only (video).

jr: how does this interact with system wide brightness and contrast setting.

kf: do we need this?

gl: this is for mediaplayer plugin, you need to expose these controls.

Kf: should this apply to images, should I be able to change contrast of
images

gl: when a technology allows the adjustment of contrast and brightness,
then it needs to expose it in the UA
... should only apply to playback of timebased media

<greg> Since AAA would be OK to essentially just be recommending that
components that play back visual time-based media allow the user to adjust
contrast and brightness.

wayne: is there a demand for this

<greg> "Components that play back visual time-based media allow the user to
adjust contrast and brightness"

+1

<Wayne> +1

<greg> 2.11.12 Playback Contrast and Brightness: Components that play back
visual time-based media allow the user to adjust contrast and brightness.
(AAA)

<greg> 2.11.12 Playback Contrast and Brightness: Components that play
visual time-based media allow the user to adjust contrast and brightness.
(AAA)

<KimPatch> +1

<greg> Shouldn't use "playback" in the title if not in the SC.

<greg> 2.11.12 Video Contrast and Brightness: Components that play visual
time-based media allow the user to adjust contrast and brightness. (AAA)

<greg> 2.11.12 Video Contrast and Brightness: Users can adjust the contrast
and brightness of visual time-based media. (AAA) [the more user-centric
phrasing]

<greg> The existing Applicability Note goes away.

<scribe> *ACTION:* jeanne to change 21112 to 2.11.12 Video Contrast and
Brightness: Users can adjust the contrast and brightness of visual
time-based media. (AAA) [the more user-centric phrasing] and remove
applicability note [recorded in
http://www.w3.org/2011/12/15-ua-minutes.html#action05]

<trackbot> Created ACTION-693 - Change 21112 to 2.11.12 Video Contrast and
Brightness: Users can adjust the contrast and brightness of visual
time-based media. (AAA) [the more user-centric phrasing] and remove
applicability note [on Jeanne F Spellman - due 2011-12-22].

<jeanne> Sorry, I need to go, apologies.
meeting on Jan 5?

kf: meet Dec 22 and 29?
... shouldn't meet on 22 or 29, write/send proposals to list
... Jan 5 ok?

resume standard meeting on Jan 5
LC push - schedule a couple of marathon day(s)

kf: will review marathon days on Jan 5
action-679

Modality Independence Principal

Users interacting with a web browser may do so using one or more input

methods including keyboard, mouse, speech, touch, and gesture.

Itís critical that each user be free to use whatever input

method or combination of methods works best for a given

situation. Therefore every potential user interaction must be

accessible via modality

independent controls that any input technology can

access.

For instance, if a user canít use or doesnít have access to a mouse, but can

use and access a keyboard, the keyboard can call a modality

independent control to activate an OnMouseOver

event.

<KimPatch> Modality Independence Principal

<KimPatch> Users interacting with a web browser may do so using one or more
input methods including keyboard, mouse, speech, touch, and gesture. Itís
critical that each user be free to use whatever input method or combination
of methods works best for a given situation. Therefore every potential user
task must be accessible via modality independent controls that any input
technology can access.

<KimPatch> For instance, if a user canít use or doesnít have access to a
mouse, but can use and access a keyboard, the keyboard can call a modality
independent control to activate an OnMouseOver event.

kp: modality is not in the document, have been using keyboard short cuts

kf: put this in doc at the beginning
... guiding principals

jr: in ATAG we have global Applicability Notes at the top of each section

<greg> I like the first paragraph, but I find the wording of the "For
instance" paragraph to be verbose and confusing. For example, "can call a
modality independent control"? Call it what? :-)

wayne: similar to Accessibility Support in WCAG

<scribe> *ACTION:* jeanne to add section at top of document "Applicability
Notes" that includes Modality Independence Principal - Users interacting
with a web browser may do so using one or more input methods including
keyboard, mouse, speech, touch, and gesture. Itís critical that each user
be free to use whatever input method or combination of methods works best
for a given situation. Therefore every... [recorded in
http://www.w3.org/2011/12/15-ua-minutes.html#action06]

<trackbot> Created ACTION-694 - Add section at top of document
"Applicability Notes" that includes Modality Independence Principal - Users
interacting with a web browser may do so using one or more input methods
including keyboard, mouse, speech, touch, and gesture. Itís critical that
each user be free to use whatever input method or combination of methods
works best for a given situation. Therefore every... [on Jeanne F Spellman
- due 2011-12-22].

UNKNOWN_SPEAKER: potential user task must be accessible via modality
independent controls that any input technology can access.

For instance, if a user canít use or doesnít have access to a mouse, but
can use and access a keyboard, the keyboard can call a modality independent
control to activate an OnMouseOver event.

<greg> I think we can just take one of the already written examples from
the corresponding SC.

<greg> E.g. the Cade or Omar examples from 2.1.1

close action-679

<trackbot> ACTION-679 Write note for top of document about overarching
principle of modality independence closed
action-678 Write a combo of 261-263 to one SC

<KimPatch> 2.6.X Activate any event handlers:

<KimPatch> The user can call up a list of input device event handlers
explicitly associated with the keyboard focus element, and activate any one
or more. (Level A)

<KimPatch> Intent of Success Criterion 2.6.X :

<KimPatch> Users interacting with a web browser may be doing so by using
one or more input technologies including keyboard, mouse, speech, touch,
and gesture. No matter how the user is controlling the user agent, the user
needs to know all the input methods assigned to a particular piece of
content. At the same time, anyone input method should not arbitrarily hold
back another. For instance, people...

<KimPatch> ...who don't use a mouse shouldn't necessarily have to map their
input methods to the same steps a mouse user would take.

<KimPatch> Examples of Success Criterion 2.6.X :

<KimPatch> o Jeremy cannot use a mouse. He needs to activate a flyout menu
that normally appears OnMouseOver. Jeremy can navigate to a link on this
flyout menu and activate it using keyboard shortcuts.

<KimPatch> o Ken is a speech input user. In order to get his work done in a
reasonable amount of time and without overtaxing his voice he uses a single
speech command phrase to move the mouse up, left and click.

<KimPatch> o Karen cannot use a mouse. She clicks a single key to activate
both events for link that has an onmousedown and an onmouseup event link.

<KimPatch> Related Resources for Success Criterion 2.6.X :

<KimPatch> The Modality Independence Principle X.X

<greg> No necessarily necessary, but could reorder sentence to "The user
can call up a list of and activate and one or more input device event
handlers explicitly associated with the keyboard focus element."

<greg> "The user can call up a list of and activate any one or more, input
device event handlers explicitly associated with the keyboard focus
element."

<Wayne> Why not just "can activate any of the handlers"

<KimPatch> The user can call up a list of input device event handlers
explicitly associated with the keyboard focus element, and activate any one
or more of the event handlers.

<greg> the or those

<KimPatch> +1 those

<scribe> *ACTION:* jeanne to add 2.6.x The user can call up a list of input
device event handlers explicitly associated with the keyboard focus
element, and activate any one or more of the event handlers.and IER above
from KIm [recorded in http://www.w3.org/2011/12/15-ua-minutes.html#action07]

<trackbot> Created ACTION-695 - Add 2.6.x The user can call up a list of
input device event handlers explicitly associated with the keyboard focus
element, and activate any one or more of the event handlers.and IER above
from KIm [on Jeanne F Spellman - due 2011-12-22].

<scribe> *ACTION:* jeanne to delete 2.6.1, 2, 3 and replace with 2.6.x
[recorded in http://www.w3.org/2011/12/15-ua-minutes.html#action08]

<trackbot> Created ACTION-696 - Delete 2.6.1, 2, 3 and replace with 2.6.x
[on Jeanne F Spellman - due 2011-12-22].

<scribe> *ACTION:* jeanne to make sure that wayne is on the list. still not
getting email [recorded in
http://www.w3.org/2011/12/15-ua-minutes.html#action09]

<trackbot> Created ACTION-697 - Make sure that wayne is on the list. still
not getting email [on Jeanne F Spellman - due 2011-12-22].

close action-678

<trackbot> ACTION-678 Write a combo of 261-263 to one SC, and intents, etc.
closed

<Wayne> clink, clink
generated content

need to reopen and respond to html5 bug

<kford> jim are you still in irc

1. generated content (gc) speaks with a screen reader on the Mac in Opera
and Safari

<kford> were you going to talk with GL about generated content?

1a. speaks with screen reader on PC in Chrome

2. gc prints on all UA

3. copy and paste does not work in any UA (ff, chome, ie, opera - all on
PC), mac? safari?

4. search - if text is on the screen it should be searchable. in Opera (PC)
you can search for terms, it will find but not highlight. search does not
find gc on ff, ie, chrome on the PC. need further testing on the MAC

[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, 15 December 2011 19:55:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 15 December 2011 19:55:50 GMT