- From: David Todd <dltodd@us.ibm.com>
- Date: Fri, 28 Mar 2014 10:54:19 -0400
- To: public-mobile-a11y-tf@w3.org
- Message-ID: <OF7B0E0F94.38F04FD7-ON85257CA9.00519A1E-85257CA9.0051E0E0@us.ibm.com>
Minutes: http://www.w3.org/2014/03/28-mobile-a11y-minutes.html W3C - DRAFT - Mobile Accessibility Task Force Teleconference 28 Mar 2014 Agenda See also: IRC log Attendees Present Kim_Patch, Kathy_Wahlbin, kathleen, +1.720.663.aaaa, Jon_Avila, Alan_Smith, DavidTodd, wuwei, Jeanne, Jan Regrets Chair Kimberly_Patch Scribe DavidTodd Contents Topics 1. Update from WCAG 2.0 meeting at CSUN regarding technique development Summary of Action Items <trackbot> Date: 28 March 2014 <AlanSmith> Have my other call to be on so I'm double listening for a while. Update from WCAG 2.0 meeting at CSUN regarding technique development Kathy & Jeanne at CSUN Kathy reporting on WCAG meeting @ CSUN. Kathy: One topic was how to write to write techs. for WCAG. <Kathy> https://www.w3.org/WAI/GL/wiki/Writing_WCAG_Techniques_-_Notes Kathy: There is a wiki page on how to write techs. ... recommend we read "how to". <Kathy> https://www.w3.org/WAI/GL/wiki/Technique_Template Kathy: There is a template for writing techs. ... recommends reviewing techs. template. ... easier to use wiki for writing techs. Kim: How to stay coordinated with other groups? <AlanSmith> I've book marked them and will look at them Kathy: Create a work plan to document what we are going to do. ... 2 things are underway (gap analysis and BBC review). ... When finished reviewing techniques send a note to the group so we can start reviewing as a group. ... There are number of ways to present mobile guidance in the techniques. Kim: 2 things that need to be done. Common failures and last part of general techniques. John will do 1 - 20 of common failures. Kim & Kathy: Keep in mind both native and hybrid apps when reviewing techniques. Kathleen: Silverlight not supported on mobile. <Kathy> Here are the assignments <Kathy> Jonathan Avila Common Failures: F52-F89 <Kathy> Kathleen Anderson CSS Techniques: C23-C30 <Kathy> David Todd General Techniques: G101-G150 <Kathy> Kathleen Wahlbin Common Failures: F1-F50 <Kathy> Kimberly Patch FLASH: FLASH 1-36 <Kathy> Alan Smith General Techniques: G151-G202 Jon: Should we add notes about html specific topics? Kim: yes Kathy: Ways we can present mobile accessibility techniques and changes to understanding documents so people get the information they need. <Jan_> http://www.w3.org/TR/WCAG20-TECHS/ Jan: Makes sense to have a mobile techs. page that pulls everything in one place. Kathy: How to deal with the different technologies? <jon_avila> There may also be some general mobile technqiues Jeanne: There are disadvantages to having separate techniques (e.g., maintenance) Kim: Thinks a separate document would be good. Kathy: What do we think from a developer perspective? <jon_avila> Right, people may be using responsive design <Zakim> jeanne, you wanted to say that a separate mobile techniques section would solve the problem of duplicating work in other groups Jan: Support the notion that WCAG is the appropriate guideline. kathleen: would like to work with one document rather that two. <Jan_> Jan: The mobile native technaiwues should be their own sections of http://www.w3.org/TR/WCAG20-TECHS/ <Jan_> Jan: Would like to see a "Mobile HTML" section of http://www.w3.org/TR/WCAG20-TECHS/ <Jan_> Jan: Then there could be cross-references from "Desktop HTML" to matching "Mobile HTML" section and vice versa Jon: General & HTML guidelines that work in mobile we should reference. <Jan_> Jon: People will be using "responsive web design" <jon_avila> The reason I was saying something might not apply is because it's not accessibility supported on mobile. Kathleen: Add additional sections to existing techs? <jon_avila> survey? <Jan_> Jan: Since what is accessibility supported changes over time, notes to that effect should be "soft" Kathy: yes, or could incorporate other models. Kim: Create a wiki page with different models. Kathy: schedule people to present what they have done. ... Decide on a direction in the next couple of weeks. ... Get feedback in a controlled manner. Kim: Next time we will have list of models and then walk through completed work. Kathy: Think about the techs. that address keyboard. <Kathy> https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Keyboard_Access/Modality_Independent_Control/IndieUI There is a summary page of keyboard issues from WCAG meeting. Summary of Action Items [End of minutes] Minutes formatted by David Booth's scribe.perl version 1.138 (CVS log) $Date: 2014-03-28 14:48:38 $ Scribe.perl diagnostic output [Delete this section before finalizing the minutes.] This is scribe.perl Revision: 1.138 of Date: 2013-04-25 13:59:11 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: DavidTodd Inferring Scribes: DavidTodd Default Present: Kim_Patch, Kathy_Wahlbin, kathleen, +1.720.663.aaaa, Jon_Avila, Alan_Smith, DavidTodd, wuwei, Jeanne, Jan Present: Kim_Patch Kathy_Wahlbin kathleen +1.720.663.aaaa Jon_Avila Alan_Smith DavidTodd wuwei Jeanne Jan Agenda: http://lists.w3.org/Archives/Public/public-mobile-a11y-tf/2014Mar/0018.html Found Date: 28 Mar 2014 Guessing minutes URL: http://www.w3.org/2014/03/28-mobile-a11y-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. [End of scribe.perl diagnostic output] David Todd 720-663-2815 IBM Human Ability and Accessibility Center
Attachments
- image/gif attachment: 84143607.gif
Received on Friday, 28 March 2014 14:54:52 UTC