W3C

- DRAFT -

User Agent Accessibility Guidelines Working Group Teleconference

22 Jan 2013

See also: IRC log

Attendees

Present
Jim_Allan, Jeanne
Regrets
Chair
SV_MEETING_CHAIR
Scribe
jeanne

Contents


<trackbot> Date: 22 January 2013

Use Cases

full featured browsers who conform

full featured browsers who are missing a few SC, but have extensions that could conform.

extensions and plugins that provides a feature or subset of features to a full functioning user agent (browser)

note: media players fit here. Maybe pdf reader

<allanj> single purpose app that the user interface and the content interface is the same

question: do want to have UAAG conformance for those extensions and plugins?

-- we eliminated AT, because it couldn't conform because it was specialized.

-- maybe different because they become part of the browser

<allanj> we added extensions, they are part of the user interface

<allanj> modify the behavior of the UA

JS: What do we gain from certifying extensions and plugins? It is making things very complicated

<allanj> an extension does nothing without being connected to the browser

<allanj> AT is stand alone and doesn't need a browser to function

JS: but they do become part of the user interface, and therefore need to be conformant when installed. So possibly follow the ATAG model of saying they can't block conformance of the full featured user agent.
... they can't modify the user interface so that they make it inaccessible.

<allanj> AT can be inaccessible, they are providing access to a particular class of people. should be possible for an extension to do the same

extension partial conformance

<allanj> mouseless browsing

<allanj> meets SC XXX

<allanj> install a shortcut key

<allanj> it is configurable

<allanj> changes the user interface

<allanj> partial conformance claim: when plugged into UA ZYX, it meets SC xxx

use case of the user agent that works on one platform but not another

UNKNOWN_SPEAKER: that's covered pretty well.

Apps as User Agents

American Airlines app

scribe: constrained content (covered by Jan's proposal)

JA: The user interface and the content interface are all you get. There is no more. They are the same, it's the only interface you get.

<allanj> works on phone, only reads AA data,

<allanj> user interacts with the controls,

media players could also fit here, that I think it fits better with extensions, because it can only do one thing, while apps can do many, many things.

scribe: apps for Skype, Facebook, games, weather report, instant messaging etc. Apps are different that media players, IMO.

Apps can full featured apps that conform. Example, Facebook app on mobile covers all different types of media.

JA: Facebook on Android doesn't have font size adjustment, which means it can't comply on the Android, because Android doesn't have zoom.

<allanj> app are fully conformant then gets rated a a full browser

Use Case: App that needs the platform features to be conformant, e.g. zoom.

scribe: Facebook app on iOS can zoom, but Android cannot, so Facebook on Android is not accessible to low vision users, or my husband without his reading glasses.
... I think this is covered by Jan's platform proposal

Use case: Apps with constrained content, like the American Airlines app.

<allanj> UAWG will be finding 2 implementations for each SC, and will have to test/document/track each one for every SC

JS: Apps on the iOS can zoom, but the zoom has to be enabled. The American Airlines app on the iOS loging page doesn't zoom. The Music player app doesn't zoom. The text is too small and doesn't increase. Not accessible.

<allanj> zaikim, please part

JS: Large fonts on iOS platform settings are not applied to apps, not Facebook, not Linked In, or on Music player. They were applied to Notepad, but not the Notepad dates, which stayed in the small system font.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.137 (CVS log)
$Date: 2013-01-22 16:31:17 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.137  of Date: 2012/09/20 20:19:01  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/SE/SC/
No ScribeNick specified.  Guessing ScribeNick: jeanne
Inferring Scribes: jeanne
Default Present: Jim_Allan, Jeanne
Present: Jim_Allan Jeanne

WARNING: Fewer than 3 people found for Present list!


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 22 Jan 2013
Guessing minutes URL: http://www.w3.org/2013/01/22-ua-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]