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

W3C Editor's Draft 01 September 2008

Table of Contents


Incomplete draft: This document is an in-progress Working Draft provided for review and feedback. It is incomplete and will likely have major changes. See also Status of this Document in the overview page.
Please send feedback to public-bpwg-comments@w3.org (with public archive).

This page is part of a multi-page document. Please refer to the “How to Use This Document” section for more information.

If your content already meets Web Content Accessibility Guidelines 1.0, this page describes what needs to be done to meet all the Mobile Web Best Practices (MWBP).

Summary of work required to make content that meets WCAG 1.0 also meet MWBP

Compliance with WCAG 1.0 helps go some way towards achieving compliance with some of the MWBP. This section provides a summary of these BPs. There are two possible levels of effort required, labelled for simplicity with the keywords nothing and something. Refer to definition of use of these terms in Appendix B: Special Terms. To summarise, if your content already complies with WCAG 1.0, to achieve compliance with the MWBP, you need to do the following:

Note on inconsistent links: Links in the “something” and “nothing” sections point to within this page. Links in the “everything” section point to the Recommendation. REVIEW NOTE: Is this too confusing? Suggestions for better ways to do it?

Nothing: Content that already meets WCAG 1.0 should already meet these BPs. Checkpoint and BP links in this section point to the relevant Recommendation.

Something: More effort of some kind or a check, is necessary to ensure compliance with these BPs. BP links in this section point to detail sections below; checkpoint links to the MWBP Recommendation.

Addressing Mobile Web Best Practices

This section deals with each of the best practices which WCAG 1.0 helps with meeting. For each BP, the section title is that of the BP. This is followed by a list of the checkpoints that can help meet it.

[ACCESS_KEYS] Assign access keys to links in navigational menus and frequently accessed functionality

[BACKGROUND_IMAGE_READABILITY] When using background images make sure that content remains readable on the device

[COLOR_CONTRAST] Ensure that foreground and background color combinations provide sufficient contrast

[CONTROL_POSITION] Position labels so they lay out properly in relation to the form controls they refer to

[FONTS] Do not rely on support of font related styling

[NAVBAR] Provide only minimal navigation at the top of the page

[PAGE_SIZE_USABLE] Divide pages into usable but limited size portions

[PAGE_TITLE] Provide a short but descriptive page title

[TABLES_ALTERNATIVES] Where possible, use an alternative to tabular presentation

[TABLES_LAYOUT] Do not use tables for layout