W3C

From MWBP to WCAG 1.0: Making content that meets Mobile Web Best Practices also meet Web Content Accessibility Guidelines 1.0

W3C Working Group Note 9 July 2009

Table of Contents

Introduction

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

For those familiar with Mobile Web Best Practices (MWBP), this page describes what also needs to be done to meet Web Content Accessibility Guidelines 1.0. W3C WAI recommends using WCAG 2.0, instead of WCAG 1.0. If your site is required to meet WCAG 1.0, you can develop it to meet both WCAG 1.0 and WCAG 2.0.

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

Compliance with the MWBP helps go some way towards achieving compliance with some WCAG 1.0 checkpoints. This section provides a summary of these checkpoints. There are three possible levels of effort required, labelled for simplicity with the keywords nothing, something and everything. To summarise, if your content already complies with the MWBP, to achieve compliance with WCAG 1.0, you need to do the following:

Nothing: If a provision is labelled “Nothing” then content that complies with MWBP already complies with the provision and no further effort is necessary.The following list includes all of the provisions that are marked “Nothing”. Links in this section point to the relevant provisions.

Something: If a provision is labelled “Something” then more effort of some kind is necessary to comply with the provision. All of the provisions marked “Something” are included in the list below. Each item in the list is a link to an explanation of what is required, in the next section of this report. For each there is a list of the provisions that may provide some compliance or are in some way related. There is no direct correspondence between one provision and another. In some cases, it may be necessary to make an extra effort or to consider a more diverse range of user needs. In these cases, the word “possibly” is used. In other cases scope may be different, giving partial compliance. In these cases the word “partially” is used. Checkpoint links in this section point to the detail section below; BPs link to the MWBP Recommendation.

Everything: For all other CPs, the MWBP do not ensure compliance and it will be necessary to do the work involved. These CPs are not related to any MWBPs.

Addressing WCAG 1.0 Checkpoints

This section lists each of the WCAG 1.0 checkpoints that are related to MWBP, which are listed under “something” above. For each checkpoint, the section title is that of the checkpoint. This is followed by a quotation of the text of the checkpoint (sometimes abbreviated) and a list of the BPs that can help meet it. The information given in this document is intentionally brief. A separate document, entitled “Techniques for Web Content Accessibility Guidelines 1.0”, explains how to implement the checkpoints. The Techniques Document discusses each checkpoint in more detail and provides examples

WCAG 1.0: “Provide redundant text links for each active region of a server-side image map.” (Priority 1)

Back to list of WCAG 1.0 checkpoints

WCAG 1.0: “Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map.” (Priority 3)

Back to list of WCAG 1.0 checkpoints

2.2 Ensure that foreground and background color combinations provide sufficient contrast…

WCAG 1.0: “Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen (for images). [Priority 2 for images, Priority 3 for text]”

Back to list of WCAG 1.0 checkpoints

3.1 When an appropriate markup language exists, use markup…

WCAG 1.0: “When an appropriate markup language exists, use markup rather than images to convey information" (Priority 2).

Back to list of WCAG 1.0 checkpoints

5.1 For data tables, identify row and column headers

WCAG 1.0: “For data tables, identify row and column headers. For example, in HTML, use TD to identify data cells and TH to identify headers.” (Priority 1)

Depending on device support, tables may or may not be used, as described for above. However, in contexts where tables are used, identify row and column headers using appropriate markup as required by this checkpoint.

Back to list of WCAG 1.0 checkpoints

5.2 For data tables that have two or more logical levels of row or column headers…

WCAG 1.0: “For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells.” (Priority 1)

Depending on device support, tables may or may not be used, as described for checkpoint 5.1, above. However, in contexts where tables are used, identify row and column headers using appropriate markup as required by this checkpoint.

Back to list of WCAG 1.0 checkpoints

5.3 Do not use tables for layout unless…

WCAG 1.0: “Do not use tables for layout unless the table makes sense when linearized.” (Priority 2)

Back to list of WCAG 1.0 checkpoints

5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting

WCAG 1.0: “If a table is used for layout, do not use any structural markup for the purpose of visual formatting.” (Priority 2)

Back to list of WCAG 1.0 checkpoints

5.5 Provide summaries for tables

WCAG 1.0: “Provide summaries for tables. For example, in HTML, use the “summary” attribute of the TABLE element (Priority 3).

Depending on device support, tables may or may not be used, as described for checkpoint 5.1, above. However, in contexts where tables are used, provide summaries as required by this checkpoint.

Back to list of WCAG 1.0 checkpoints

5.6 Provide abbreviations for header labels

WCAG 1.0: “Provide abbreviations for header labels.” (Priority 3)

Depending on device support, tables may or may not be used, as described for checkpoint 5.1, above. However, in contexts where tables are used, provide abbreviations for header labels where appropriate, as described by this checkpoint.

Back to list of WCAG 1.0 checkpoints

6.2 Ensure that equivalents for dynamic content are updated…

WCAG 1.0: “Ensure that equivalents for dynamic content are updated when the dynamic content changes.” (Priority 1)

Back to list of WCAG 1.0 checkpoints

9.1 Provide client-side image maps instead of server-side image maps…

WCAG 1.0: “Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape.” (Priority 1)

Back to list of WCAG 1.0 checkpoints

10.2 Until user agents support explicit associations between labels…

WCAG 1.0: “Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned.” (Priority 2)

Back to list of WCAG 1.0 checkpoints

10.3 Until user agents (including assistive technologies) render side-by-side text correctly…

WCAG 1.0: “Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns.” (Priority 3)

Depending on device support, tables may or may not be used, as described for checkpoint 5.1, above. However, in contexts where tables are used to lay out text in parallel, word-wrapped columns, provide a linear text alternative, as described by this checkpoint.

Back to list of WCAG 1.0 checkpoints

11.1 Use W3C technologies when they are available and appropriate for a task…

WCAG 1.0: “Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported.” (Priority 2)

Back to list of WCAG 1.0 checkpoints

11.2 Avoid deprecated features of W3C technologies

WCAG 1.0: “Avoid deprecated features of W3C technologies” (Priority 2)

Back to list of WCAG 1.0 checkpoints

12.1 Title each frame to facilitate frame identification and navigation

WCAG 1.0: “Title each frame to facilitate frame identification and navigation” (Priority 1)

Back to list of WCAG 1.0 checkpoints

12.2 Describe the purpose of frames and how frames relate to each other…

WCAG 1.0: “Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone.” (Priority 2)

Back to list of WCAG 1.0 checkpoints

12.3 Divide large blocks of information into more manageable groups where natural and appropriate

WCAG 1.0: “Divide large blocks of information into more manageable groups where natural and appropriate.” (Priority 2)

Back to list of WCAG 1.0 checkpoints

Back to list of WCAG 1.0 checkpoints

13.2 Provide metadata to add semantic information to pages and sites

WCAG 1.0: “Provide metadata to add semantic information to pages and sites.” (Priority 2)

Back to list of WCAG 1.0 checkpoints

13.5 Provide navigation bars to highlight and give access to the navigation mechanism

WCAG 1.0: “Provide navigation bars to highlight and give access to the navigation mechanism” (Priority 3)

Back to list of WCAG 1.0 checkpoints

Back to list of WCAG 1.0 checkpoints

14.1 Use the clearest and simplest language appropriate for a site's content

WCAG 1.0: “Use the clearest and simplest language appropriate for a site's content.” (Priority 1)

Back to list of WCAG 1.0 checkpoints


Updated 27 June 2009.