Incomplete draft: This document is a draft and is not complete. Particularly, the section WCAG 2.0 and MWBP Together is only an outline; WCAG 1.0 to MWBP is only partly filled out. It is subject to major changes and is therefore not intended for implementation. It is provided for review and feedback only. Please send feedback to both email@example.com and firstname.lastname@example.org.
A Requirements/Analysis and changelog for Relationship Between MWBP & WCAG and a record of updates and modifications to this document are available separately.
This multi-page document describes the similarities and differences between the Web Content Accessibility Guidelines (WCAG) and the Mobile Web Best Practices (MWBP).
This document makes primary reference to Web Content Accessibility Guidelines (WCAG) 1.0 and the 11 December 2007 draft of WCAG 2.0 and Mobile Web Best Practices 1.0. New versions of these documents are expected to be produced during the life of this document. New versions of this document should be produced as soon as new versions of the referenced Recommendations are published and well understood.
Readers of this document are expected to be familiar with the creation of Web sites, and to have a general familiarity with the technologies involved, such as Web servers and HTTP. Readers are not expected to have a background in mobile-specific technologies. it is important to understand the other W3C Recommendations to which it refers (see Related Documents of Interest).
Our intention is to make it clear to all involved what the Best Practices are, and hence establish a common basis of understanding. As a result of wishing to be clear to those not already involved in the development of mobile friendly content, some of our statements may appear to be obvious or trivial to those with experience in this area.
The document is not targeted solely at developers; others, such as interaction and graphic designers are encouraged to read it.
Many readers of the document are likely to have a good knowledge of general Web accessibility but are concerned with the problems of persons with disabilities in the mobile context.
This document describes the relationships, overlaps and differences between MWBP and WCAG. This document does not create any further requirements beyond those defined in the MWBP and the WCAG.
Web accessibility for people with disabilities is beyond the scope of this document except where it especially affects mobile users. It is described in WCAG. The needs of users in the mobile Web context is beyond the scope of this document except where it especially affects users with disabilities. It is described in MWBP.
Before continuing with this document further you may wish to read the introductory documents that accompany it:
This overview introduces a multi-page document describing the relationship between WCAG and MWBP. There are five other sections (each a separate page) corresponding to the relationships between MWBP 1.0 and two versions of WCAG. Of the other five, you may prefer to concentrate on only one, either to address both accessibility or mobile-awareness together, or if you currently focus on one, the aspect towards which you are aiming:
Certain features of Web content cause barriers both for users of mobile devices and users with disabilities. However, the ways to overcome these barriers are dealt with in different documents, depending on the category of users who the document seeks to help. While reading this section it can be useful to compare the effects that content features have on different users. This is described in the separate document @@Experiences Shared by People with Disabilities and by People Using Mobile Devices [Editors' Draft, January 2008]
Many Web sites have already adopted the WCAG, which explains how to make Web content accessible to people with disabilities. In many countries compliance with WCAG is mandatory. The MWBP document specifies Best Practices for delivering Web content to mobile devices. The principal objective is to improve the user experience of the Web when accessed from such devices.
Increasingly, web content is designed to comply with one of these sets of guidelines or best practices. However, misunderstanding of their requirements and the assumptions about the user and device characteristics on which they are based, leads to less than optimal implementation. This document is intended to serve as an added justification or argument for aiming for compliance with either of the recommendations. The benefits include:
It may be useful for building the business case for adopting either WCAG or MWBP in a web site that already complies with one, or for adopting both together. For accessibility, the Web Accessibility Initiative provides a guidance document Developing a Web Accessibility Business Case for Your Organization.
Accessibility specialists are not generally concerned with the mobile context. Likewise Mobile Web specialists tend not to be concerned with accessibility for persons with disabilities. However they do have common requirements and design principles.
Unlike the Web Content Accessibility Guidelines, the Mobile Web Best Practices are not prioritized. MWBP relate to checkpoints of all the WCAG 1.0 priorities (1, 2 and 3).
While there appear to be many similarities between many of the WCAG provisions and those of the Mobile Web Best Practices, in reality there are many subtle differences. A simple table would be misleading and lead to duplication of work in some aspects and 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).
Readers familiar with accessibility and WCAG can not be expected to be aware of the mobile web, mobile devices, infrastructure and the MWBPs. Similarly, Mobile Web specialists can not be expected to have a thorough knowledge of the needs of users with disabilities and assistive technology. More information and guidance is needed.
Both the Mobile Web Best Practices and WCAG provide information about the possible barriers to users, and advice about how to avoid them. Compliance does not guarantee usability or accessibility. Barriers may arise other than those described and content providers should avoid them by performing user testing. Other solutions than those described may be found to the barriers. User testing should always include a full range of users, including those with different disabilities.