16:15:41 RRSAgent has joined #ua 16:15:41 logging to http://www.w3.org/2012/04/12-ua-irc 16:15:43 RRSAgent, make logs public 16:15:43 Zakim has joined #ua 16:15:45 Zakim, this will be WAI_UAWG 16:15:45 ok, trackbot; I see WAI_UAWG()1:00PM scheduled to start in 45 minutes 16:15:46 Meeting: User Agent Accessibility Guidelines Working Group Teleconference 16:15:46 Date: 12 April 2012 16:15:57 rrsagent, set logs public 16:16:10 chair: KellyFord, JimAllan 16:55:51 WAI_UAWG()1:00PM has now started 16:55:57 +[Microsoft] 16:56:04 jeanne has joined #ua 16:59:44 +Jim_Allan 17:01:13 Topic: ***closing Guideline 1 17:01:14 Agenda+ 1.2.1 & 1.2.2 Action-712 Simon 17:01:16 Agenda+ 1.3.2 editors note (not assigned to anyone) Kim? 17:01:17 Agenda+ 1.3.3, 1.5.1 needs decision on whether it is done or not (no 17:01:19 action items) 17:01:20 Agenda+ 1.7 Action-657 Jeanne (adding Wayne's final proposal ... which 17:01:22 one, we edited it) 17:01:22 Sorry, bad ACTION syntax 17:01:23 Agenda+ 1.8 Action-631 Jeanne (add new wording) Action-662 Jeanne (add 17:01:25 revised wording) 17:01:26 Agenda+ 1.10.2 Action-639 Jan (revise for proposal) 17:01:28 Agenda+ 1.11.1 & 1.11.2 Action-467 Jim (revise for proposal) 17:01:39 +Jeanne 17:01:44 zakim, who is here? 17:01:47 On the phone I see [Microsoft], Jim_Allan, Jeanne 17:01:55 On IRC I see jeanne, Zakim, RRSAgent, JAllan, trackbot 17:02:33 agenda? 17:02:34 zakim, agenda? 17:02:53 I see 7 items remaining on the agenda: 17:02:55 1. 1.2.1 & 1.2.2 Action-712 Simon [from JAllan] 17:02:58 2. 1.3.2 editors note (not assigned to anyone) Kim? [from JAllan] 17:02:59 3. 1.3.3, 1.5.1 needs decision on whether it is done or not (no [from JAllan] 17:03:01 4. 1.7 Action-657 Jeanne (adding Wayne's final proposal ... which [from JAllan] 17:03:02 Jan has joined #ua 17:03:03 5. 1.8 Action-631 Jeanne (add new wording) Action-662 Jeanne (add [from JAllan] 17:03:06 6. 1.10.2 Action-639 Jan (revise for proposal) [from JAllan] 17:03:07 7. 1.11.1 & 1.11.2 Action-467 Jim (revise for proposal) [from JAllan] 17:03:36 zakim, code? 17:03:36 the conference code is 82941 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), Jan 17:04:11 +??P6 17:04:32 zakim, ??P6 is really Jan 17:04:32 +Jan; got it 17:05:55 kford has joined #ua 17:10:09 +Kim_Patch 17:10:52 sharper has joined #ua 17:10:52 Kudos to ATAG for it's last Call! 17:11:25 Kim did a talk yesterday about keyboard shortcuts and voice navigation 17:11:47 +??P14 17:11:54 zakim, ??P14 is sharper 17:11:54 +sharper; got it 17:14:12 regrets: greg 17:17:45 KimPatch has joined #ua 17:17:59 zakim, open item 1 17:17:59 agendum 1. "1.2.1 & 1.2.2 Action-712 Simon" taken up [from JAllan] 17:19:27 beginning of thread: http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0008.html 17:20:10 discussion of changed wording and levels 17:21:00 Proposal: Delete 1.2.1 & 1.2.2 17:21:02 Add: 17:21:03 1.2.X Provide Available Information: If missing or empty alternative 17:21:05 content or associations are recognized, the user agent will notify the 17:21:06 user and provide a mechanism to relate all available metadata to the 17:21:08 user upon request. 17:22:20 merge the intents and examples from 1.2.1, 1.2.2 17:23:15 jr: word "associations", label for form has association. but there are others. associations is not precise enough 17:23:40 ... metadata is too general 17:24:03 sh: not sure how to do it 17:24:34 jr: see appendix on Accessibility information, could substitute for meta information. 17:24:58 ... would help scope the information 17:25:49 jr: would replace associations and metadata with 'accessibility information' 17:26:22 jr: does UAAG want to use the relative accessibility based on WCAG. 17:27:27 js: depends on the use case. this SC would be useful with photo sites. if we just to a11y information, we would eliminate all of the photo metadata available 17:27:55 ... reason I liked the 'metadata' term 17:28:06 jr: another usecase 17:28:50 ... the bigger case is the relationships, form field has visual relation ship but not in code. they need more help discovering those. 17:29:10 js: that is AI (it is difficult) 17:29:35 jr: interpage links need to be remediated. 17:30:00 js: don't want to do this a A. its too hard 17:30:47 js: simons proposal...don't try to repair, just give me the metadata the user will make some sense out of it. 17:31:01 kf: how do you cap that. 17:31:43 ... images will have resolution, time, date, geolocation, etc. dozens more. how do we scope it. 17:32:13 sh: it is useful information, but may be overwhelming, perhaps terse and verbose setting 17:32:24 kf: what does wcag require. 17:32:53 ja: alt and longdesc 17:33:19 kf: how much of the photo image info is retained when converted. 17:33:43 js: UA provides what it has. and provides it on request 17:34:46 ja: do UAs already do this? 17:36:12 sh: the act of displaying the image, must process it and have access to the metadata 17:36:54 jr: but then there is surfacing it, need UI, structure data. 17:37:12 sh: yes its not critical, but it is on user request only 17:37:46 ... disagree, it is critical to get as much info as necessary 17:39:28 ja: reviews discussion 17:39:40 q+ to propose that "associations" become "accessibility information" 17:39:58 sh: perhaps 2 sc, one for a11y info level A, and meta info at AA 17:40:26 js: but a11y info is not there, that's the point. 17:41:12 js: has proposal 17:41:26 1.2.X Provide Available Information: If missing or empty alternative content or accessibility information are recognized, the user agent will notify the user and provide a mechanism to relate all available metadata to the user upon request. 17:42:13 1.2.X Provide Available Information: If missing or empty accessibility information is recognized, the user agent will notify the user and provide a mechanism to relate all available metadata to the user upon request. 17:42:35 kf: +1 17:42:39 kim: +1 17:43:41 jr: empty?? so if an ignored image, the user can still get some info 17:44:44 sh: what if site is stupid and pastes in imagesorce as alt, then alt is not missing or empty. then UA doesn't have to do anything. 17:45:22 jr: missing, empty, or improper 17:45:48 js: how to define improper 17:46:20 sh: what about eliminate missing or empty, just give metadata 17:47:03 jr: +1, but bring it back to human language metadata, or something to scope it. 17:47:36 js: need to bind it to certain element, else its everything on the page. 17:47:53 sh: also on the focused element 17:48:26 jr: non-text element well defined by WCAG 17:49:11 http://www.w3.org/TR/2012/WD-IMPLEMENTING-ATAG20-20120410/#def-Accessibility-Information 17:49:15 http://www.w3.org/TR/2012/WD-IMPLEMENTING-ATAG20-20120410/#prompting-types 17:49:57 http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0025.html 17:50:26 scribe: jallan 17:51:01 http://www.w3.org/TR/2012/WD-ATAG20-20120410/Overview.html#sc_b233 17:51:32 js: would this apply to keyboard shortcuts 17:52:11 jr: explains ATAG b233 17:53:12 this could be a resource for 1.2.x 17:54:30 sh: what about adding poorly repaired alternative 17:55:42 js: we don't want repair, we want alternatives 17:56:30 jr: UA of future could ocr image, use databased images (OBI project from DIAGAM) 17:57:55 jr: keep 121 and 122, because they can be turned off, and add simons for additional help 17:58:26 ... user access metadata to discover. 17:58:52 js: don't like, we spent lots of time about not repairing information. 17:59:21 kf: without repair, how much effort will users go to to get information 17:59:58 sh: useful repair is so far out, thinks metadata is more important. 18:00:25 js: we wanted to eliminate stupid repair. 18:00:40 ... good with removing 121 and 122. 18:01:14 jr: then we must eliminate totally the repair. the entire point is the 'whether or not'. 18:02:18 js: how to reword to eliminate an sc. 18:02:53 jr: ATAG has concept...don't repair unless special knowledge, then kick to AT to make obvious repair. 18:03:10 ... that special knowledge is the metadata. 18:03:41 js: filename is matadata, but we want to eliminate it. 18:04:45 sh: support wrapping in 1.2.3 repair association. as a AAA 18:05:27 ... put 121 122 and 123 in to 1 sc. and the Metadata (new one is A). 18:05:43 ... other (conflated one) is AAA 18:06:49 action-712 assign to Jan 18:07:00 zakim, assign action-712 to Jan 18:07:00 I don't understand 'assign action-712 to Jan', jeanne 18:07:35 zakim, close item 1 18:07:35 I see a speaker queue remaining and respectfully decline to close this agendum, JAllan 18:07:51 zakim, q? 18:07:51 I see jeanne on the speaker queue 18:07:57 ack jeanne 18:07:57 jeanne, you wanted to propose that "associations" become "accessibility information" 18:08:06 zakim, close item 1 18:08:06 agendum 1, 1.2.1 & 1.2.2 Action-712 Simon, closed 18:08:07 I see 6 items remaining on the agenda; the next one is 18:08:07 2. 1.3.2 editors note (not assigned to anyone) Kim? [from JAllan] 18:10:04 Resolved: Remove editor's note from 1.3.2 18:10:10 zakim, close item 2 18:10:10 agendum 2, 1.3.2 editors note (not assigned to anyone) Kim?, closed 18:10:11 I see 5 items remaining on the agenda; the next one is 18:10:11 3. 1.3.3, 1.5.1 needs decision on whether it is done or not (no [from JAllan] 18:10:35 zakim, open next 18:10:35 agendum 3. "1.3.3, 1.5.1 needs decision on whether it is done or not (no" taken up [from JAllan] 18:11:35 jr: seems like we talked about this recently 18:12:58 ... what is this adding to 1.3.1 18:14:44 kim: intents are very different 18:15:05 ja: 131 does not cover scripted elements. 18:15:32 sh: these are all about visually perceiveable. what about auditory highlighting? 18:18:19 kim: need to add 'visual highlighting' to 132 18:19:02 jr: general highlighting is covered in 131 18:19:32 ... we could get prescriptive and add auditory 18:19:47 ja: what about haptic 18:20:15 kp: do we have a parallel for what the audio highlighting should be? 18:20:50 js: perhaps add to UAAG-Next! 18:21:05 kim: kelly would this be useful 18:21:15 kf: not sure 18:22:50 sh: have audio style bold, italic (different audio, voices) what about links selections, etc 18:23:12 kp: what is the audio equivelent 18:24:32 How about "If the user agent uses visual, " 18:26:05 issue: if the user agent has an audio or tactile or xxx display then provide the following highlighting...related to 1.3.1,2,3 18:26:05 Created ISSUE-91 - If the user agent has an audio or tactile or xxx display then provide the following highlighting...related to 1.3.1,2,3 ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/91/edit . 18:28:05 jr: this is a disconnect between 131 c and 133 a 18:28:36 ... what if we remove 133a and let it focus on scripted input. 18:28:42 kp: +1 18:28:48 ja: +1 18:30:19 jr: should 131 c be enabled input elements 18:33:20 action: kim to rewrite 133 to eliminate a) and make b the focus of it be b. need some rewording on the (e.g. ) perhaps eliminate. 18:33:20 Created ACTION-723 - Rewrite 133 to eliminate a) and make b the focus of it be b. need some rewording on the (e.g. ) perhaps eliminate. [on Kimberly Patch - due 2012-04-19]. 18:34:19 jr: every element on a page could have an id, don't want to highlight everything 18:34:30 ja: javascript blackhole 18:35:56 -Jan 18:36:31 ja: how is this related to tabindex=_1 18:37:37 the onclick or onkeypress are going away. 18:40:35 ja: should 133 be eliminated. because scripting is becomming more abstract, and only special case of onClick and onKeyPress 18:41:27 -sharper 18:41:30 -Kim_Patch 18:41:31 -[Microsoft] 18:41:33 -Jeanne 18:41:37 -Jim_Allan 18:41:38 WAI_UAWG()1:00PM has ended 18:41:38 Attendees were [Microsoft], Jim_Allan, Jeanne, Jan, Kim_Patch, sharper 19:24:38 s/x=_1/x=-1 19:24:46 rrsagent make minutes 19:24:55 rrsagent, make minutes 19:24:55 I have made the request to generate http://www.w3.org/2012/04/12-ua-minutes.html JAllan 19:25:48 zakim, [Microsoft] is really KellyFord 19:25:48 sorry, JAllan, I do not recognize a party named '[Microsoft]' 19:26:04 zakim, please part 19:26:04 Zakim has left #ua 19:26:11 rrsagent, make minutes 19:26:11 I have made the request to generate http://www.w3.org/2012/04/12-ua-minutes.html JAllan 19:26:24 rrsagent, please part 19:26:24 I see 1 open action item saved in http://www.w3.org/2012/04/12-ua-actions.rdf : 19:26:24 ACTION: kim to rewrite 133 to eliminate a) and make b the focus of it be b. need some rewording on the (e.g. ) perhaps eliminate. [1] 19:26:24 recorded in http://www.w3.org/2012/04/12-ua-irc#T18-33-20