W3C

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

W3C Editor's Draft 24 June 2008

Table of Contents

Introduction

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 multi-page document. Please refer to the “How to Use This Document” section for more information.

It describes how some Mobile Web Best Practices (MWBPs) help with achieving compliance with the Web Content Accessibility Guidelines 2.0 (WCAG). For content that already complies with MWBP, it outlines what may need to be done to comply with all of WCAG.

As described in this section, many Mobile Web BPs have the added benefit of partial or complete compliance with certain WCAG success criteria. However, the accessibility guidelines are often more detailed or describe a different aspect of the same concept. It should not be assumed that following any BP will ensure accessibility. To ensure accessibility it is important to always consult the Web Content Accessibility Guidelines.

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

Compliance with the MWBP helps go some way towards achieving compliance with some WCAG 2.0 success criteria. This section provides a summary of these SC. For those SC not listed, there is no synergy between the recommendations.

Nothing: content already complies with these SCs. The list is provided for completeness.

Something: some more effort of some kind or a check, will be necessary to ensure compliance with these SCs. Refer to the sections below on each success criterion for an explanation of how and in what way the BPs partially or possibly help to meet the SC.

For all other success criteria, the MWBP do not ensure compliance and it will be necessary to [do the work]. (Comment: these are listed temporarily at the end of the document under SCs with no coverage.)

Addressing WCAG 2.0 Success Criteria

This section deals with each of the success criteria which MWBP helps with meeting.

1.3.1 Info and Relationships

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)

Refer to 1.3.1, Info and Relationships in summary list.

Back to list of WCAG 2.0 checkpoints

1.3.2 Meaningful Sequence

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A)

Refer to 1.3.2, Meaningful Sequence in summary list.

Back to list of WCAG 2.0 checkpoints

1.4.3 Contrast (Minimum)

The visual presentation of text and images of text has a contrast ratio of at least 5:1, except for... (Level AA)

Refer to 1.4.3 Contrast (Minimum) in summary list.

Back to list of WCAG 2.0 checkpoints

1.4.6 Contrast (Enhanced)

The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for...: (Level AAA)

Refer to 1.4.6 Contrast (Enhanced) in summary list.

Back to list of WCAG 2.0 checkpoints

1.4.8 Visual Presentation

For the visual presentation of blocks of text, a mechanism is available to achieve the following: (Level AAA) How to Meet 1.4.8 Understanding 1.4.8

  1. foreground and background colors can be selected by the user

  2. width is no more than 80 characters or glyphs (40 if CJK)

  3. text is not justified (aligned to both the left and the right margins)

  4. line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing

  5. text is resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window

Refer to 1.4.8 Visual Presentation in summary list.

Back to list of WCAG 2.0 checkpoints

2.1.1 Keyboard

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A)

Refer to 2.1.1 Keyboard, in summary list.

Back to list of WCAG 2.0 checkpoints

2.1.3 Keyboard (No Exception)

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. (Level AAA)

Refer to 2.1.3 Keyboard (No Exception), in summary list.

Back to list of WCAG 2.0 checkpoints

Web pages have titles that describe topic or purpose

Refer to 2.4.2 Page Titled, in summary list.

Back to list of WCAG 2.0 checkpoints

The purpose of each link can be determined from the link text alone, or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.

Refer to 2.4.4 Link Purpose (In Context) in summary list.

Back to list of WCAG 2.0 checkpoints

Headings and labels describe topic or purpose. (Level AA)

Refer to 2.4.6 Labels Descriptive in summary list.

Back to list of WCAG 2.0 checkpoints

A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general. (Level AAA)

Refer to 2.4.9 Link Purpose (Link Only) in summary list.

Back to list of WCAG 2.0 checkpoints

3.1.5 Reading Level

When text requires reading ability more advanced than the lower secondary education level, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available. (Level AAA)

Refer to 3.1.5 Reading Level in summary list.

3.2.1 On Focus

When any component receives focus, it does not initiate a change of context. (Level A)

Refer to 3.2.1 On Focus in summary list.

Back to list of WCAG 2.0 checkpoints

3.2.2 On Input

Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A)

Refer to 3.2.2 On Input in summary list.

Back to list of WCAG 2.0 checkpoints

3.2.3 Consistent Navigation

Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA)

Refer to 3.2.3 Consistent Navigation in summary list.

3.2.5 Change on Request

Changes of context are initiated only by user request or a mechanism is available to turn off such changes. (Level AAA)

Refer to 3.2.5 Change on Request in summary list.

Back to list of WCAG 2.0 checkpoints

3.3.2 Labels or Instructions

Labels or instructions are provided when content requires user input. (Level A)

Refer to 3.3.2 Labels or Instructions in summary list.

Back to list of WCAG 2.0 checkpoints

4.1.2 Name, Role, Value

For all user user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)

Refer to 4.1.2 Name, Role, Value in summary list.

Back to list of WCAG 2.0 checkpoints

SCs with no coverage

This list is provided as a completeness check during editing and will be removed in the final document, as discussed by EOWG.