16:27:37 RRSAgent has joined #ua 16:27:37 logging to http://www.w3.org/2015/04/30-ua-irc 16:27:39 RRSAgent, make logs public 16:27:41 Zakim, this will be WAI_UAWG 16:27:41 ok, trackbot; I see WAI_UAWG()1:00PM scheduled to start in 33 minutes 16:27:42 Meeting: User Agent Accessibility Guidelines Working Group Teleconference 16:27:42 Date: 30 April 2015 16:27:47 rrsagent, set logs public 16:28:01 chair: Jim Allan 16:28:10 regrets: Jan 16:37:42 agenda+ DRAFT Charter http://www.w3.org/WAI/UA/2013/draft_uawg_charter.html 16:37:44 agenda+ implementations - not testing, just the settings/tools 16:37:45 agenda+ user requirements 16:37:56 agenda? 16:38:15 delete item 2 16:55:01 remove item 1 16:55:31 agenda+ DRAFT Charter http://www.w3.org/WAI/UA/2015/draft_uawg_charter.html 16:55:37 scribe: allanj 16:58:59 WAI_UAWG()1:00PM has now started 16:59:06 +Jim_Allan 17:00:18 +Jeanne 17:03:15 +Greg_Lowney 17:03:30 +Kim_Patch 17:04:01 Greg has joined #ua 17:09:31 agenda? 17:11:31 rrsagent, make minutes 17:11:31 I have made the request to generate http://www.w3.org/2015/04/30-ua-minutes.html allanj 17:11:58 rrsagent, set logs public 17:13:09 Overview of the plan for UAWG coming from a lot of discussions 17:13:26 Kim has joined #ua 17:14:12 ... publish UAAG and UAAG Reference as Notes 17:20:40 ... include the testing in the Reference doc 17:21:10 ... at the end of the charter, merge with ATAG WG and UAWG and probably WCAG into a combined group. 17:22:25 http://www.w3.org/WAI/UA/2015/draft_uawg_charter.html 17:23:47 open item 5 17:24:03 topic: Draft Charter 17:25:46 gl: should add "dialog with user, browser vendors,..." 17:25:50 +1 17:25:58 kp: +1 17:26:25 Topic: Publish stabilization draft 17:26:42 +1 17:26:45 +1 to publishing a working draft 17:26:46 +1 17:27:06 +1 17:27:48 RESOLUTION: UAWG agrees to publish a Stabilization Draft of UAAG20 17:28:03 topic: Draft Charter 17:29:53 Jim: We need to add browsers have to meet WCAG by default. Anything the author can do before it is customized should meet WCAG 17:30:36 ... new example I found: Arrowing down through an options list in one browser, the options color doesn't meet WCAG for color contrast. 17:31:04 ... and it is not stylable by the author or the user, so it can't be repaired. 17:32:51 ... another example: The language tag change is not being picked up by the assistive tech. Published on the IG list. 17:34:52 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. 17:35:03 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... 17:35:05 ...the UAAG 2.0 tests from the UAWG wiki. 17:35:15 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. 17:35:26 kp: a very good idea 17:35:43 4. Develop UAAG 2.0 introductory and overview materials in cooperation with the EOWG. 17:36:08 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. 17:36:55 gl: timeline may overtake #5, and UAWG won't have time to do this 17:37:16 6. Transition more user agent need expertise to more coordinated work with APA on reviewing specs on user agent issues. 17:37:28 js: APA is new name for PF 17:39:04 js: members can move to APA to provide expertise 17:41:43 js: deleted Testing Materials from Deliverables, as they will be incorporated in Reference document 17:41:57 ===Timeline==== 17:42:35 js: pub in 2 weeks, get comments. Final doc in September 17:42:59 js: reference doc finish in Dec 17:46:52 js: Delete Testing Materials from Success Criteria 17:48:11 ja: publish user requirements as a note? or just submit info to WAI2020 17:48:41 ... if a note then add to Success criteria 17:49:56 js: remove #5 17:50:16 kp: we can update the note as needed 17:54:11 -Jeanne 17:54:31 +Jeanne 17:56:12 zakim, code? 17:56:12 the conference code is 82941 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), jeanne 17:58:04 topic: browser behaviors 17:58:06 https://lists.w3.org/Archives/Public/w3c-wai-ua/2015AprJun/0024.html 17:59:10 gl: can't search, save, copy/paste, read (with screen reader) generated content 17:59:27 gl: can't stop animations 18:00:07 gl: not maintain point of regard when zooming, or screen size changes 18:01:15 kp: nonstandard keyboard interface across browsers make it difficult to switch browsers for speech control users 18:02:35 Easy way to replace images with alternative content. 18:02:43 gl: can't turn off images and have 'alt' text displayed. can't search the 'alt' even when it is on the screen 18:02:52 Option to prevent wrapping when performing sequential searches. 18:03:24 Allowing users to install and toggle User Style Sheets. 18:07:02 That includes multiple, cascading user style sheets. 18:07:55 +Judy 18:08:12 Judy has joined #ua 18:08:49 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. 18:08:55 charter - http://www.w3.org/WAI/UA/2015/draft_uawg_charter.html 18:10:27 js: should use cases be a note or just input 18:16:19 zakim, who's on the phone? 18:16:19 On the phone I see Jim_Allan, Greg_Lowney, Kim_Patch, Jeanne, Judy 18:19:11 judy: what about " what browsers can do help meet WCAG" 18:24:54 judy: name is WG Note, not W3C note 18:30:19 judy: UAAG support for WCAG would be good 18:31:30 ja: could incorporate in the guideline note, without creating another document 18:32:34 judy: add active taskforces at time of Charter is Mobile Accessibility TF (jointly with WCAG), add as a bullet 18:33:57 -Judy 18:37:12 close item 3 18:37:16 close item 4 18:37:28 agenda? 18:37:33 close item 5 18:37:41 rrsagent, make minutes 18:37:41 I have made the request to generate http://www.w3.org/2015/04/30-ua-minutes.html allanj 18:38:17 -Kim_Patch 18:38:18 -Greg_Lowney 18:38:21 zakim, please part 18:38:21 leaving. As of this point the attendees were Jim_Allan, Jeanne, Greg_Lowney, Kim_Patch, Judy 18:38:21 Zakim has left #ua 18:38:50 rrsagent, make minutes 18:38:50 I have made the request to generate http://www.w3.org/2015/04/30-ua-minutes.html allanj 18:39:17 rrsagent, please part 18:39:17 I see no action items