W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2018

RE: WCAG 2.1 Guideline Suggested Changes

From: Alastair Campbell <acampbell@nomensa.com>
Date: Tue, 10 Apr 2018 23:59:17 +0000
To: Michael Gower <michael.gower@ca.ibm.com>, Katie Haritos-Shea <ryladog@gmail.com>
CC: "Bailey, Bruce" <bailey@access-board.gov>, Kathy Wahlbin <kathy@interactiveaccessibility.com>, Katie Haritos-Shea <katie.haritos-shea@deque.com>, Shadi Abou-Zahra <shadi@w3.org>, WCAG <w3c-wai-gl@w3.org>
Message-ID: <AM5PR0902MB2002D7BD9AAB9EB6EBADA714B9BE0@AM5PR0902MB2002.eurprd09.prod.outlook.com>
Personally: I think both are improvements, overall I prefer the simpler approach to 2.5-8 (i.e. just having 2.5).

There’s a lot of conceptual overlap between speech input, input methods, and device settings. For me the simpler grouping matters more than where (new) individual SCs go.

Cheers,

-Alastair



From: Michael Gower

Changes from existing editor's draft:

  *   rename the existing Pointer Accessible guideline to Input Methods
     *   remove the word "pointer" from the existing short description of the guideline to now read: "Make it easier for users to operate functionality."
  *   remove Additional Sensor Inputs (put Motion Actuation under Input Methods)
  *   move Orientation to Adaptable -- where it fits well: "Create content that can be presented in different ways (for example simpler layout) without losing information or structure."
  *   move Character Key Shortcuts to Keyboard Accessible. It is where it fits practically and linguistically; speech operability rides on top of the keyboard API.
  *   move Label in Name to Compatible, where it fits well with the second Intention ("exposing information in the content in standard ways that assistive technologies can recognize and interact with.")
  *
Received on Tuesday, 10 April 2018 23:59:54 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:25 UTC