W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > April to June 2008

Re: MWBP-WCAG doc suggested restyle

From: Yeliz Yesilada <yesilady@cs.man.ac.uk>
Date: Sun, 29 Jun 2008 21:28:39 +0100
Message-Id: <9698DC34-BF8D-47DD-A998-C18B08D68DCB@cs.man.ac.uk>
Cc: achuter@technosite.es, EOWG <w3c-wai-eo@w3.org>
To: Liam McGee <liam.mcgee@communis.co.uk>

I think this looks really good...

Yeliz.
On 27 Jun 2008, at 14:27, Liam McGee wrote:

> Hi all, folloowing discussion today, please see attached example.  
> Tested on IE6/7 and FF2, seems fine. Let me know if it's a go-er  
> and I'll ensure it works on everything else.
>
> Regards
>
> Liam
>
> -- 
> Liam McGee, Managing Director, Communis Ltd
> www.communis.co.uk      +44 (0)1373 836 476
> Skip to Page Contents
> Overview
> WCAG 2.0 and MWBP Together
> MWBP to WCAG 2.0
> MWBP to WCAG 1.0
> WCAG 2.0 to MWBP
> WCAG 1.0 to MWBP
>
>
> Mobile Web Best Practices (MWBP) and
> Web Content Accessibility Guidelines (WCAG)W3C Editor's Draft 24  
> June 2008This version:http://www.w3.org/2005/MWI/BPWG/Group/ 
> TaskForces/Accessibility/drafts/ED-mwbp-wcag-20080624/Latest  
> version:http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/ 
> Accessibility/drafts/latestPrevious version:http://www.w3.org/2005/ 
> MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwbp- 
> wcag-20080606 Editors:Alan Chuter (Fundación ONCE / Technosite)
> Copyright � 2008 W3C� (MIT, ERCIM, Keio), All Rights Reserved.  
> W3C liability, trademark and document use rules apply.
>
> Abstract
> This technical report describes the relationships, overlaps and  
> differences between the Web Content Accessibility Guidelines (WCAG)  
> and the Mobile Web Best Practices (MWBP). Introductory information  
> can be found in Web Content Accessibility and Mobile Web: Making a  
> Web Site Accessible Both for People with Disabilities and for  
> Mobile Devices.
>
> Status of This Document
> This section describes the status of this document at the time of  
> its publication. Other documents may supersede this document. A  
> list of current W3C publications and the latest revision of this  
> technical report can be found in the W3C technical reports index at  
> http://www.w3.org/TR/.
>
> This document was developed jointly by the Mobile Web Best  
> Practices Working Group and the Education & Outreach Working Group  
> (EOWG) of the Web Accessibility Initiative (WAI).
>
> Publication as a Working Draft does not imply endorsement by the  
> W3C Membership. This is a draft document and may be updated,  
> replaced or obsoleted by other documents at any time. It is  
> inappropriate to cite this document as other than work in progress.  
> If you wish to make comments regarding this document, please send  
> them to public-bpwg-comments@w3.org (with public archive) or wai-eo- 
> editors@w3.org (with public archive). All feedback is welcome.
>
> This document was produced by groups operating under the 5 February  
> 2004 W3C Patent Policy. W3C maintains a public list of any patent  
> disclosures made in connection with the deliverables of the Mobile  
> Web Best Practices Group and also maintains a public list of any  
> patent disclosures made in connection with the deliverables of the  
> Education and Outreach Working Group; those pages also include  
> instructions for disclosing a patent. An individual who has actual  
> knowledge of a patent which the individual believes contains  
> Essential Claim(s) must disclose the information in accordance with  
> section 6 of the W3C Patent Policy.
>
> Table of Contents
> How to Use This Document
> Scope
> Managing Overlapping Requirements
> Differences Between WCAG and MWBP
> Why No WCAG to MWBP Correspondence Table?
> Appendix A: References
> Appendix B: Glossary
> Appendix C: Acknowledgements
> How to Use This Document
> Before continuing with this document, please read the introductory  
> documents: Web Content Accessibility and Mobile Web: Making a Web  
> Site Accessible Both for People with Disabilities and for Mobile  
> Devices and Experiences Shared by People with Disabilities and by  
> People Using Mobile Devices.
>
> This technical report consists of a number of pages describing the  
> relationship between WCAG and MWBP. If you are interested in  
> complying with both WCAG 2.0 and MWBP 1.0 together and are not  
> familiar with either of them, then refer to WCAG 2.0 and MWBP 1.0  
> Together: Making content meet Web Content Accessibility Guidelines  
> 1.0 and Mobile Web Best Practices 1.0. If you have already complied  
> with one of these recommendations, then depending on which one,  
> continue with the following documents.
>
> If you have done MWBP 1.0 and are considering progressing to:
> WCAG 2.0, then read From MWBP 1.0 to WCAG 2.0: Making content that  
> meets Mobile Web Best Practices 1.0 also meet Web Content  
> Accessibility Guidelines 2.0
> WCAG 1.0, then read From MWBP 1.0 to WCAG 1.0: Making content that  
> meets Mobile Web Best Practices 1.0 also meet Web Content  
> Accessibility Guidelines 1.0
> If you have done WCAG 1.0 and considering progressing to MWBP 1.0,  
> then read From WCAG 2.0 to MWBP 1.0: Making content that meets Web  
> Content Accessibility Guidelines 2.0 also meet Mobile Web Best  
> Practices 1.0
> If you have done WCAG 2.0, and considering progressing to MWBP 1.0,  
> then read From WCAG 1.0 to MWBP 1.0: Making content that meets Web  
> Content Accessibility Guidelines 1.0 also meet Mobile Web Best  
> Practices 1.0
> Done Doing next Then read
> MWBP WCAG 2.0 From MWBP 1.0 to WCAG 2.0: Making content that meets  
> Mobile Web Best Practices 1.0 also meet Web Content Accessibility  
> Guidelines 2.0
> MWBP WCAG 1.0 From MWBP 1.0 to WCAG 1.0: Making content that meets  
> Mobile Web Best Practices 1.0 also meet Web Content Accessibility  
> Guidelines 1.0
> WCAG 1.0 MWBP From WCAG 1.0 to MWBP 1.0: Making content that meets  
> Web Content Accessibility Guidelines 1.0 also meet Mobile Web Best  
> Practices 1.0
> WCAG 2.0 MWBP From WCAG 2.0 to MWBP 1.0: Making content that meets  
> Web Content Accessibility Guidelines 2.0 also meet Mobile Web Best  
> Practices 1.0
> Scope
> This technical report is created as a supporting document to WCAG  
> and MWBP, and does not replace either of those. For further and  
> comprehensive information about how to make Web content accessible  
> to people with disabilities, please refer to the Web Content  
> Accessibility Guidelines. Similarly, for further and comprehensive  
> information about best Practices for delivering Web content to  
> mobile devices, please refer to the Mobile Web Best Practices.
>
> Managing Overlapping Requirements
> As explained in the document Experiences Shared by People with  
> Disabilities and by People Using Mobile Devices [Editors' Draft,  
> January 2008], certain features of Web content can cause barriers  
> to both people with disabilities (using desktop or laptop  
> computers) and people without disabilities who are using mobile  
> devices. Although W3C provides best practices and guidelines to  
> address such barriers, depending on the user group these barriers  
> are addressed in different documents. However, considering  
> overlapping requirements has some benefits which include:
>
> Unnecessary effort and cost is often expended in complying with  
> recommendations separately or consecutively. This document explains  
> the overlaps between the two recommendations, allowing for greater  
> efficiency.
> Content providers may decide not to adopt another recommendation  
> due to imagined cost. This document explains the overlaps and  
> synergies between the two recommendations, and the ways in which  
> once one recommendation is adopted, the other is less onerous.
> Specialists in the “Web accessibility” or “mobile Web”  
> fields may be unaware of the importance of the other and have  
> difficulty communicating. This document can spread awareness and  
> improve communication by helping specialists in different fields  
> understand that their concerns are often related and parallel. It  
> should help trainers teaching students already experienced in  
> another field using terminology and concepts they are familiar with  
> and without repeating material they already know.
> Vendors of evaluation tools may expend unnecessary effort and cost  
> developing test implementations that already exist for the other  
> recommendation. The information in this document allows them to  
> understand how implementations may be reused or easily adapted.
> Differences Between WCAG and MWBP
> Unlike the Web Content Accessibility Guidelines, the Mobile Web  
> Best Practices are not prioritised or assigned levels. MWBP relates  
> to checkpoints of all the WCAG 1.0 priorities (1, 2 and 3) and to  
> all the WCAG 2.0 level A, AA and AAA success criteria.
>
> Why No WCAG to MWBP Mapping Table?
> While there appears to be many similarities between many of the  
> WCAG provisions and those of the MWBPs, there are still many subtle  
> differences. A simple table would be misleading and lead to  
> duplication of work in some aspects and inadequate implementations  
> in others. Also the relationships are not symmetrical (SC x relates  
> to BP y, but it does not follow therefore that BP y relates to SC  
> x). For example, while both WCAG and MWBP require good colour  
> contrast, WCAG emphasises users' color perception while MWBP  
> focuses on the device characteristics (reduced color palette, poor  
> lighting). This means that complying with WCAG may meet the related  
> MWBP, but not the inverse.
>
> Appendix A: References
> For the latest version of any W3C specification please consult the  
> list of W3C Technical Reports.
>
> [WAI/Business] Developing a Web Accessibility Business Case for  
> Your Organization [WAI/Experiences] Experiences Shared by People  
> with Disabilities and by People Using Mobile Devices[WAI/Mobile]Web  
> Content Accessibility and Mobile Web: Making a Web Site Accessible  
> Both for People with Disabilities and for Mobile Devices[WAI/ 
> Resouces]WAI Resources page[MWBP1.0]Mobile Web Best Practices 1.0,  
> Rabin, J. and McCathieNevile, C., November 2006 (see http:// 
> www.w3.org/TR/mobile-bp/)[WCAG1.0]Web Content Accessibility  
> Guidelines 1.0, W. Chisholm, G. Vanderheiden and I. Jacobs, May  
> 1999 (see http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/) 
> [WCAG2.0]Web Content Accessibility Guidelines 2.0, B. Caldwell, M.  
> Cooper, L. Guarino Reid and G. Vanderheiden, May 2007 (see http:// 
> www.w3.org/TR/2007/WD-WCAG20-20070517/)Appendix B: Glossary
> Some common words are used in this document with specific meanings.  
> These are defined below.
>
> everything Concerning the effort required to meet a checkpoint or  
> best practice, this means that the other provisions do not cover  
> this aspect at all, and it is necessary to comply with these  
> checkpoints from scratch. As there is no coverage in the MWBPs, no  
> BPs are referenced, or vice versa. nothing Concerning the effort  
> required to meet a checkpoint or best practice, this means that  
> content already complies with this provision so no further effort  
> is necessary. partially In many cases there is no direct  
> correspondence between one provision and another. In some cases the  
> scope may be different, giving partial compliance. For example, the  
> NON-TEXT_ALTERNATIVES best practice covers images, but the scope of  
> the WCAG provisions is much wider. In these cases the word  
> “partially” is used. possibly In many cases there is no direct  
> correspondence between one provision and another. In some cases, it  
> may be necessary to make an extra effort or to consider a more  
> diverse range of user needs. For example, [COLOR_CONTRAST] is  
> intended to help mobile users with monochrome displays or in poor  
> lighting conditions. By also considering the needs of users with  
> color deficits (color blindness) the same BP makes content  
> accessible to more users and ensures compliance with success  
> criterion 1.4.3 “Contrast (Minimum)”. In these cases, the word  
> “possibly” is used. something Concerning the effort required to  
> meet a checkpoint or best practice, this means that more effort of  
> some kind is necessary to comply with the provision. What is  
> required depends on the individual checkpointor best practice. For  
> each there is a list of the provisions that provide partial  
> compliance or are in some way related. Appendix C: Acknowledgements
> The editor acknowledges the contributions of members of the WAI  
> Education & Outreach Working Group and the Mobile Web Best  
> Practices Working Group in compiling this document, in particular  
> Yeliz Yesilada (University of Manchester) and Charles  
> McCathieNevile (Opera Software).
>
> Document Information
> Version: W3C Editor's Draft $Date: 2008/06/24 14:58:21 $
> Editor: Alan Chuter. Developed by the Education and Outreach  
> Working Group (EOWG) and Mobile Web Best Practices Working Group  
> (MWBP).
>
> A Requirements/Analysis and changelog for Relationship Between MWBP  
> & WCAG and a record of updates and modifications to this document  
> are available separately.
>
> Copyright � 1994-2008 W3C� (MIT, ERCIM,Keio), All Rights  
> Reserved. W3C liability, trademark, document use and software  
> licensing rules apply. Your interactions with this site are in  
> accordance with our public and Member privacy statements.
>
Received on Sunday, 29 June 2008 20:29:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:55:57 UTC