W3C

- DRAFT -

User Agent Accessibility Guidelines Working Group Teleconference

01 Oct 2015

See also: IRC log

Attendees

Present
jeanne, jim, greg
Regrets
Chair
jim
Scribe
allanj

Contents


<trackbot> Date: 01 October 2015

http://w3c.github.io/UAAG-Implementations/Implementations-by-feature

<scribe> scribe: allanj

Open Item 1

Announcements

Jeanne on leave till Nov 30

UAAG Working Draft comments close 13 October 2015

close item 1

open item 2

Jim on vacation for next 2 weeks

<jeanne> https://lists.w3.org/Archives/Public/public-uaag2-comments/

2.10.6 Navigation of Time-Based Media by Time

quicktime, real, and wmp allow this. JwPlayer, PayPal player and OZ player all allow this

youtube player also

all of these allow relative units (5, 10, 15, 20, 30 seconds)

<Greg> It might be nice to say something like "For example, by sliding a scroll bar (continuous scale) and by using a command to jump forward or backwards a certain amount of time (relative units)"

add to intent

2.10.7 Navigation of Time-Based Media by Semantics

quicktime does

https://www.youtube.com/watch?v=O8Ja4u8_RGQ

youtube allows nav by chapter (section) they are highlighted in the timeline

jwplayer has chapter navigation

2.10.8 Video Contrast and Brightness

quicktime, real, and wmp

stand alone players

vlc does also

<allanj_> http://www.addictivetips.com/windows-tips/15-features-of-vlc-player-that-you-probably-dont-know-about/

2.11.1 Platform Text Input Devices:

<allanj_> all seem to work with what ever keyboard, braille, onscreen, etc.

there may be some instances, applications, that don't work

<Greg> I have noticed that on Android apps can provide their own on-screen keyboards, as far as I can tell refusing to use the one's you've installed at the system level. If a browser does that, it will fail this SC.

2.12.2 Operation With Any Device

https://support.apple.com/kb/PH13833?locale=en_US

https://developer.yahoo.com/blogs/ydn/enabling-full-keyboard-access-mac-090053716.html

<Greg> For example, are there any functions you cannot do in browser X on platform Y with the available on-screen keyboards? For Chrome on Android, can you "go to the next link" using the touchscreen? Or is "go to the next link" a command on desktop computers that simply isn't supported on touchscreen-only devices?

<scribe> New number is 2.11.1

chrome, ie, firefox, and safari

3.1.1 Text Entry Undo

on desktop there is undo. no undo on mobile

3.1.2 Settings Changes can be Reversed or Confirmed

IE has reset,

firefox has refresh. removes all extenstions sets browser to default settings

chrome has reset

<Greg> It does not appear that Chrome lets you override author colors any more.

<Greg> Jim just verified that in Firefox you can adjust settings to always use white text on a white background, making the Settings page unusable. There does not seem to be any Undo for this change.

<Greg> Thus, Firefox fails this one.

firefox fails, no confirmation, no Undo button, can set text to white on white. settings page is html so all settings vanish

New Guidelines group - use cases

- WCAG and UAAG are different sides of the screen related to accessibility

- browsers meet WCAG by default - need fail examples

- mobile use cases for browsers

- low vision use cases for browsers

examples in our document are good, but there are too many

need to distill, or combine

meetings will reconvene on Oct 22.

trackbot, end meeting

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2015/10/01 18:35:51 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: allanj
Inferring ScribeNick: allanj
Default Present: jeanne, jim, greg
Present: jeanne jim greg
Found Date: 01 Oct 2015
Guessing minutes URL: http://www.w3.org/2015/10/01-ua-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]