- From: Shawn Henry <shawn@w3.org>
- Date: Wed, 27 May 2009 16:07:09 -0500
- To: "EOWG (E-mail)" <w3c-wai-eo@w3.org>
EOWG, Per our discussion at last week's EOWG teleconference, please review Yeliz's changes below. The updated draft document is now online at: http://www.w3.org/WAI/mobile/experiences-new Please send any comments (or request additional time for review) *by Thursday 18 May*. [Yeliz, if no comments come in, please go ahead and incorporate your changes in the table version and I'll update the published version of each. Thanks!] Best, ~Shawn -------- Original Message -------- Subject: Re: EOWG: For 22 May discussion: WCAG and MWBP comments Resent-Date: Sat, 23 May 2009 09:12:47 +0000 Resent-From: w3c-wai-eo@w3.org Date: Sat, 23 May 2009 12:11:54 +0300 From: Yeliz Yesilada <yesilady@cs.man.ac.uk> To: EOWG (E-mail) <w3c-wai-eo@w3.org> CC: Alan Chuter <achuter@technosite.es>, Andi Snow-Weaver <andisnow@us.ibm.com> References: <4A161D58.1080809@w3.org> <4A16526D.4040407@technosite.es> Hi Alan, Andi, Thanks so much for your comments. To address the raised points below and also Anna's comment, I have updated and attached a new version of this document. My changes are as follows: 1. Added a new sentence "For a comprehensive comparison, see Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG)" to the second parag. in the introduction to address Anna's comment (<http://lists.w3.org/Archives/ Public/w3c-wai-eo/2009AprJun/0082.html>); 2. Combined "Embedded non-text objects (images, sound, video) with no text alternative" & "Important information in non-text content (images, multimedia, CSS effects)" into a single item called "Non- text objects (images, sound, video) with no text alternative". 3. "Free-text entry (for example, alphabetical characters allowed in numeric fields)" changed the title to "Text entry" and also updated the references so now it doesn't refer to WCAG 1.0 CP 10.4 and MWBP AVOID_FREE_TEXT and it refers to WCAG 2.0 SC 3.3, I have also updated the text to make it more clear; 4. Split "Scripting required to operate or generate content" into two: i) "Scripting required to operate content" and kept it under "operable", also updated the WCAG 2.0 references to "# Conformance Requirement 4: Only Accessibility-Supported Ways of Using Technologies and # Conformance Requirement 5: Non-Interference" based on the table here: <http://www.w3.org/WAI/WCAG20/from10/comparison/> ii) "Scripting required to generate content" and moved to "Robust" and also added a reference to "Understanding Guideline 4.1". Please let me know if you are happy with these changes and I will also update the tabular version to reflect these changes.
Received on Wednesday, 27 May 2009 21:07:13 UTC