<trackbot> Date: 30 April 2015

delete item 2

remove item 1

<scribe> scribe: allanj

<jeanne> Overview of the plan for UAWG coming from a lot of discussions

<jeanne> ... publish UAAG and UAAG Reference as Notes

<jeanne> ... include the testing in the Reference doc

<jeanne> ... at the end of the charter, merge with ATAG WG and UAWG and probably WCAG into a combined group.

<jeanne> http://www.w3.org/WAI/UA/2015/draft_uawg_charter.html

open item 5

Draft Charter

gl: should add "dialog with user, browser vendors,..."

+1

kp: +1

Publish stabilization draft

+1

<jeanne> +1 to publishing a working draft

<Greg> +1

<Kim> +1

RESOLUTION: UAWG agrees to publish a Stabilization Draft of UAAG20

Draft Charter

<jeanne> Jim: We need to add browsers have to meet WCAG by default. Anything the author can do before it is customized should meet WCAG

<jeanne> ... new example I found: Arrowing down through an options list in one browser, the options color doesn't meet WCAG for color contrast.

<jeanne> ... and it is not stylable by the author or the user, so it can't be repaired.

<jeanne> ... another example: The language tag change is not being picked up by the assistive tech. Published on the IG list.

1. Transform User Agent Accessibility Guidelines (UAAG) 2.0 to a W3C Note. UAAG guides developers in designing user agents that make the web more accessible to people with disabilities. The process of transforming UAAG to a Note will include: dialog with users and browser vendors, identifyng any approaches that need updating, and wrapping up additional comments.

2. Complete development of UAAG 2.0 Reference: Explanations, Examples, and Resources for User Agent Accessibility Guidelines 2.0 as a Note. UAAG 2.0 Reference includes explanations, applicability, examples, resources, and tests for the UAAG 2.0 success criteria. The completion process will include response to comments, updates from changes to the UAAG 2.0 success criteria, and integration of...

scribe: the UAAG 2.0 tests from the UAWG wiki.

3. Contribute user requirements and relevant user agent accessibility support needs to be included and addressed as part of the WAI 2020 Framework. This work will be done in coordination with WCAG WG.

kp: a very good idea

4. Develop UAAG 2.0 introductory and overview materials in cooperation with the EOWG.

5. Maintain UAAG 2.0 Reference with additional examples and resources for user agents on specific types of devices, technologies, and industries including mobile, media, webTV, and digital publishing.

gl: timeline may overtake #5, and UAWG won't have time to do this

6. Transition more user agent need expertise to more coordinated work with APA on reviewing specs on user agent issues.

js: APA is new name for PF
... members can move to APA to provide expertise
... deleted Testing Materials from Deliverables, as they will be incorporated in Reference document

===Timeline====

js: pub in 2 weeks, get comments. Final doc in September
... reference doc finish in Dec
... Delete Testing Materials from Success Criteria

ja: publish user requirements as a note? or just submit info to WAI2020
... if a note then add to Success criteria

js: remove #5

kp: we can update the note as needed

browser behaviors

https://lists.w3.org/Archives/Public/w3c-wai-ua/2015AprJun/0024.html

gl: can't search, save, copy/paste, read (with screen reader) generated content
... can't stop animations
... not maintain point of regard when zooming, or screen size changes

kp: nonstandard keyboard interface across browsers make it difficult to switch browsers for speech control users

<Greg> Easy way to replace images with alternative content.

gl: can't turn off images and have 'alt' text displayed. can't search the 'alt' even when it is on the screen

<Greg> Option to prevent wrapping when performing sequential searches.

<Greg> Allowing users to install and toggle User Style Sheets.

<Greg> That includes multiple, cascading user style sheets.

kp: user need to be able modify the default commands in the browser, be able to save and share. single key commands don't work for speech control.

charter - http://www.w3.org/WAI/UA/2015/draft_uawg_charter.html

js: should use cases be a note or just input

judy: what about " what browsers can do help meet WCAG"
... name is WG Note, not W3C note
... UAAG support for WCAG would be good

ja: could incorporate in the guideline note, without creating another document

judy: add active taskforces at time of Charter is Mobile Accessibility TF (jointly with WCAG), add as a bullet

close item 3

close item 4

close item 5

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: Jim_Allan, Jeanne, Greg_Lowney, Kim_Patch, Judy
Present: Jim_Allan Jeanne Greg_Lowney Kim_Patch Judy
Regrets: Jan
Found Date: 30 Apr 2015
Guessing minutes URL: http://www.w3.org/2015/04/30-ua-minutes.html
People with action items: