How Compliance with
Mobile Web Best Practices 1.0 Helps with
Web Content Accessibility Guidelines 2.0
W3C Working Draft 06 May 2008
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 suite of related documents. Please refer to the “How to Use These Documents” 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.
- 1.1.1, Non-text Content, covered by NON-TEXT_ALTERNATIVES.
- 1.4.1 Use of Color, covered by USE_OF_COLOR. Note: However, it is important to taken into account that unlike the MWBP, the accessibility guidelines specify the ways that color may be used.
- 1.4.4, Resize text covered by MEASURES.
- 2.4.3 Focus Order, covered by TAB_ORDER.
- 2.4.10 Section Headings, covered by STRUCTURE. Tip: Although the BP has a generic title covering all structural elements, it only mentions section headings. Using other commonly-accepted structural elements not mentioned in the BP can improve usability for mobile users as well as accessibility, and give go some way toward compliance with WCAG success criterion 1.3.1 Info and Relationships. These elements include lists, quotations and citations, table markup, and semantic aspects like emphasis.
- 4.1.1, Parsing covered by VALID_MARKUP.
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.
- 1.3.1, Info and Relationships partially covered by FONTS, STRUCTURE, STYLE_SHEETS_SUPPORT, STYLE_SHEETS_USE.
- 1.3.2, Meaningful Sequence possibly covered by TABLES_LAYOUT.
- 1.4.3, Contrast (Minimum), possibly covered by BACKGROUND_IMAGE_READABILITY and COLOR_CONTRAST.
- 1.4.6, Contrast (Enhanced), possibly covered by BACKGROUND_IMAGE_READABILITY and COLOR_CONTRAST.
- 1.4.8, Visual Presentation, partially covered by SCROLLING.
- 2.1.1, Keyboard possibly covered by OBJECTS_OR_SCRIPT.
- 2.1.3, Keyboard (No Exception) possibly covered by OBJECTS_OR_SCRIPT
- 2.4.2, Page Titled, possibly covered by PAGE_TITLE.
- 2.4.4, Link Purpose (In Context), covered by LINK_TARGET_ID, possibly partially covered by IMAGE_MAPS.
- 2.4.6, Labels Descriptive, possibly partially covered by STRUCTURE and CONTROL_LABELLING.
- 2.4.9, Link Purpose (Link Only), covered by LINK_TARGET_ID, possibly partially covered by IMAGE_MAPS.
- 3.1.5, Reading Level, possibly covered by CLARITY.
- 3.2.1, On Focus, partially covered by POP_UPS.
- 3.2.2, On Input, partially covered by POP_UPS.
- 3.2.3, Consistent Navigation partially covered by NAVIGATION.
- 3.2.5 Change on Request, possibly covered by AUTO_REFRESH, POP_UPS and REDIRECTION.
- 3.3.2 Labels or Instructions, partially covered by CONTROL_LABELLING and CONTROL_POSITION.
- 4.1.2, Name, Role, Value, partially covered by CONTROL_LABELLING and NO_FRAMES.
For all other success criteria, the MWBP do not ensure compliance and it will be necessary to [do the work]. ()
Addressing WCAG 2.0 Success Criteria
1.3.1 Info and Relationships
Back to list of WCAG 2.0 checkpoints
1.3.2 Meaningful Sequence
Back to list of WCAG 2.0 checkpoints
1.4.3 Contrast (Minimum)
Back to list of WCAG 2.0 checkpoints
1.4.6 Contrast (Enhanced)
Back to list of WCAG 2.0 checkpoints
1.4.8 Visual Presentation
Back to list of WCAG 2.0 checkpoints
Back to list of WCAG 2.0 checkpoints
2.1.3 Keyboard (No Exception)
Back to list of WCAG 2.0 checkpoints
2.4.2 Page Titled
- PAGE_TITLE may possibly help. However, the accessibility techniques are more detailed, and in particular may lead to a title that is longer than suitable for a mobile device. Tip: While for the mobile context it is important to keep the title short, for the general user it is also important to provide an adequate description. One way to do this (known as “front loading”) is to place the most differentiating information first. More generic information (for example the section of a site) can be placed following this, or omitted for mobile delivery.
Refer to 2.4.2 Page Titled, in summary list.
Back to list of WCAG 2.0 checkpoints
2.4.4 Link Purpose (In Context)
Back to list of WCAG 2.0 checkpoints
2.4.6 Labels Descriptive
Back to list of WCAG 2.0 checkpoints
2.4.9 Link Purpose (Link Only)
Back to list of WCAG 2.0 checkpoints
3.1.5 Reading Level
- CLARITY may possibly help but it concerns a different aspect of language comprehension. WCAG is concerned with a user's reading ability, while this BP is concerned with reading difficulty due to context of use (for example, small screen, distracting environnment, lack of time).
Refer to 3.1.5 Reading Level in summary list.
Back to list of WCAG 2.0 checkpoints
Back to list of WCAG 2.0 checkpoints
3.2.3 Consistent Navigation
3.2.5 Change on Request
- AUTO_REFRESH may possibly help. This SC requires that refresh be started only by user request, but this BP concerns using auto-refresh started automatically and stopped by user request. If auto-refresh is used compliance is not necessarily achieved. However, if auto-refresh is not used at all, this does ensure compliance with the success criterion.
- POP_UPS partially covers this SC. WCAG 2.0 considers a number of different changes of context and a popup window is just one of them.
- REDIRECTION may partially help. It ensures that redirection is initiated only by user request, and therefore ensures compliance in the automatic redirects situation.
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
Back to list of WCAG 2.0 checkpoints
4.1.2 Name, Role, Value
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.
- 1.1.2, Live Audio-only (AAA)
- 1.2.1, Captions (Prerecorded) (A)
- 1.2.2, Audio Description or Full Text Alternative (A)
- 1.2.3, Captions (Live) (AA)
- 1.2.4, Audio Description (AA)
- 1.2.5, Sign Language (AAA)
- 1.2.6, Audio Description (Extended) (AAA)
- 1.2.7, Full Text Alternative (AAA)
- 1.3.3, Sensory Characteristics (A)
- 1.4.2, Audio Control (A)
- 1.4.5, Images of Text (Limited) (AA)
- 1.4.7, Low or No Background Audio (AAA)
- 1.4.9, Images of Text (Essential) (AAA)
- 2.1.2, No Keyboard Trap (A)
- 2.2.1, Timing Adjustable (A)
- 2.2.2, Pausing (AA)
- 2.2.3, No Timing (AAA)
- 2.2.4, Interruptions (AAA)
- 2.2.5, Re-authenticating (AAA)
- 2.3.1, Three Flashes or Below Threshold (A)
- 2.3.2, Three Flashes (AAA)
- 2.4.1, Bypass Blocks (A)
- 2.4.5, Multiple Ways (AA)
- 2.4.7, Focus Visible (AA)
- 2.4.8, Location (AAA)
- 3.1.1, Language of Page (A)
- 3.1.2, Language of Parts (AA)
- 3.1.3, Unusual Words (AAA)
- 3.1.4, Abbreviations (AAA)
- 3.1.6, Pronunciation (AAA)
- 3.2.4, Consistent Identification (AA)
- 3.3.1, Error Identification (A)
- 3.3.3, Error Suggestion (AA)
- 3.3.4, Error Prevention (Legal, Financial, Data) (AA)
- 3.3.5, Help (AAA)
- 3.3.6, Error Prevention (All) (AAA)