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 email@example.com (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.
As described in this document, the two recommendations are complementary. The motivation for adopting them may be different for each (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) seperately may also be much greater than doing both together, due to the synergies between them. (So we suggest that for many projects there are compelling reasons to do both at the same time...)
The document Experiences Shared by People with Disabilities and by People Using Mobile Devices shows some of the overlaps between the Recommendations from the users' standpoint.
This document looks at ways in which some of the Mobile Web BPs and WCAG SCs can be addressed together. Future versions of this document may provide detailed guidance on how to approach both Recommendations together. This version provides just a brief outline of how it is possible to devise a coherent set of requirements for a given project covering both recommendations together. It is important to understand that WCAG 2.0 success criteria (SCs) are assigned levels, and for this reason compilation of the list of requirements begins with WCAG. The following steps can be used to draw up a list of requirements: