DRAFT: Mobile Accessibility WCAG 2.0 Extension

This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This page catalogs Mobile A11y Task Force proposed new mobile guidelines, success criteria and techniques.

Table of Contents

1. Perceivable

Guideline 1.1 Text Alternatives: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.

1.1.1 Non-text Content

Guideline 1.2 Time-based Media: Provide alternatives for time-based media.

1.2.1 Audio-only and Video-only (Prerecorded)

1.2.2 Captions (Prerecorded)

1.2.3 Audio Description or Media Alternative (Prerecorded)

1.2.4 Captions (Live)

1.2.5 Audio Description (Prerecorded)

1.2.6 Sign Language (Prerecorded)

1.2.7 Extended Audio Description (Prerecorded)

1.2.8 Media Alternative (Prerecorded)

1.2.9 Audio-only (Live)

Guideline 1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

1.3.1 Info and Relationships

1.3.2 Meaningful Sequence

1.3.3 Sensory Characteristics

Guideline 1.4 Distinguishable: Make it easier for users to see and hear content including separating foreground from background.

1.4.1 Use of Color

1.4.2 Audio Control

1.4.3 Contrast (Minimum)

1.4.4 Resize text

1.4.5 Images of Text

1.4.6 Contrast (Enhanced)

1.4.7 Low or No Background Audio

1.4.8 Visual Presentation

1.4.9 Images of Text (No Exception)

Principle 2: Operable - User interface components and navigation must be operable.

Guideline 2.1 Keyboard Accessible: Make all functionality available from a keyboard.

2.1.1 Keyboard

2.1.2 No Keyboard Trap

2.1.3 Keyboard (No Exception)

Guideline 2.2 Enough Time: Provide users enough time to read and use content.

2.2.1 Timing Adjustable

2.2.2 Pause, Stop, Hide

2.2.3 No Timing

2.2.4 Interruptions

2.2.5 Re-authenticating

Guideline 2.3 Seizures: Do not design content in a way that is known to cause seizures.

2.3.1 Three Flashes or Below Threshold

2.3.2 Three Flashes

Guideline 2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are.

2.4.1 Bypass Blocks

2.4.2 Page Titled

2.4.3 Focus Order

2.4.4 Link Purpose (In Context)

2.4.5 Multiple Ways

2.4.6 Headings and Labels

2.4.7 Focus Visible

2.4.8 Location

2.4.9 Link Purpose (Link Only)

2.4.10 Section Headings

Guideline 2.5 Touch and Pointer: Make it easier for users to operate touch and pointer functionality. [MOBILE]

2.5.1 Touch: All functions available by touch are still available by touch after system assistive technology that remaps touch gestures is turned on. (Level A) [MOBILE]

2.5.2 No Swipe Trap: When touch input behavior is modified by built-in assistive technology so that touch focus can be moved to a component of the page using swipe gestures, then focus can be moved away from that component using swipe gestures or the user is advised of the method for moving focus away. (Level A) [MOBILE]

2.5.3 Single Taps and Long Presses Revocable: Interface elements that require a single tap or a long press as input will only trigger the corresponding event when the finger is lifted inside that element. (Level A) [MOBILE]

2.5.4 Touch Target Size: One dimension of any touch targt measures at least 9 mm except when the user has reduced the default scale of content. (Level AA) [MOBILE]

2.5.5 Touch Target Clearance: The center of each touch target has a distance of at least 9 mm from the center of any other touch target, except when the user has reduced the default scale of content. (Level AA) [MOBILE]

2.5.6 Device manipulation: When device manipulation gestures are provided, touch and keyboard operable alternative control options are available. (Level AA) [MOBILE]

Principle 3: Understandable - Information and the operation of user interface must be understandable.

Guideline 3.1 Readable: Make text content readable and understandable.

3.1.1 Language of Page

3.1.2 Language of Parts

3.1.3 Unusual Words

3.1.4 Abbreviations

3.1.5 Reading Level

3.1.6 Pronunciation

Guideline 3.2 Predictable: Make Web pages appear and operate in predictable ways.

3.2.1 On Focus

3.2.2 On Input

3.2.3 Consistent Navigation

3.2.4 Consistent Identification

3.2.5 Change on Request

Guideline 3.3 Input Assistance: Help users avoid and correct mistakes.

3.3.1 Error Identification

3.3.2 Labels or Instructions

3.3.3 Error Suggestion

3.3.4 Error Prevention (Legal, Financial, Data)

3.3.5 Help

3.3.6 Error Prevention (All)

Guideline 3.4 Make content usable in device orientations.[MOBILE]

3.4.1 Expose Orientation: Changes in orientation are programmatically exposed to ensure assistive technology such as screen readers know the changes in layout. [MOBILE]

Guideline 3.5 Make interactive elements distinguishable [MOBILE]

3.5.1 Triggers Distinguishable: Elements that trigger changes should be sufficiently distinct to be clearly distinguishable from non-actionable elements (content, status information, etc). [MOBILE]

Principle 4: Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.

Guideline 4.1 Compatible: Maximize compatibility with current and future user agents, including assistive technologies.

4.1.1 Parsing

4.1.2 Name, Role, Value

4.1.3 Non-interference of AT: Content does not interfere with default functionality of platform level assistive technology [MOBILE]

Techniques with No Home

M003 Touch Activation: Activating elements via the touchend event