Doing Web Content Accessibility Guidelines 2.0 and
Mobile Web Best Practices 1.0 Together

Editor's draft, version 0i, 17 December 2007

Suite of Documents

This page is part of a suite of related documents. Please refer to the “How to Use These Documents” section for more information.

Table of Contents


Comment: In an ideal world this would be initial reading for anyone starting starting a new Web project as all content would be made both accessible and mobile-aware from the start. At present is likely to be a secondary scenario.

As described in this document, the two recommendations are complementary. the motivation for adopting them may be different (for example, commercial, regulatory, altruistic). It has been described elsewhere that retrofitting existing websites for compliance with another set of non-functional requirements is much more costly than complying during the design and development phases. the cost of late implementation (content repair, staff training, redesigning workflow) separately may also be much greater than doing both together, due to the synergies between them.

When a WCAG SC is more comprehensive or demanding than a BP and overlaps it completely, only include the SC in the list, and vice versa.

When starting a new Web project...

Meet this subset of WCAG success criteria


Meet this subset of the MWBPs

Not included above (and remove from this section of document once it is complete):

This is what projects doing both do not need to worry about if they do the preceding two sets.