W3C

- DRAFT -

User Agent Accessibility Guidelines Working Group Teleconference

24 Jan 2013

See also: IRC log

Attendees

Present
Jeanne, [Microsoft], Greg_Lowney, Jim_Allan, sharper, Kim_Patch, EricHansen
Regrets
Jan
Chair
SV_MEETING_CHAIR
Scribe
kford, sharper, jallan

Contents


<trackbot> Date: 24 January 2013

<kford> scribe: kford

<allanj> UAWG review of First Public Working Draft of IndieUI: Events needed http://www.w3.org/TR/2013/WD-indie-ui-events-20130122/

<sharper> scribe: sharper

UAWG review of First Public Working Draft of IndieUI: Events needed http://www.w3.org/TR/2013/WD-indie-ui-events-20130122/

JS: INDIEUI Events working draft published - now have a dependancy on UAWG to prevent overlap
... There group formed to look at modality independance
... They would like us to look at this.
... Normally they don't have dependancies to other WAI groups - at our suggestion
... Lets look at it - and decide on responces

<jeanne> Overview -> http://www.w3.org/WAI/intro/indieui

<jeanne> Document -> http://www.w3.org/TR/indie-ui-events/

<jeanne> Blog -> http://www.w3.org/QA/2013/01/indie-ui_events_fpwd.html

<allanj> Latest editor's draft - http://www.w3.org/WAI/UA/2012/ED-UAAG20-20130108

<allanj> http://www.w3.org/WAI/UA/2013/ED-UAAG20-20130108/

conformance use cases for conformance scenarios (extensions, mobile apps, etc)

<allanj> http://lists.w3.org/Archives/Public/w3c-wai-ua/2013JanMar/0003.html

<allanj> http://lists.w3.org/Archives/Public/w3c-wai-ua/2013JanMar/0010.html

<allanj> http://www.w3.org/2013/01/22-ua-minutes.html - new thoughts

<jeanne> http://lists.w3.org/Archives/Public/w3c-wai-ua/2013JanMar/0012.html - Use cases

JA: First link Greg Wrote / 2nd link responses / 3rd link / JA-JS discussion / Link 4 is the cleaned up version.

JS: 2nd is full featured missing some criteria but could conform with extensions

3rd partial features which don't conform

4th stand alone applications

Use Cases: (Full Conformance?)

1) full featured user agents who conform (full regular conformance)

2) full featured user agents who are missing a few SC, but could conform

with external extensions

3) limited user agents who are constrained by the type of content they

access -- e.g. media players

4) standalone software that has a user agent component (e.g. Microsoft

Word).

Use Cases: (Partial Conformance?)

5) Mobile apps with constrained content -- e.g. the "American Airlines"

app.

6) User agent component

7) User agent component - a full featured browser or player that is

missing some SC but doesn't want to state a specific extension that

could complete it.

8 ) full or limited user agents who are dependent on the underlying

platform for some SC.

JS: 1st = covered

2nd = Stop trying to provide partial conformance to the browsers by allowing outside extensions

EH: claimant is defining the uA and the conformance claimed pertains to their defn of the UA - assumption has been that if they say that the UA + this extension is what is being evaluated then that is what will be evaluated
... if we can state up from what flexibility the claimant has in defining the boundaries of the UA
... makes things easier now.

KP: if they provide instructions to extension then I've been assuming this is what will be evaluated.

EH: shouldn't matter who owns that extension - then that is what is evaluated

KP: good extensions should count

EH: Licensing arrangements are irrelevant to conformance - their claim is via any number of defined inclusions or exclusions

JS: I could be talked into that - not adding a whole new structure - claimant defines what parts is their user agent. Defining the boundary of the UA.

EH: discussion of the boundaries of the UA - around JS: #2

JS: will be the boundary - what is an extension and what is an assistive technology

EH: we don't ask for testing but my assumption is that it has to work together

JS: We will have to test for w3c policy
... we have to show 2 implementations of each success criteria.

<allanj> scribe: jallan

<Greg> Three separate discussions: (1) what products needs to be tested against UAAG20; (2) how to test the product against each SC, and what specific answers are allowed e.g. pass, fail, not applicable; (3) how to summarize those into a conformance claim, including conformance levels, partial conformance claims if we allow them, whether you have to cite specific add-ons, etc.

<allanj> ja: tries to summarize

<allanj> js provided use cases

<allanj> discussion of conformance, progress toward conformance, but must set some bar

<allanj> gl: partial conformance, pass 75% of A, 53% of AA, and 23% of AAA

<allanj> kp: should list what is not met

<allanj> js: percentages are tough. and contentious. 150 preferences, how to weight fully met, some trivial thing missed vs. an important item is missed.

<Greg> Jeanne, I didn't mean to suggest that they measure what percentage of their product complies with a particular SC, but rather what percentage of the SC their entire product complies with.

<Greg> And of course the actual answers for all SC would be included in the claim.

resolving @@ from the draft.

<allanj> 2.1.1 jim sent these before the new year

<allanj> http://www.w3.org/WAI/UA/2013/ED-IMPLEMENTING-UAAG20-20130108/

<Greg> 2.1.1, 2.11.2, and 4.1.2 all have @@ in the Related Resources sections.

<allanj> 2.11.2 editor task

<allanj> 4.1.2 http://lists.w3.org/Archives/Public/w3c-wai-ua/2013JanMar/0006.html

<jeanne> ACTION: jeanne to update 4.1.2 with email from Jim -> http://lists.w3.org/Archives/Public/w3c-wai-ua/2013JanMar/0006.html [recorded in http://www.w3.org/2013/01/24-ua-minutes.html#action01]

<trackbot> Created ACTION-792 - Update 4.1.2 with email from Jim -> http://lists.w3.org/Archives/Public/w3c-wai-ua/2013JanMar/0006.html [on Jeanne F Spellman - due 2013-01-31].

<allanj> 2.1.1 http://lists.w3.org/Archives/Public/w3c-wai-ua/2012OctDec/0056.html

<allanj> rrsagend, set logs public

<jeanne> ACTION: jeanne to update 2.1.1 with email from Jim -> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012OctDec/0056.html [recorded in http://www.w3.org/2013/01/24-ua-minutes.html#action02]

<trackbot> Created ACTION-793 - Update 2.1.1 with email from Jim -> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012OctDec/0056.html [on Jeanne F Spellman - due 2013-01-31].

<jeanne> ACTION: jeanne to update the link in 2.11.2 to Latest HTML5 [recorded in http://www.w3.org/2013/01/24-ua-minutes.html#action03]

<trackbot> Created ACTION-794 - Update the link in 2.11.2 to Latest HTML5 [on Jeanne F Spellman - due 2013-01-31].

glossary

<allanj> jeanne will delete the terms.

<jeanne> ACTION: jeanne to update the glossary to move all unused items to the end. [recorded in http://www.w3.org/2013/01/24-ua-minutes.html#action04]

<trackbot> Created ACTION-795 - Update the glossary to move all unused items to the end. [on Jeanne F Spellman - due 2013-01-31].

<allanj> the @@ will be removed when we formally publish. jeanne will move them to the end of the document.

<allanj> GLOBALLY - 1.4.1 need to write a definition. applies to the UA, not a specific page or particular content

<Greg> Globally: a global setting is one that applies to the entire user agent or all content being rendered by it, rather than to a specific feature within the user agent or a specific document being viewed.

<Greg> A global command is one that is available regardless of what content the user is currently viewing.

<Greg> We use "global setting"/"global option", "global volume", "global command"/"global control".

<Greg> Also "globally set".

<Greg> Those break down into global settings/options/volume (and globally set), global commands/controls.

<Greg> Might want to normalize the phrasing (e.g. change the one occurance of global option to global setting) in an editorial pass.

<jeanne> ACTION: jeanne to add definition for global - Globally: a global setting is one that applies to the entire user agent or all content being rendered by it, rather than to a specific feature within the user agent or a specific document being viewed. [recorded in http://www.w3.org/2013/01/24-ua-minutes.html#action05]

<jeanne> <Greg> A global command is one that is available regardless of what content the user is currently viewing

<trackbot> Created ACTION-796 - Add definition for global - Globally: a global setting is one that applies to the entire user agent or all content being rendered by it, rather than to a specific feature within the user agent or a specific document being viewed. [on Jeanne F Spellman - due 2013-01-31].

<jeanne> ACTION: jeanne to normalize the phrase "global settings" in intent for 1.1.2 and example for 2.9.1 [recorded in http://www.w3.org/2013/01/24-ua-minutes.html#action06]

<trackbot> Created ACTION-797 - Normalize the phrase "global settings" in intent for 1.1.2 and example for 2.9.1 [on Jeanne F Spellman - due 2013-01-31].

<allanj> add to agenda for next week - review Eric's comments

Summary of Action Items

[NEW] ACTION: jeanne to add definition for global - Globally: a global setting is one that applies to the entire user agent or all content being rendered by it, rather than to a specific feature within the user agent or a specific document being viewed. [recorded in http://www.w3.org/2013/01/24-ua-minutes.html#action05]
[NEW] ACTION: jeanne to normalize the phrase "global settings" in intent for 1.1.2 and example for 2.9.1 [recorded in http://www.w3.org/2013/01/24-ua-minutes.html#action06]
[NEW] ACTION: jeanne to update 2.1.1 with email from Jim -> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012OctDec/0056.html [recorded in http://www.w3.org/2013/01/24-ua-minutes.html#action02]
[NEW] ACTION: jeanne to update 4.1.2 with email from Jim -> http://lists.w3.org/Archives/Public/w3c-wai-ua/2013JanMar/0006.html [recorded in http://www.w3.org/2013/01/24-ua-minutes.html#action01]
[NEW] ACTION: jeanne to update the glossary to move all unused items to the end. [recorded in http://www.w3.org/2013/01/24-ua-minutes.html#action04]
[NEW] ACTION: jeanne to update the link in 2.11.2 to Latest HTML5 [recorded in http://www.w3.org/2013/01/24-ua-minutes.html#action03]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.137 (CVS log)
$Date: 2013-01-24 19:39:58 $

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/8)/8 )/
Succeeded: s/propose stop trying to cater to the browsers - If it can be done with extensions then they should include it/Stop trying to provide partial conformance to the browsers by allowing outside extensions/
Succeeded: s/include specific/cite specific/
Found Scribe: kford
Found Scribe: sharper
Inferring ScribeNick: sharper
Found Scribe: jallan
Scribes: kford, sharper, jallan
Default Present: Jeanne, [Microsoft], Greg_Lowney, Jim_Allan, sharper, Kim_Patch, EricHansen
Present: Jeanne [Microsoft] Greg_Lowney Jim_Allan sharper Kim_Patch EricHansen
Regrets: Jan

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

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

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


[End of scribe.perl diagnostic output]