- From: Jeanne Spellman <jeanne@w3.org>
- Date: Thu, 03 Apr 2014 11:35:04 -0400
- To: UAWG <w3c-wai-ua@w3.org>
These minutes were not sent originally. I am sending them late so that they will be included in the archives and be searchable. http://www.w3.org/2014/03/13-ua-minutes.html [1]W3C [1] http://www.w3.org/ - DRAFT - User Agent Accessibility Guidelines Working Group Teleconference 13 Mar 2014 See also: [2]IRC log [2] http://www.w3.org/2014/03/13-ua-irc Attendees Present Regrets Jim Chair SV_MEETING_CHAIR Scribe jeanne Contents * [3]Topics 1. [4]Next meeting 2. [5]Math/science holidays 3. [6]Comment Responses 4. [7]review comments 5. [8]OP06 - Jan's proposal 6. [9]OP06 2.3.1 from Jan's Proposal * [10]Summary of Action Items __________________________________________________________ <trackbot> Date: 13 March 2014 <scribe> scribe: jeanne Next meeting Jeanne & Jim will be at CSUN. Kim will be on vacation, so only Greg, Jan and Kelly are around. <kford> sorry for my delay. <Greg> Tomorrow is Pi Day, but don't forget [11]http://www.moleday.org/ in October. [11] http://www.moleday.org/ Math/science holidays Comment Responses <kford> comments document: [12]http://www.w3.org/WAI/UA/2014/LCcomments.html [12] http://www.w3.org/WAI/UA/2014/LCcomments.html Jeanne updated the editors draft and LC comment spreadsheet with the actions from last week's meeting. <kford> regrests: Jim No meeting next week - 20 March 2014 review comments [13]http://lists.w3.org/Archives/Public/w3c-wai-ua/2014JanMar/0 046.html [13] http://lists.w3.org/Archives/Public/w3c-wai-ua/2014JanMar/0046.html OP06 - Jan's proposal [14]http://lists.w3.org/Archives/Public/w3c-wai-ua/2014JanMar/0 046.html [14] http://lists.w3.org/Archives/Public/w3c-wai-ua/2014JanMar/0046.html <kford> JS reading JR's proposal GL: This lowers the bar to be non-existent - it uses "may". JS: Is this a problem? A video would not use those, they would use "scenes". ... We should add scenes to the list of examples. <Greg> My preference would be "*should* include *recognized* headings, table captions...", but I can live with the proposed wording. <scribe> ACTION: Jeanne to update 1.9.1 to say: 1.9.1 Outline View: Users can view a navigable outline of the rendered content that allows focus to be moved to the corresponding element in the main viewport. (Level AA) [recorded in [15]http://www.w3.org/2014/03/13-ua-minutes.html#action01] - Note: The elements reflected in the outline view will depend on the web content technology and can include: headings, table captions, content sections, and scenes. <trackbot> Created ACTION-960 - Update 1.9.1 to say: 1.9.1 outline view: users can view a navigable outline of the rendered content that allows focus to be moved to the corresponding element in the main viewport. (level aa) [on Jeanne F Spellman - due 2014-03-20]. Resolution: Accept Jan's proposal for 1.9.1 with minor edits OP06 2.3.1 from Jan's Proposal JS: It's a big change from important elements to enabled elements. Since we are requiring direct navigation to each one, that's a LOT of keyboard shortcuts GL: That's the 'mouseless browsing" extension KP: but that works with links and not all enabled elements <Greg> We don't necessarily have a full implementation yet, one that goes to all enabled elements. Would not be that big a change for Mouseless Browsing to add that. <Greg> Kim says that it does support almost all enabled elements. KP: It should do anything you can click on. JS: I withdraw my objection. GL: So we have an implementation of this with enabled elements. KP: Mouseless browsing has been around for a long time with increasing coverage of "gaps". I haven't looked around in a long time. Jan's update: 2.3.1 Allow Direct Navigation to Enabled Elements: The user can move keyboard focus directly to any enabled elements in the rendered content. (Level AA) <Greg> Jeanne questioned move to "move keyboard focus to" on touchscreen devices, but we already require a virtual keyboard focus in those cases. GL: Link to the definition of keyboard focus which reminds them it is not just a physical keyboard. JS: There is a comment that says we are dated because we mention keyboard so much. KP: We have the note, modality independent controls. ... could we use that phrase? <Greg> UAAG20 makes it clear that keyboard isn't always physical keyboard, but that is spread out through several definitions and the Note at the beginning of Principle 2. JS: I think we should postpone this discussion until we address the comment about keyboard issue. <Greg> We could change term to something technology neutral, like "mechanism for discrete input", but Kim thinks Jan had argument against that. Summary of Action Items [NEW] ACTION: Jeanne to update 1.9.1 to say: 1.9.1 Outline View: Users can view a navigable outline of the rendered content that allows focus to be moved to the corresponding element in the main viewport. (Level AA) [recorded in [16]http://www.w3.org/2014/03/13-ua-minutes.html#action01]
Received on Thursday, 3 April 2014 15:35:06 UTC