minutes: user agent telecon 20 Nov 2014

from: http://www.w3.org/2014/11/20-ua-minutes.html
User Agent Accessibility Guidelines Working Group Teleconference 20 Nov 2014

See also: IRC log  http://www.w3.org/2014/11/20-ua-irc
Present Jeanne, Kim_Patch, Jan, Jim_AllanRegretskelly, gregChairJimAllan

   - Topics <http://www.w3.org/2014/11/20-ua-minutes.html#agenda>
      1. 2.10 flashing.
      2. 1.2.2 removal <http://www.w3.org/2014/11/20-ua-minutes.html#item02>
      3. 2.10 <http://www.w3.org/2014/11/20-ua-minutes.html#item03>
      4. 2.11.7 semantic nav for time-based media
      5. 2.12.2 operation with any device
      6. 3.1.2 setting changes
      7. 3.1.4 <http://www.w3.org/2014/11/20-ua-minutes.html#item07>
   - Summary of Action Items


<trackbot> Date: 20 November 2014
2.10 flashing.

comment: 2.10 can't be A. We are not at all sure this is implementable. The
browser does not always know how something will flash. Flash rate is
dependent on script, system state (is my swap file full? It will run
slower) and hardware.

ja: there is the Applicability notes - for recognized

1.2.2 removal

no implementations, no test

*RESOLUTION: remove 1.2.2*

ja: not sure there are any implementations for 2.10.1 or 2.10 2

jr: have an SC for no autoplay on video
... largest part of flashing may come from certain videos

<Jan> 2.11.1 Time-Based Media Load-Only:

<Jan> 2.11.2 Execution Placeholder

<Jan> 2.11.3 Execution Toggle

ja: other than ESC to stop animated gifs, otherwise no good way to stop all
of the other things that could flash
... there are no UAs that preemptively stop motion even in animated gifs
... at one time these were only for UA UI

jr: ok with setting back to UA UI

<jeanne> +1 for going back to UA UI

ja: browser developers should be able to control the amount of flashing
that the UA user interface does

js: how to test, look at all screens,

jr: review documentation

js: make error conditions, see

<jeanne> https://www.w3.org/WAI/UA/work/wiki/Tests_for_CR

ja: WG changed to wording to make flashing specific to UA UI, developers
should be able to control the amount of flashing that the UA user interface
2.11.7 semantic nav for time-based media

MS06: 2.11.7 might make more sense as AT than mainstream UA requirement

<Jan> http://www.w3.org/TR/media-accessibility-reqs/#captioning

<Kim> MS06: 2.11.7 This does have existing implementations outside AT.
Mainstream uses are also increasing and include journalists and archivists.

<Kim> It's possible to jump between chapters in mainstream players
including QuickTime and real media
2.12.2 operation with any device

MS06: 2.12.2 should be A. It is required for WCAG and is easy to implement

jr: what is an input device, how do I test this.
... for ios - keyboard, braille display, switch,
... 2.1.1 keyboard functionality. so this is more than keyboard
... if you could only use a mouse, then 2.12.2 means everything can be done
with a mouse, and 2.12.3 including text input
... how does speech input play into this

kp: works on laptop and desktop. not so much on mobile

there is no definition of Device

jr: how to test

discussion of input on mobile

kp: don't want to limit any mix of input (gesture for somethings, speech
for other, keyboard for other)

jr: is this done by OS or UA

kp: better if OS

discussion of APIs

ja: would just have 2.12.3 if platform supports input mechanism, then user
can command, control, and text input at level A

jr: want to make it clear, that the UA is constained by the OS.
... sometime the OS doesn't provide service all the way to applications
... api issues are tough
... is testing ... using all devices and see if the UA works?

ja: that sound right

jr: like collapsing into 1

js: say instead of supported "can be equipped"
... never mind

ja: agreement on rolling into one SC, test with a bunch of devices

jr: we have keyboard at level A, this is extra so AA, and UA need to pass
at A

ja: most could pass at AA

kp: on mobile you can map speech to keyboard, but not speech to gesture

ja: so need a new API

jr: in the OS

kp: no speech control of browser, can navigate in content and text input.
no mapping of speech to controls

Proposal: remove 2.12.1 and 2.12.2, make 2.12.3 AA

<jeanne> +1

and 2.1.1 covers keyboard at A

jr: cross reverence 2.1.1 and 2.12.1

*RESOLUTION: remove 2.12.1 and 2.12.2, make 2.12.3 AA. cross reverence 2.1
and 2.12*
3.1.2 setting changes

MS06: 3.1.2 should be AA. It may be difficult to implement. I am not aware
of any browser that currently support it. Requiring confirmation is easy,
but greatly decreases usability.

jr: all setting changes can be reversed.
... confirmation is "or" so UAs don't have to do it.

<Jan> http://w3c.github.io/UAAG/UAAG20/#gl-store-prefs

*RESOLUTION: leave 3.1.2 at A*

jr: this should go in Setting section (2.7)

<Jan> Guideline 2.7 - Configure and store preference settings

<Jan> JR: Let's just leave it and avoid renyumbering

MS06: 3.1.4 should be A. All the browsers support it.

jr: do all mobile browsers support it? will users loose accessibility if
the document doesn't have spell check

ja: checked default browser on android, it auto corrects

*RESOLUTION: leave at AA, no user will loose accessibility if the document
doesn't have spell check*
 Summary of Action Items [End of minutes]

[image: http://www.tsbvi.edu] <http://www.tsbvi.edu>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, 20 November 2014 19:34:23 UTC