Incomplete draft: This document is an editor's copy that has no official standing and is incomplete. 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 public-bpwg-comments@w3.org (archive).
This page is part of a suite of related documents. Please refer to the “How to Use These Documents” section for more information.
This document describes how different WCAG checkpoints help Mobile Web users and how compliance with these checkpoints can help comply with the Mobile Web Best Practices 1.0 (MWBP). For content that already complies with WCAG at different levels, it outlines what may need to be done to comply with all of the MWBP (“Extending from WCAG 1.0 to MWBP 1.0”).
This section provides guidance on the “upgrade path” from WCAG 1.0 compliance to MWBP 1.0. What follows is a summary of the detailed information for each success criterion that follows it. For each of the WCAG 1.0 priorities (1, 2 and 3) already achieved, the BPs are classified in three broad categories representing the effort required, labelled for simplicity with keywords (nothing, something, everything):
${define_efforts}To summarize, if your content already complies with WCAG 1.0, to achieve compliance with MWBP 1.0, you need to do the following:
Nothing: content already complies with these BPs:
Something: more effort of some kind or a check, to comply with these BPs:
Everything: start from scratch to comply with these BPs:
[Not evaluated yet]. When reviewing the document the following list should be ignored. During document editing, it contains CPs, SCs or BPs not yet evaluated. It is progressively reduced as items are studied and moved to the “something”, “nothing” and “everything” lists. It will not appear in the finished document.
List of best practices described in detail:
MWBP 1.0: Provide a text equivalent for every non-text element.
No further effort is required. [1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content)...] ensures compliance with this best practice.