16:49:22 RRSAgent has joined #ua 16:49:22 logging to http://www.w3.org/2012/05/17-ua-irc 16:49:24 RRSAgent, make logs public 16:49:24 Zakim has joined #ua 16:49:26 Zakim, this will be WAI_UAWG 16:49:26 ok, trackbot; I see WAI_UAWG()1:00PM scheduled to start in 11 minutes 16:49:27 Meeting: User Agent Accessibility Guidelines Working Group Teleconference 16:49:27 Date: 17 May 2012 16:49:34 rrsagent, set logs public 16:50:08 Chair: Jim Allan, Kelly Ford 16:50:21 Agenda+ Face to Face planning 16:51:18 Agenda+ finalize 1.7 http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0040.html, http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0042.html 16:51:31 Agenda+ Action-631 UAAG:next? 16:52:29 Agenda+ Action-630 is this done? http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0070.html 16:52:47 Agenda+ Action-631 UAAG:next? 16:58:44 Agenda+ 1.11.1 & 1.11.2 Action-467 Jim (revise for proposal) https://www.w3.org/WAI/UA/tracker/actions/467 16:59:30 Greg has joined #ua 16:59:53 WAI_UAWG()1:00PM has now started 17:00:00 +Greg_Lowney 17:01:26 sharper has joined #ua 17:01:43 zakim, code? 17:01:43 the conference code is 82941 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), sharper 17:01:50 Jan has joined #ua 17:01:55 zakim, code? 17:01:55 the conference code is 82941 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), Jan 17:02:05 +??P4 17:02:19 zakim, ??P4 is really Jan 17:02:19 +Jan; got it 17:02:20 jeanne has joined #ua 17:02:38 +Jeanne 17:02:58 zakim, who is here? 17:02:58 On the phone I see Greg_Lowney, Jan, Jeanne 17:02:59 On IRC I see jeanne, Jan, sharper, Greg, Zakim, RRSAgent, JAllan, trackbot 17:03:14 +??P5 17:03:17 zakim, ??P5 is sharper 17:03:17 +sharper; got it 17:04:04 +Kim_Patch 17:04:19 +Jim_Allan 17:04:33 KimPatch has joined #ua 17:06:57 zakim, agenda? 17:06:57 I see 6 items remaining on the agenda: 17:06:59 1. Face to Face planning [from JAllan] 17:06:59 2. finalize 1.7 http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0040.html, http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0042.html [from JAllan] 17:06:59 3. Action-631 UAAG:next? [from JAllan] 17:06:59 4. Action-630 is this done? http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0070.html [from JAllan] 17:06:59 5. Action-631 UAAG:next? [from JAllan] 17:07:02 6. 1.11.1 & 1.11.2 Action-467 Jim (revise for proposal) https://www.w3.org/WAI/UA/tracker/actions/467 [from JAllan] 17:07:38 zakim, open item 1 17:07:38 agendum 1. "Face to Face planning" taken up [from JAllan] 17:08:23 js: any request for items on agenda, or other issues. 17:08:51 ja: any dietary issues? 17:13:05 zakim, close item 1 17:13:05 agendum 1, Face to Face planning, closed 17:13:06 I see 5 items remaining on the agenda; the next one is 17:13:06 2. finalize 1.7 http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0040.html, http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0042.html [from JAllan] 17:13:14 zakim, open item 2 17:13:14 agendum 2. "finalize 1.7 http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0040.html, http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0042.html" taken up [from 17:13:18 ... JAllan] 17:15:43 http://www.w3.org/WAI/UA/2012/ED-UAAG20-20120510/#gl-style-sheets-config 17:17:48 http://www.w3.org/WAI/UA/2012/ED-UAAG20-20120510/#def-stylesheet 17:18:44 http://www.w3.org/WAI/UA/2012/ED-UAAG20-20120510/#def-style-grouping 17:21:09 gl: use term stylesheet, define broadly to cover other technologies 17:21:14 Most agreed they did not see that Style Rule and Style Grouping designation was needed. There are no links to it. 17:21:19 ... perhaps a note 17:21:22 http://en.wikipedia.org/wiki/Style_sheet_%28web_development%29 17:21:32 A web style sheet is a form of separation of presentation and content for web design in which the markup (i.e., HTML or XHTML) of a webpage contains the page's semantic content and structure, but does not define its visual layout (style). Instead, the style is defined in an external style sheet file using a style sheet language such as CSS or XSL. 17:21:57 GL: I would keep the definition of Stylesheet, but it needs to include non-CSS technologies. 17:25:10 In particular, it is a set of style rules that can both be separated from content and applied to content. 17:25:28 JS: CSS does not appear to define Stylesheet. However, they do have a concept of Style Profile which is diffferent from what Wayne was proposing, which strengthens my opinion not to use the term Style Profile as it will be more confusing. 17:25:49 Content that supports only inline styling would not count, presumably, but what about a script that applied styles, or applied inline stylings? If a script bolds every phrase ending in a colon, or underlines every other word, would they count? 17:30:49 scribe: jallan 17:31:11 Ensure the final definition applies to non-markup (e.g. binary) file formats, and that it is clear on whether or not scripts count, and that the stylesheets can be separate from content and applied to content. 17:32:30 action: jan to write definition of stylesheet. 17:32:30 Created ACTION-729 - Write definition of stylesheet. [on Jan Richards - due 2012-05-24]. 17:33:30 Resolution: remove other definitions related to style (profile, rule, etc.) 17:33:59 Re 1.7.1 we could simply require that the same styling or formatting mechanisms available to authors should be available to users. For example, if authors can define a style sheet but users could only define scripts, they might both be equally effective but one is far more difficult. 17:35:25 ja: thought, last week we removed 'equally effective' from the SC, not testable 17:36:08 gl: what the method available to users is usable and as easy it is for authors. 17:37:40 ... add a note in the intent. explaining the mechanism for users 17:39:49 resolution: remove words "an equally effective" replace with "a", and use UAAG standard phrasing 17:40:24 1.7.1 If the user agent supports a mechanism for authors to supply stylesheets, the user agent also provides a mechanism for users to supply stylesheets. 17:42:26 gl: level of 1.7.2, currently A, could be AA, quotes from email message 17:44:59 It seems that 1.7.2 could be AA because the bare minimum component, C, is already covered by 1.7.1; what 1.7.2 adds is the ability to switch between that baseline and more complex behaviors (A and B). 17:45:57 I would not fail a browser from minimal accessibility because it failed to do A and B, even though I would hope every browser would do them. 17:48:25 -Jan 17:50:38 Jan has joined #ua 17:51:22 Jim, when working on 1.7.4 note that if you lose the part after the comma (as per the email discussino) then you're left with the problem of a lot of tools (e.g. Session Manager) that you can only save and restore them on a single system, but cannot transfer them between systems and cannot modify them. That would almost entirely remove their usefulness. 17:53:05 action: Jim to revise GL 1.7, pay attention to current behavior and aspirational subpoints, adjust IER and add where necessary 17:53:05 Created ACTION-730 - Revise GL 1.7, pay attention to current behavior and aspirational subpoints, adjust IER and add where necessary [on Jim Allan - due 2012-05-24]. 17:53:11 JS: when Wayne originally proposed these SC, Shawn Henry (WAI's low vision person) recommended that the levels be AA or AAA. 17:53:21 +??P4 17:53:36 zakim, ??P4 is really Jan 17:53:36 +Jan; got it 17:54:06 zakim, close item 2 17:54:06 agendum 2, finalize 1.7 http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0040.html, http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0042.html, closed 17:54:10 I see 4 items remaining on the agenda; the next one is 17:54:10 3. Action-631 UAAG:next? [from JAllan] 17:56:01 zakim, open item 3 17:56:01 agendum 3. "Action-631 UAAG:next?" taken up [from JAllan] 17:56:40 kim will write IER for new SC on user generated in page bookmarks 17:56:55 zakim, close item 3 17:56:55 agendum 3, Action-631 UAAG:next?, closed 17:56:56 I see 3 items remaining on the agenda; the next one is 17:56:56 4. Action-630 is this done? http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0070.html [from JAllan] 17:57:59 zakim, open item 4 17:57:59 agendum 4. "Action-630 is this done? http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0070.html" taken up [from JAllan] 17:58:40 zakim, agenda? 17:58:40 I see 3 items remaining on the agenda: 17:58:41 4. Action-630 is this done? http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0070.html [from JAllan] 17:58:41 5. Action-631 UAAG:next? [from JAllan] 17:58:41 6. 1.11.1 & 1.11.2 Action-467 Jim (revise for proposal) https://www.w3.org/WAI/UA/tracker/actions/467 [from JAllan] 17:59:51 zakim, close item 5 17:59:51 agendum 5, Action-631 UAAG:next?, closed 17:59:52 I see 2 items remaining on the agenda; the next one is 17:59:52 4. Action-630 is this done? http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0070.html [from JAllan] 18:00:18 zakim, agenda? 18:00:18 I see 2 items remaining on the agenda: 18:00:20 4. Action-630 is this done? http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0070.html [from JAllan] 18:00:20 6. 1.11.1 & 1.11.2 Action-467 Jim (revise for proposal) https://www.w3.org/WAI/UA/tracker/actions/467 [from JAllan] 18:00:29 zakim, open item 4 18:00:29 agendum 4. "Action-630 is this done? http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0070.html" taken up [from JAllan] 18:01:27 http://www.w3.org/WAI/UA/2012/ED-UAAG20-20120510/#def-point-of-regard 18:06:55 jr: if in an interactive movie, you click on some content that takes you to a different site. you hit the back button you return to the point in the movie you return to. 18:07:34 If we want the definition of viewport to address both static visual and audio/video, we could have two paragraphs in the definition, one that starts "in video and audio..." and the other that starts "in (something else)...". Better two simple definitions than one very complicated one like we used to have for "viewport". 18:08:22 The current definition has a lot of parentheticals, making it difficult to read and comprehend. 18:08:55 jr: when zooming you zoom on a particular pixel. use that as a base 18:10:10 gl: but if I search, want the found item in the view port after zoom 18:12:16 gl: definition should be more general. 18:12:36 items that may b relevant to the def: 18:12:37 Starting with the base assumption that regardless of 18:12:39 other content that may have focus, or be selected, the current point 18:12:41 of regard is that information that is visible to the user with the 18:12:42 bounds of the viewport (user agent content area). 18:12:58 There are at least three cases where the user agent may have to take 18:13:00 action to keep the point of regard in essentially the same location 18:13:00 Sorry, couldn't find user - to 18:13:01 within the visible portion of the viewport: (a) the viewport is 18:13:03 resized; (b) the zoom/scale on the content is changed; or (c) the 18:13:05 formatting of some or all of the content changes (e.g. font or text 18:13:06 size, causing content to change height and/or rewrap). 18:13:08 In these cases the user agent should maintain the same top-left 18:13:09 (top-right for RTL) corner UNLESS there is a focussed/selected content 18:13:11 INSIDE the pre-zoomed viewport, in which case the focused/selected 18:13:13 content remains in the post-zoom viewport. 18:13:14 Note: "Content" and "selected" are used because there may be cases 18:13:16 where the viewport is zooming into just part of an element (e.g. if I 18:13:17 select a few words of text that are part of a

and zoom in) 18:14:09 Starting with the base assumption that regardless of 18:14:10 other content that may have focus, or be selected, the current point 18:14:12 of regard is that information that is visible to the user with the 18:14:14 bounds of the viewport (user agent content area). 18:14:15 There are at least three cases where the user agent may have to take 18:14:17 action to keep the point of regard in essentially the same location 18:14:17 Sorry, couldn't find user - to 18:14:18 within the visible portion of the viewport: (a) the viewport is 18:14:20 resized; (b) the zoom/scale on the content is changed; or (c) the 18:14:22 formatting of some or all of the content changes (e.g. font or text 18:14:23 size, causing content to change height and/or rewrap). 18:14:25 In these cases the user agent should maintain the same top-left 18:14:26 (top-right for RTL) corner UNLESS there is a focussed/selected content 18:14:28 INSIDE the pre-zoomed viewport, in which case the focused/selected 18:14:29 content remains in the post-zoom viewport. 18:14:31 Note: "Content" and "selected" are used because there may be cases 18:14:32 where the viewport is zooming into just part of an element (e.g. if I 18:14:34 select a few words of text that are part of a

and zoom in) 18:16:11 rrsagent, make minutes 18:16:11 I have made the request to generate http://www.w3.org/2012/05/17-ua-minutes.html JAllan 18:16:47 gl: should stay in the intent. how point of regard is used should stay in the sc 18:17:02 "The point of regard is the position in rendered content" could be "The point of regard is the portion of rendered content", or perhaps "point or portion", but it's rarely if ever a real point; normally it's at least a character which is larger than a point. 18:18:42 Even if it's just the insertion bar, that has height, if not width. 18:20:36 sc 1.8.z Maintain Point of Regard: By default, when the user changes 18:20:38 viewport or content size the point of regard remains at the same 18:20:40 relative location within the visible portion of the viewport. 18:23:23 Re 1.8.z, minor wording ambiguity "changes viewport or content size", which could be read as "changes viewport, or changes content size". 18:24:15 1.8.z Maintain Point of Regard: When the user resizes the viewport or rendered content then the point of regard remains at the same 18:24:16 relative location within the viewport. 18:25:23 gl: should this be always, or a setting 18:25:55 1.8.z Maintain Point of Regard: When the viewport or rendered content is resized, the point of regard remains at the same 18:25:56 relative location. 18:26:26 gl: limiting to resizing. 18:26:33 1. should we indeed limit this to resizing? 18:27:00 If the content changes, say a paragraph is added, or some hidden content shown, does this still apply? 18:27:10 I would say yes. 18:27:18 jim and jr +1 18:29:28 1.8.z Maintain Point of Regard: The point of regard remains at the same relative location: 18:29:29 (a) the viewport is resized 18:29:31 (b) the rendered content is resized 18:29:32 (c) rendered content is added or removed 18:30:17 gl: application, if I deleted something then the tool would shift the content to the beginning of the content 18:30:57 sharper has left #ua 18:31:11 2. Maintaining the relative location within the viewport is less important than keeping the point of regard visible. For example, let's say you do a Find and it highlights a sentence in the middle of the viewport. Now you increase the zoom considerably, it's more important for the entire highlighted sentence to be kept visible than for the beginning of the sentence to still be in the middle... 18:31:12 ...of the screen. 18:31:55 sharper has joined #ua 18:33:00 jr: 2 sc, 1 on resize and 2 on content modification 18:34:06 -Jan 18:34:15 -sharper 18:34:19 -Jeanne 18:34:30 -Kim_Patch 18:36:29 -Greg_Lowney 18:36:30 -Jim_Allan 18:36:30 WAI_UAWG()1:00PM has ended 18:36:31 Attendees were Greg_Lowney, Jan, Jeanne, sharper, Kim_Patch, Jim_Allan 18:36:45 rrsagent, make minutes 18:36:45 I have made the request to generate http://www.w3.org/2012/05/17-ua-minutes.html JAllan 18:37:01 zakim, please part 18:37:01 Zakim has left #ua 18:37:08 rrsagent, make minutes 18:37:08 I have made the request to generate http://www.w3.org/2012/05/17-ua-minutes.html JAllan 18:38:13 rrsagent, please part 18:38:13 I see 2 open action items saved in http://www.w3.org/2012/05/17-ua-actions.rdf : 18:38:13 ACTION: jan to write definition of stylesheet. [1] 18:38:13 recorded in http://www.w3.org/2012/05/17-ua-irc#T17-32-30 18:38:13 ACTION: Jim to revise GL 1.7, pay attention to current behavior and aspirational subpoints, adjust IER and add where necessary [2] 18:38:13 recorded in http://www.w3.org/2012/05/17-ua-irc#T17-53-05