- From: Jim Allan <jimallan@tsbvi.edu>
- Date: Thu, 16 Apr 2009 13:51:36 -0500
- To: <w3c-wai-ua@w3.org>
>From http://www.w3.org/2009/04/16-ua-minutes.html - DRAFT - User Agent Accessibility Guidelines Working Group Teleconference 16 Apr 2009 Summary of Action Items [NEW] ACTION: Jallan to write CG about review of UAAG20 [recorded in http://www.w3.org/2009/04/16-ua-minutes.html#action01] [NEW] ACTION: JS to update the glossary with the definition of input configuration [recorded in http://www.w3.org/2009/04/16-ua-minutes.html#action02] [NEW] ACTION: sharper to investigate / review interactive and enabled for contradictions. [recorded in http://www.w3.org/2009/04/16-ua-minutes.html#action03] Attendees Present Harper_Simon, Ford_Kelly, Allan_Jim, Spellman_Jeanne, Patch_Kim, Richards_Jan, Swan_Henny Regrets Hakkinen_Mark Chair Allan_James, Ford_Kelly Scribe Harper_Simon Contents * Topics 1. Logistics (Regrets, agenda requests, comments)? 2. Update scribing schedule 3. New Member 4. Generating UAAG comments 5. Survey results http://www.w3.org/2002/09/wbs/36791/20090331/ 6. WAI-ARIA last call review http://www.w3.org/TR/wai-aria/ * Summary of Action Items <trackbot> Date: 16 April 2009 <scribe> scribe: Harper_Simon <scribe> ScribeNick: sharper <kford> Hey Simon. <scribe> meeting: User Agent Working Group Telecon - 16 April 2009 Logistics (Regrets, agenda requests, comments)? <jeanne> http://www.w3.org/2002/09/wbs/36791/20090414/ Update scribing schedule New Member JA: Welcome Kim Patch as a new Member KP: Introductions and brief background All: Introductions and professional backgrounds Generating UAAG comments JA: New working draft went out for comments http://www.w3.org/WAI/UA/2009/UAAG20-20090121-ED/ ... No Comments to date HS: Blogged and Twittered already <Henny> http://www.iheni.com/uaag-needs-you/ JR: Will announce at Authoring tools event SH: Will Announce at the W4A Conference Next Week <AllanJ> ACTION: Jallan to write CG about review of UAAG20 [recorded in http://www.w3.org/2009/04/16-ua-minutes.html#action01] <trackbot> Created ACTION-179 - Write CG about review of UAAG20 [on Jim Allan - due 2009-04-23]. JA: If HS related to WASP - would anyone be interested there? ... Anymore thoughts on this? ... to KF will MicroSoft be commenting? KF: yes HS: Likewise Opera - many comments - but more questions. Survey results http://www.w3.org/2002/09/wbs/36791/20090331/ <AllanJ> http://www.w3.org/2002/09/wbs/36791/20090415/ <AllanJ> http://www.w3.org/2002/09/wbs/36791/20090331/results Focus on input configuration Accept 2 / 1 More / 2 Neutral MH: "Input configurations may be affected by author-specified bindings (e.g., through the accesskey attribute of HTML 4 [HTML4])." Is this a statement of what has happened, and should continue, OR should we say that such is not a good thing? "Input configurations should not be affected by author-specified bindings (e.g., through the accesskey attribute of HTML 4 [HTML4]) without first notifying the user." JR: is in glossary, is a statement of fact that authors can set keyboard bindings JA: true - any more thoughts? KF: I agree with JR ... talk about this in some places JA: Addressed elsewhere ... Still missing the negotiating keybindings ... Should we also mention JavaScript - or leave it as there may be many otherways to do this KF: as it is, this is one illustration, could be many more. KF + JA: so leave it this way RESOLUTION: as The set of "bindings" between user agent functionalities and user interface input mechanisms (e.g., menus, buttons, keyboard keys, and voice commands). The default input configuration is the set of bindings the user finds after installation of the software. Input configurations may be affected by author-specified bindings (e.g., through the accesskey attribute of HTML 4 [HTML4]). <AllanJ> http://www.w3.org/2002/09/wbs/36791/20090415/results <jeanne> ACTION: JS to update the glossary with the definition of input configuration [recorded in http://www.w3.org/2009/04/16-ua-minutes.html#action02] <trackbot> Created ACTION-180 - Update the glossary with the definition of input configuration [on Jeanne Spellman - due 2009-04-23]. JA: Proposal - interactive element, non-interactive element 5 Accept / 1 More JR: (More) Comment - leaves out non-interactive JA: (Accept) Comment - should programmatic enablement be 'scripting'? <AllanJ> SH: if we use scripting, are we confining to a specific language <JR> Elements that by specification or programming have associated behaviors .... <kford> +1 to JR. SH: That sounds good +1 to JR <AllanJ> +1 <Henny> +1 <jeanne> +1 <KimPatch> +1 JA: Junk the 'non-interactive element' part of the title ... any Objections? <kford> +1 to removal JS: Good - clarifys +1 to removal RESOLUTION: remove on-interactive element to make 'interactive element' NOT interactive element, non-interactive element RESOLUTION: to -- Elements that by specification or programming have associated behaviours to be executed or carried out as a result of user or programmatic interaction. (e.g., in HTML 4 [HTML4] the interactive elements include: links, image maps, form elements, elements with a value for the longdesc attribute, and elements with event handlers explicitly associated with them). <scribe> ACTION: sharper to investigate / review interactive and enabled for contradictions. [recorded in http://www.w3.org/2009/04/16-ua-minutes.html#action03] <trackbot> Created ACTION-181 - Investigate / review interactive and enabled for contradictions. [on Simon Harper - due 2009-04-23]. WAI-ARIA last call review http://www.w3.org/TR/wai-aria/ <AllanJ> http://lists.w3.org/Archives/Public/w3c-wai-ua/2009AprJun/0020.html KP: many standards - will it jump to individual characters or as a word? Big mix of this - especially with speech I/F KF: dragon doesn't just use keyboard emulation, uses active accessibility to. <AllanJ> s/to. /too KF: basic c&c can get to the elements, then keyboard as final option. ... concern that ARIA doesn't create a false sense of how easy it will be to use. More complicated structures induce and expectation of certain characteristics - which may not be the case. ... hopefully we'll have web ARIA tools kits and add 'their' version of the tree - expected behaviour is 'key' and not getting this behaviour may mean we make more barriers <AllanJ> KF: AT users have higher level of knowledge/expectations of keyboard interaction with UI elements than ARIA can/may provide and may confuse users All: general ARIA conversation. JA: Comments on the issue at http://lists.w3.org/Archives/Public/w3c-wai-ua/2009AprJun/0020.html should be more formal JS: will find correct way to do this - just need a more formal version - will answer JA tomorrow - deadline for comments tomorrow. KF: these will be our (the groups) comments on ARIA - anything else members need to speak up ASAP RESOLUTION: These are our (the groups) comments on ARIA - and will be sent formally ASAP <AllanJ> SH: two items: web applications, and personalization and UA implementation JA: Items for next week - We have been doing yeoman's work on the glossary. While the glossary > is important, it is time (beginning next week) to review the open action > items related to video and alternative content. JS: UBIWeb Notes mentioned in WAI group - team would like us to comment so they can hear them. <AllanJ> http://www.w3.org/TR/2009/NOTE-UWA-personalization-roadmap-20090409/ <AllanJ> mobile best practices - http://www.w3.org/TR/mobile-bp/ <AllanJ> Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG) http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwb p-wcag- 20090218/ <AllanJ> http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwb p-wcag-20090218/ Jim Allan, Accessibility Coordinator & Webmaster Texas School for the Blind and Visually Impaired 1100 W. 45th St., Austin, Texas 78756 voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/ "We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Thursday, 16 April 2009 18:54:35 UTC