16:50:52 RRSAgent has joined #ua 16:50:52 logging to http://www.w3.org/2010/09/02-ua-irc 16:50:54 RRSAgent, make logs public 16:50:54 Zakim has joined #ua 16:50:56 Zakim, this will be WAI_UAWG 16:50:56 ok, trackbot; I see WAI_UAWG()1:00PM scheduled to start in 10 minutes 16:50:57 Meeting: User Agent Accessibility Guidelines Working Group Teleconference 16:50:57 Date: 02 September 2010 16:51:16 regrets+GRosmaita 16:56:41 Greg has joined #ua 16:59:42 WAI_UAWG()1:00PM has now started 16:59:48 +kford 17:00:11 Agenda+ Select a date for a Face to Face meeting survey - http://www.w3.org/2002/09/wbs/36791/UAWG20100824/ Agenda+ Writers Meeting Survey#3 focus on questions 3-7 - http://www.w3.org/2002/09/wbs/36791/20100802-3/ Agenda+ Writers Meeting Survey#4 - http://www.w3.org/2002/09/wbs/36791/20100802-4/ Agenda+ HTML A11Y bugs relating to UA from Michael Cooper - http://lists.w3.org/Archives/Public/w3c- 17:00:12 wai-ua/2010JulSep/0061.html Agenda+ ATAG review 17:00:45 +AllanJ 17:00:45 Agenda+ Writers Meeting Survey#3 focus on questions 3-7 - http://www.w3.org/2002/09 17:01:01 Agenda+ Writers Meeting Survey#4 - http://www.w3.org/2002/09/wbs/36791/20100802-4/ 17:01:14 Agenda+ ATAG review 17:01:25 kford has joined #ua 17:01:33 Jan has joined #ua 17:01:33 +Greg 17:01:39 zakim, code? 17:01:39 the conference code is 82941 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), Jan 17:01:41 Agenda+ HTML A11Y bugs relating to UA from Michael Cooper - http://lists.w3.org/Archives/Public/w3c-wai-ua/2010JulSep/0061.html 17:01:59 Agenda+ Select a date for a Face to Face meeting survey - http://www.w3.org/2002/09/wbs/36791/UAWG20100824/ 17:02:05 zakim, agenda? 17:02:05 I see 6 items remaining on the agenda: 17:02:06 1. Select a date for a Face to Face meeting survey - http://www.w3.org/2002/09/wbs/36791/UAWG20100824/ Agenda+ Writers Meeting Survey#3 focus on questions 3-7 - 17:02:09 ... http://www.w3.org/2002/09/wbs/36791/20100802-3/ Agenda+ Writers Meeting Survey#4 - http://www.w3.org/2002/09/wbs/36791/20100802-4/ Agenda+ HTML A11Y bugs relating to UA from 17:02:11 zakim, agenda+ 17:02:14 ... Michael Cooper - http://lists.w3.org/Archives/Public/w3c- [from AllanJ] 17:02:16 2. Writers Meeting Survey#3 focus on questions 3-7 - http://www.w3.org/2002/09 [from AllanJ] 17:02:18 3. Writers Meeting Survey#4 - http://www.w3.org/2002/09/wbs/36791/20100802-4/ [from AllanJ] 17:02:23 4. ATAG review [from AllanJ] 17:02:24 5. HTML A11Y bugs relating to UA from Michael Cooper - http://lists.w3.org/Archives/Public/w3c-wai-ua/2010JulSep/0061.html [from AllanJ] 17:02:27 6. Select a date for a Face to Face meeting survey - http://www.w3.org/2002/09/wbs/36791/UAWG20100824/ [from AllanJ] 17:02:29 +??P14 17:02:50 zakim, close item 1 17:02:50 agendum 1, Select a date for a Face to Face meeting survey - http://www.w3.org/2002/09/wbs/36791/UAWG20100824/ Agenda+ Writers Meeting Survey#3 focus on questions 3-7 - 17:02:53 ... http://www.w3.org/2002/09/wbs/36791/20100802-3/ Agenda+ Writers Meeting Survey#4 - http://www.w3.org/2002/09/wbs/36791/20100802-4/ Agenda+ HTML A11Y bugs relating to UA from 17:02:58 ... Michael Cooper - http://lists.w3.org/Archives/Public/w3c-, closed 17:03:00 I see 5 items remaining on the agenda; the next one is 17:03:01 2. Writers Meeting Survey#3 focus on questions 3-7 - http://www.w3.org/2002/09 [from AllanJ] 17:03:09 sharper has joined #ua 17:03:34 zakim, code? 17:03:34 the conference code is 82941 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), sharper 17:03:41 zakim, who's here? 17:03:41 On the phone I see kford, AllanJ, Greg, ??P14 17:03:41 zakim, p14 is really JanRichards 17:03:42 On IRC I see sharper, Jan, kford, Greg, Zakim, RRSAgent, AllanJ, trackbot 17:03:44 sorry, AllanJ, I do not recognize a party named 'p14' 17:04:05 zakim, P14 is really JanRichards 17:04:15 sorry, AllanJ, I do not recognize a party named 'P14' 17:04:23 jeanne has joined #ua 17:04:25 zakim, ??P14 is really JanRichards 17:04:33 +JanRichards; got it 17:05:01 +Jeanne 17:05:03 zakim, who's your daddy? 17:05:07 Ralph is taking good care of me but you all are my family, Jan 17:05:41 +??P10 17:05:45 zakim, ??P10 is sharper 17:05:45 +sharper; got it 17:07:52 +Kim 17:08:15 KimPatch has joined #ua 17:08:17 zakim, I'm hungry 17:08:17 I don't understand 'I'm hungry', kford 17:08:28 zakim, feed me 17:08:28 I don't understand 'feed me', kford 17:08:44 zakim, agenda 17:08:44 I don't understand 'agenda', kford 17:08:50 zakim, agenda? 17:08:50 I see 5 items remaining on the agenda: 17:08:52 2. Writers Meeting Survey#3 focus on questions 3-7 - http://www.w3.org/2002/09 [from AllanJ] 17:08:55 3. Writers Meeting Survey#4 - http://www.w3.org/2002/09/wbs/36791/20100802-4/ [from AllanJ] 17:08:57 4. ATAG review [from AllanJ] 17:08:59 5. HTML A11Y bugs relating to UA from Michael Cooper - http://lists.w3.org/Archives/Public/w3c-wai-ua/2010JulSep/0061.html [from AllanJ] 17:09:02 6. Select a date for a Face to Face meeting survey - http://www.w3.org/2002/09/wbs/36791/UAWG20100824/ [from AllanJ] 17:10:44 zakim, open item 4 17:10:44 agendum 4. "ATAG review" taken up [from AllanJ] 17:11:10 UAAG Members: 17:11:11 These are the comments I am proposing to send to the official comment address for Authoring tool guidelines 2.0 last call. This is on our agenda to discuss on 9/2/2010. 17:11:13 You can find the last call document at http://www.w3.org/TR/2010/WD-ATAG20-20100708/. 17:11:15 1. 17:11:16 A.2.1.1 Recognized Alternative Content: If recognized alternative content is available for editing view content renderings, then the alternative content is provided to authors. 17:11:18 UAReview: (and other SC) this and other success criteria were at time very hard to understand (for us it depended on the line breaks). suggest changing 'editing view' to 'editing-view'. it may help the reader understand the content rendering and alternative content are in the editing-view. 17:11:19 2. 17:11:21 A.3.7.2 Preview: If a preview is provided, then at least one of the following is true: (Level A) [Implementing A.3.7.2] 17:11:22 (a) Third-Party User Agent: The preview makes use of an existing third-party user agent; or 17:11:24 the goal of A.3.7 is to ensure the preview is accessible. 17:11:26 if A.3.7.2.a is true, there is no guarantee that the 3rd party user agent is accessible. A.3.7.2.a only says there is a preview, A.3.7.2.b the preview must be accessible according to UAAG. the way A.3.7.2 is written having a preview and the preview being accessible could be mutually exclusive. 17:11:30 UAReview: Suggest changing 17:11:32 (a) Third-Party User Agent: The preview makes use of an existing third-party user agent; or to be 17:11:34 (a) Third-Party User Agent: The preview makes use of an existing third-party accessible user agent; 17:11:36 3. 17:11:38 1. Scope of authoring tool user interface: The Part A success criteria apply to all aspects of the authoring tool user interface that are under the control of the authoring tool developer. This includes views of the web content being edited and features that are independent of the content being edited, such as menus, button bars, status bars, user preferences, documentation, etc. 17:11:43 UAReview:What about authoring systems that offer end-to-end publishing and web server publication/configuration. It should be clear where any line for AU responsibility ends. 17:11:46 4. 17:11:48 A.3.6.2 Respect Platform Settings: The authoring tool respects platform display settings and control settings. 17:11:50 UAReview:Broaden this to any settings that impact accessibility? 17:11:52 5. 17:11:54 B.2.5.2 Provide Accessible Templates: If the authoring tool provides templates, then there are accessible template options for a range of template uses. 17:11:58 UAReview: How does this differ from just making any templates accessible? One would assume all templates offered should have equal accessibility. What happens if the end user selects a template with less accessibility? 17:12:00 6. 17:12:02 B.2.5.4 Template Selection Mechanism: If authors are provided with a template selection mechanism, then both of the following are true: (Level AA) [Implementing B.2.5.4] (a) Indicate: The selection mechanism indicates the accessibility status of templates (if known); and (b) Prominence: Any accessible template options are at least as prominent as other template options. 17:12:07 UAReview: The definition for prominence says in part: 17:12:09 For purposes of conformance to ATAG 2.0, item A is considered to be at least as prominent as item B if: 17:12:11 both items occur in the same item container (e.g., a menu for menu items, a list for list items, a dialog box for text boxes); if item B is emphasized, then so is item A; 17:12:14 so if the accessible option is at the bottom of a menu separated from the less accessible option by 10 entires, this is acceptable? If the list has 25 items and the user must scroll to see the accessible option, is this then acceptable? 17:13:42 Re #1 A.2.1.1, I agree totally with your concern--when read as plain text it's unfathomable. To me the clearest wording for the SC would be "is available when rendering content in editing views", if they can adopt the phrase "rendering content" as equivalent to "content rendering". 17:13:44 Re #2, A.3.7.2, I think a clearer, less subjective wording for would be "The preview makes use of an existing third-party user agent that conforms to the User Agent Accessibility Guidelines Level A; or". However, we should also acknowledge that the authoring tool may allow the user to configure which third-party user agent should be used, and should be able to pick an accessible one but... 17:13:45 ...should not be prohibited from choosing an inaccessible one. I haven't had time to draft wording that entirely works. 17:13:47 Re #3, 1., You might want to give examples to more clearly define what you mean by "authoring systems that offer end-to-end publishing and web server publication/configuration". Would that include Web-based authoring tools such as when Drupal provides forms where the user can author or edit content that it hosts, using either text markup or WYSIWIG mode, and their choice of Web browsers? 17:13:50 Re #4, A.3.6.2, Their definitions of "display settings" and "control settings" seem broad enough to possibly include all input or output preference settings; however, it would be nice if one didn't have to take the links to the glossary to figure that out, and it's still somewhat ambiguous: would it include the option to hide or show alternative text? Also, an example of preference settings... 17:13:55 ...beyond display and control settings that still affect accessibility would be the option to turn on and off AT compatibility modes such as support for platform accessibility API. 17:13:58 Re #5, B2.5.2, It sounds like you're proposing a requirement that if the user selects an inaccessible template, the authoring tool at least provides an accessible mechanism to exit the mode where they're using that template. 17:14:01 Also minor, but it might clarify that we're talking about templates that are accessible to the author while creating or editing content, not templates that are designed to produce content accessible to the end-user. Is the latter also addressed somewhere? 17:14:05 Re #6, Of the topic somewhat, but the question of whether accessible options should be displayed as prominently as, and/or in proximity to, their inaccessible counterparts applies to more things than just templates (for example, a list of schemes). 17:15:18 zakim, agenda? 17:15:18 I see 5 items remaining on the agenda: 17:15:19 2. Writers Meeting Survey#3 focus on questions 3-7 - http://www.w3.org/2002/09 [from AllanJ] 17:15:21 3. Writers Meeting Survey#4 - http://www.w3.org/2002/09/wbs/36791/20100802-4/ [from AllanJ] 17:15:24 4. ATAG review [from AllanJ] 17:15:26 5. HTML A11Y bugs relating to UA from Michael Cooper - http://lists.w3.org/Archives/Public/w3c-wai-ua/2010JulSep/0061.html [from AllanJ] 17:15:28 6. Select a date for a Face to Face meeting survey - http://www.w3.org/2002/09/wbs/36791/UAWG20100824/ [from AllanJ] 17:15:44 scribe: AllanJ 17:16:19 KF will send merged comments (including Gregs) to the ATWG after the meeting 17:16:39 zakim, close item 4 17:16:39 agendum 4, ATAG review, closed 17:16:40 I see 4 items remaining on the agenda; the next one is 17:16:41 2. Writers Meeting Survey#3 focus on questions 3-7 - http://www.w3.org/2002/09 [from AllanJ] 17:17:09 -kford 17:17:29 zakim, open item 5 17:17:29 agendum 5. "HTML A11Y bugs relating to UA from Michael Cooper - http://lists.w3.org/Archives/Public/w3c-wai-ua/2010JulSep/0061.html" taken up [from AllanJ] 17:18:17 zakim, bring back kford! 17:18:17 I don't understand 'bring back kford!', Jan 17:20:18 my phone seems dead. 17:20:48 phoning in again. odd. 17:21:26 phone system is acting weird. 17:21:55 +kford 17:23:43 kf: a11y taskforce found 6 bugs that UAWG needs to adopt 17:24:10 ... need to review bugs, history, and if we care about them and then adopt them. 17:24:32 http://www.w3.org/Bugs/Public/buglist.cgi?bug_id=8647,8648,8666,8682,8743,8751 17:24:34 http://www.w3.org/Bugs/Public/buglist.cgi?bug_id=8647,8648,8666,8682,8743,8751 17:27:03 KP: question about HTML5 resolution of bug (work, won't) 17:28:03 kf: who wants to take these up, if we take them up, it is not an insignificant amount of work 17:29:56 ja: response on 8751 http://lists.w3.org/Archives/Public/w3c-wai-ua/2010JulSep/0067.html 17:31:01 js: does our SC on blinking in 4.7 impact this. 17:31:26 ... might have a chance in changing html5 17:32:29 ja: question - do we want to change html5 or are they things we need to add to uaag 17:32:56 js: should add to our spec. then also html5 17:33:29 gl: html has lots of inaccessible stuff, the accessibility is fixed in WCAG and UAAG 17:35:14 Or to rephrase that, HTML allows creation of inaccessible content, which we try to address in WCAG and UAAG. 17:35:29 discussion of 8648, 8666, and 8682 17:36:12 kf: need 1 person to understand bugs, what does html5 say, etc. and make presentation to the group. 17:37:10 Bug 8647 - Define tab order for IFrame: I agree that this would be useful, because the author can prescribe tab order within a frame or frameless document, but essentially cannot for the entire document as they have no way to control or even hint how it works on a page that includes iframes. However, unlike some accessibility problems with HTML5, this one could be addressed as future... 17:37:12 ...enhancement to HTML5 attributes, rather than needing to be in from the beginning. 17:39:58 ja: action Jallan review bugs listed in > http://www.w3.org/Bugs/Public/buglist.cgi?bug_id=8647,8648,8666,8682,8743,8751 17:41:07 kf: group bugs into 1 - html off base must be fixed, 2 - this is a uaag issue, fix now, 3 - fix later 17:41:09 I think that we can postpone any concerns (like 8647) that don't absolutely need to be fixed in the first incarnation of HTML5 because they can be fixed later. 17:41:39 action Jallan review bugs listed in > http://www.w3.org/Bugs/Public/buglist.cgi?bug_id=8647,8648,8666,8682,8743,8751 17:41:39 Created ACTION-440 - Review bugs listed in > http://www.w3.org/Bugs/Public/buglist.cgi?bug_id=8647,8648,8666,8682,8743,8751 [on Jim Allan - due 2010-09-09]. 17:42:51 sh: agree with the proposed resolutions 17:43:26 zakim, close item 5 17:43:26 agendum 5, HTML A11Y bugs relating to UA from Michael Cooper - http://lists.w3.org/Archives/Public/w3c-wai-ua/2010JulSep/0061.html, closed 17:43:29 I see 3 items remaining on the agenda; the next one is 17:43:30 2. Writers Meeting Survey#3 focus on questions 3-7 - http://www.w3.org/2002/09 [from AllanJ] 17:43:55 zakim, open item 6 17:43:55 agendum 6. "Select a date for a Face to Face meeting survey - http://www.w3.org/2002/09/wbs/36791/UAWG20100824/" taken up [from AllanJ] 17:44:08 http://www.w3.org/2002/09/wbs/36791/UAWG20100824/results 17:45:01 -JanRichards 17:48:53 discussion for video meeting 17:49:12 js: 9 &10 17:49:22 kp +1 17:49:32 ja: +1 17:51:03 sh +1 (could participate for 3 or 4 hours) 17:51:37 discussion of start time 17:52:14 proposed 7 pacific, 9 central, 10 eastern, 3 gmt 17:54:05 Resolved: video telecon Nov 9-10 starting 7 pacific, 2 gmt 17:54:54 Resolution: video telecon Nov 9-10 starting 7 pacific, 2 gmt 17:55:27 zakim, close item 6 17:55:27 agendum 6, Select a date for a Face to Face meeting survey - http://www.w3.org/2002/09/wbs/36791/UAWG20100824/, closed 17:55:30 I see 2 items remaining on the agenda; the next one is 17:55:31 2. Writers Meeting Survey#3 focus on questions 3-7 - http://www.w3.org/2002/09 [from AllanJ] 17:57:00 zakim, open item 3 17:57:02 agendum 3. "Writers Meeting Survey#4 - http://www.w3.org/2002/09/wbs/36791/20100802-4/" taken up [from AllanJ] 17:58:28 change url http://www.w3.org/2002/09/wbs/36791/20100802-3/results 17:58:50 kf: start with q3 http://www.w3.org/2002/09/wbs/36791/20100802-3/results#xq3 17:59:18 Current wording: 17:59:19 2.1.3 Accessible Alternative: If a component of the user agent user interface cannot be exposed through the platform accessibility architecture, then provide an equivalent alternative that is exposed through the platform accessibility architecture. (Level A) 17:59:21 * Intent of Success Criterion 2.1.3: 17:59:22 Users need to be able to carry out all tasks provided by the user agent. The purpose of this success criterion is to ensure that when circumstances do not allow direct accessibility to some items in the user agent, there is an accessible option that will let them complete their task. 17:59:24 * Examples of Success Criterion 2.1.3 : 17:59:25 o The user agent provides a single, complex control for 3-dimensional manipulation of a virtual object. This custom control cannot be represented in the platform accessibility architecture, so the user agent provides the user the option to achieve the same functionality through an alternate user interface, such as a panel with several basic controls that adjust the yar, spin, and... 17:59:28 ...roll independently. 18:02:21 gl: need to mention API and platform accessibility architecture 18:03:25 kf: the sc says if component can't be exposed, get the user an equivalent. 18:03:51 gl: yes, then intent throws in 'direct accessibility', needs to be replaced 18:04:13 The upshot is the Intent says "direct accessibility" where it should say something like "support for assistive technology using a platform accessibility architecture". 18:04:30 kf: perhaps say 'direct accessibility through the platform accessibility architecture' 18:05:21 Thus "Users need to be able to carry out all tasks provided by the user agent. The purpose of this success criterion is to ensure that when a component does not support assistive technlogy via a platform accessibility architecture, there is an accessible component that does." 18:05:46 "Users who rely on assistive technology need to be able to carry out all tasks provided by the user agent, just like everyone else. When a particular user interface component cannot support for the platform accessibiltiy architecture, and thus can't be made compatible with assistive technology, the user agent should let the user achieve the same goal using another component that IS fully... 18:05:48 ...accessible." 18:07:38 action: jeanne to update intent for 2.1.3 to be "Users who rely on assistive technology need to be able to carry out all tasks provided by the user agent, just like everyone else. When a particular user interface component cannot support for the platform accessibiltiy architecture, and thus can't be made compatible with assistive technology, the user agent should let the user achieve the... 18:07:38 Created ACTION-441 - Update intent for 2.1.3 to be "Users who rely on assistive technology need to be able to carry out all tasks provided by the user agent, just like everyone else. When a particular user interface component cannot support for the platform accessibiltiy architecture, and thus can't be made compatible with assistive technology, the user agent should let the user achieve the... [on Jeanne Spellman - due 2010-09-09]. 18:07:40 ...same goal using another component that IS fully accessible." 18:09:25 topic # Proposal for 2.1.4 Programmatic Availability of DOMs http://www.w3.org/2002/09/wbs/36791/20100802-3/results#xq4 18:09:28 Current wording: 18:09:29 2.1.4 Programmatic Availability of DOMs: If the user agent implements one or more DOMs, they must be made programmatically available to assistive technologies. (Level A) 18:09:31 * Intent of Success Criterion 2.1.4: 18:09:32 User agents (and other applications) and assistive technologies use a combination of DOMs, accessibility APIs, native platform APIs, and hard-coded heuristics to provide an accessible user interface and accessible content (http://accessibility.linuxfoundation.org/a11yspecs/atspi/adoc/a11y-dom-apis.html). It is the user agents responsibility to expose all relevant content to the... 18:09:34 ...platform accessibility api. Alternatively, the user agent must respond to requests for information from APIs. 18:09:35 * Examples of Success Criterion 2.1.4 : 18:09:37 o In user agents today, an author may inject content into a web page using CSS (generated content). This content is written to the screen and the CSS DOM. The user agent does not expose this generated content from the CSS-DOM (as per CSS recommendation) to the platform accessibility API or to the HTML-DOM. This generated content is non-existent to an assistive technology user. The... 18:09:40 ...user agent should expose all information from all DOMs to the platform accessibility API. 18:09:42 o A web page is a compound document containing HTML, MathML, and SVG. Each has a separate DOM. As the user moves through the document, they are moving through multiple DOMs. The transition between DOMs is seamless and transparent to the user and their assistive technology. All of the content is read and all of the interaction is available from the keyboard regardless of the... 18:09:47 ...underlying source code or the respective DOM. 18:11:19 kf: defer till later 18:11:37 topic: Proposal for 2.1.5 Write Access http://www.w3.org/2002/09/wbs/36791/20100802-3/results#xq5 18:14:52 action: jeanne to replace example 1 in intent for 2.1.5 to be "When the user says the phrase 'Volume 35%' their speech input utility can programmatically set the value of the volume slider to 35%, rather than having to use trial and error by simulating mouse clicks or arrow presses to try to find the 35% point." change 'programatic' in the intent to be 'programmatic' 18:14:52 Created ACTION-442 - Replace example 1 in intent for 2.1.5 to be "When the user says the phrase 'Volume 35%' their speech input utility can programmatically set the value of the volume slider to 35%, rather than having to use trial and error by simulating mouse clicks or arrow presses to try to find the 35% point." change 'programatic' in the intent to be 'programmatic' [on Jeanne Spellman - due 2010-09-09]. 18:16:31 rrsagent, make minutes 18:16:31 I have made the request to generate http://www.w3.org/2010/09/02-ua-minutes.html jeanne 18:18:11 Tom activates a macro that sets the value of a tri-state check boxes to "mixed". Even though the control would normally need to be cycled through its states of “on”, “off”, and “mixed”, the macro utility to set the control directly to the desired state. 18:20:10 Francois directs his third-party macro utility set the value of a tri-state check boxes to "mixed". Even though the control would normally need to be cycled through its states of “on”, “off”, and “mixed”, the macro utility can set the control directly to the desired state. 18:20:29 Francois directs his third-party macro utility to set the value of a tri-state check boxes to "mixed". Even though the control would normally need to be cycled through its states of “on”, “off”, and “mixed”, the macro utility can set the control directly to the desired state. 18:20:53 Francois directs his third-party macro utility to set the value of a tri-state check box to "mixed". Even though the control would normally need to be cycled through its states of “on”, “off”, and “mixed”, the macro utility can set the control directly to the desired state. 18:22:04 action: jeanne to changes example 2 in 2.1.5 to be "Francois directs his third-party macro utility to set the value of a tri-state check box to "mixed". Even though the control would normally need to be cycled through its states of “on”, “off”, and “mixed”, the macro utility can set the control directly to the desired state." 18:22:04 Created ACTION-443 - Changes example 2 in 2.1.5 to be "Francois directs his third-party macro utility to set the value of a tri-state check box to "mixed". Even though the control would normally need to be cycled through its states of “on”, “off”, and “mixed”, the macro utility can set the control directly to the desired state." [on Jeanne Spellman - due 2010-09-09]. 18:22:45 topic: Proposal for 2.1.6 Properties http://www.w3.org/2002/09/wbs/36791/20100802-3/results#xq6 18:23:24 # intent of Success Criterion 2.1.6: These properties are all used by assistive technology to allow provide alternative means for the user to view or navigate the content, or to accurately create a view of the user interface and rendered content. # Examples of Success Criterion 2.1.61: * Kiara loads a new version of a popular web browser for the first time. She puts her screen reader... 18:23:26 ...into an "explore mode" that lets her review what is appearing on the screen. Her screen reader uses the bounding rectangle of each element to tell her that items from the menu bar all appear on the same horizontal line, which is below the window's title bar. * Kiara is using a screen reader at a telephone call center. The Web application displays caller names in different colors... 18:23:27 ...depending on their banking status. Kiara needs to know this information to appropriately respond to each customer immediately, without taking the time to look up their status through other means. * Max uses a screen magnifier that only shows him a small amount of the screen at one time. He gives it commands to pan through different portions of a Web page, but then can give it... 18:23:30 ...additional commands to quickly pan back to positions of interest, such as the text matched by the recent Search operation, text that he previously selected by dragging the mouse, or the text caret, rather than having to manually pan through the document searching for them. 18:26:04 These properties are used by assistive technology to create alternative views of the user agent user interface and rendered content as well as providing alternative means the user to interact with these items. 18:27:08 action: jeanne to change 1 sentence of intent of 2.1.6 to be "These properties are used by assistive technology to create alternative views of the user agent user interface and rendered content as well as providing alternative means for the user to interact with these items." 18:27:08 Created ACTION-444 - Change 1 sentence of intent of 2.1.6 to be "These properties are used by assistive technology to create alternative views of the user agent user interface and rendered content as well as providing alternative means for the user to interact with these items." [on Jeanne Spellman - due 2010-09-09]. 18:27:38 topic: q4 Proposal for 2.1.7 Timely Communication http://www.w3.org/2002/09/wbs/36791/20100802-3/results#xq7 18:27:53 kf: 4 accepts, 18:28:40 ... need to review personas http://www.aegis-project.eu/index.php?option=com_content&view=article&id=63&Itemid=53 18:28:56 zakim, agenda? 18:28:56 I see 2 items remaining on the agenda: 18:28:58 2. Writers Meeting Survey#3 focus on questions 3-7 - http://www.w3.org/2002/09 [from AllanJ] 18:29:01 3. Writers Meeting Survey#4 - http://www.w3.org/2002/09/wbs/36791/20100802-4/ [from AllanJ] 18:29:57 action: GregLowney to redraft proposal for 2.1.5 Write Access Intent, Examples and Related Resources. from http://www.w3.org/2002/09/wbs/36791/20100802-3/results#xq5 18:29:57 Sorry, couldn't find user - GregLowney 18:30:09 action: Greg to redraft proposal for 2.1.5 Write Access Intent, Examples and Related Resources. from http://www.w3.org/2002/09/wbs/36791/20100802-3/results#xq5 18:30:09 Created ACTION-445 - Redraft proposal for 2.1.5 Write Access Intent, Examples and Related Resources. from http://www.w3.org/2002/09/wbs/36791/20100802-3/results#xq5 [on Greg Lowney - due 2010-09-09]. 18:30:40 rrsagent, make minutes 18:30:40 I have made the request to generate http://www.w3.org/2010/09/02-ua-minutes.html AllanJ 18:30:50 rrsagent, set logs public 18:30:51 -Jeanne 18:30:52 -Kim 18:30:53 -Greg 18:30:55 -sharper 18:36:26 -AllanJ 18:36:27 WAI_UAWG()1:00PM has ended 18:36:29 Attendees were kford, AllanJ, Greg, JanRichards, Jeanne, sharper, Kim 18:36:51 zakim, leave 18:36:51 Zakim has left #ua 18:37:00 rrsagent, make minutes 18:37:00 I have made the request to generate http://www.w3.org/2010/09/02-ua-minutes.html AllanJ 18:37:20 chair: KFord 18:37:22 rrsagent, make minutes 18:37:22 I have made the request to generate http://www.w3.org/2010/09/02-ua-minutes.html AllanJ 18:55:22 rrsagent, please part 18:55:22 I see 6 open action items saved in http://www.w3.org/2010/09/02-ua-actions.rdf : 18:55:22 ACTION: jeanne to update intent for 2.1.3 to be "Users who rely on assistive technology need to be able to carry out all tasks provided by the user agent, just like everyone else. When a particular user interface component cannot support for the platform accessibiltiy architecture, and thus can't be made compatible with assistive technology, the user agent should let the user achieve the... [1] 18:55:22 recorded in http://www.w3.org/2010/09/02-ua-irc#T18-07-38 18:55:22 ACTION: jeanne to replace example 1 in intent for 2.1.5 to be "When the user says the phrase 'Volume 35%' their speech input utility can programmatically set the value of the volume slider to 35%, rather than having to use trial and error by simulating mouse clicks or arrow presses to try to find the 35% point." change 'programatic' in the intent to be 'programmatic' [2] 18:55:22 recorded in http://www.w3.org/2010/09/02-ua-irc#T18-14-52 18:55:22 ACTION: jeanne to changes example 2 in 2.1.5 to be "Francois directs his third-party macro utility to set the value of a tri-state check box to "mixed". Even though the control would normally need to be cycled through its states of “on”, “off”, and “mixed”, the macro utility can set the control directly to the desired state." [3] 18:55:22 recorded in http://www.w3.org/2010/09/02-ua-irc#T18-22-04 18:55:22 ACTION: jeanne to change 1 sentence of intent of 2.1.6 to be "These properties are used by assistive technology to create alternative views of the user agent user interface and rendered content as well as providing alternative means for the user to interact with these items." [4] 18:55:22 recorded in http://www.w3.org/2010/09/02-ua-irc#T18-27-08 18:55:22 ACTION: GregLowney to redraft proposal for 2.1.5 Write Access Intent, Examples and Related Resources. from http://www.w3.org/2002/09/wbs/36791/20100802-3/results#xq5 [5] 18:55:22 recorded in http://www.w3.org/2010/09/02-ua-irc#T18-29-57 18:55:22 ACTION: Greg to redraft proposal for 2.1.5 Write Access Intent, Examples and Related Resources. from http://www.w3.org/2002/09/wbs/36791/20100802-3/results#xq5 [6] 18:55:22 recorded in http://www.w3.org/2010/09/02-ua-irc#T18-30-09