WCAG 2.1 Understanding and Techniques Development

From Mobile Accessibility Task Force
Jump to: navigation, search

This page includes links to all of the accepted SC, and a table of information to help the WG understand what work is needed for each:

Current Editor's Draft (Rendered as HTML): http://rawgit.com/w3c/wcag21/master/guidelines/index.html

Proposed Techniques for Accepted SC

Understanding Document

SC Name Level Understanding Content People working on this Last Update
Character Key Shortcuts (public) (member) A Edit View @KimPatch 2017-10-19
Label in Name (public) (member) A Edit View @KimPatch 2017-10-19
Guideline 2.5 Pointer Accessible - Edit View @detlevhfischer -
Target Size (public) (member) AAA Edit View @kwahlbin 2018-02-08 COMPLETED
Pointer Gestures (public) (member) A Edit View @detlevhfischer 2018-02-13
Pointer Cancellation (formerly Accidental Activation) (public) (member) A Edit View Chris
Concurrent Input Mechanisms (public) (member) AAA Edit View @jake-abma 2018-02-17
Guideline 2.6 Additional Sensor Inputs - Edit View @detlevhfischer 2018-02-13
Orientation (public) (member) AA Edit View @marcjohlic 2018-03-15
Motion Actuation (public) (member) A Edit View @melaniephilipp & @mbgower 2018-02-20
Status Changes (public) (member) AA Edit View Kathy 2017-12-06
Conformance - Full Pages (public) (member) - Edit View @DavidMacDonald -
Conformance - Optional Components of a Conformance Claim (public) (member) - Edit View @DavidMacDonald NA


WCAG 2.1 Master List Across all Taskforces:

OLD Techniques List

Everything below this line is for reference only, please use the WCAG 2.1 master list – see link above.


Character Key Shortcuts

  • Techniques
    • Turn off, Remap
  • Failures
    • Single key shortcut

Label in Name

Target Size

  • Techniques
    • Target size for buttons, links and controls
  • Failures
    • Target size less than 44 x 44 CSS px for buttons and controls

Pointer Gestures

Pointer Cancellation

Concurrent Input Mechanisms

  • Techniques
    • Only using high-level, input-agnostic event handlers (focus, blur, click) in Javascript (operating systems/UAs fire these events for all input mechanisms).
    • Registering event handlers for keyboard/keyboard-like and pointer inputs simultaneously in Javascript
  • Failures
    • Registering either touch event handlers or keyboard/mouse event handlers based on a feature check/presence of a touchscreen in Javascript.
    • Using CSS Media Queries Level 4 Interaction Media Features to determine what the UA deems to be the "primary" input mechanism and assuming no other input mechanisms are present/may be added/may be used.


  • Techniques
    • Using CSS to set the orientation to allow both landscape and portrait.
    • Use of show/hide controls to allow access to content in different orientations.
    • Use of the flexible box model to change the meaningful sequence order of content to match the visual order in different orientations.
  • Failures
    • Locking the orientation.
    • Non-essential functionality that is only available in one orientation.

Motion Actuation

  • Techniques
    • Do not use the device motion event to activate content functionality
    • Ensure that alternative means of input exist when using device motion sensor input to activate content functionality
    • Functionality/content must not solely rely on device inputs (e.g. an alternative which does not require the user to manipulate their device/use these device inputs must be available)
  • Failures
    • Functionality/content solely relies on device inputs (e.g. shaking or tilting)

Status Changes

  • Techniques
    • G199
    • ARIA19
    • using role="status"
    • Using role="log"
    • Using role="timer"
    • Using role="progressbar"
  • Failures
    • Using role="alert" or aria-live="assertive" on content which is not critical and time-sensitive