Re: CFC - SC Reorganization

Do we still need the editors not for 4.1.3?


EDITOR'S NOTE

The working group seeks input regarding the feasibility and applicability
of complex gaming scenarios for this SC.


Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Thu, Apr 12, 2018 at 8:12 PM, Greg Lowney <gcl-0039@access-research.org>
wrote:

> Section 0.5.1 "New Features in WCAG 2.1", still lists new SC by
> yesterday's numbers, so needs to be corrected.
>
> -------- Original Message --------
> Subject: CFC - SC Reorganization
> From: Andrew Kirkpatrick <akirkpat@adobe.com> <akirkpat@adobe.com>
> To: WCAG <w3c-wai-gl@w3.org> <w3c-wai-gl@w3.org>
> Date: 4/12/2018 9:31 AM
>
> Call For Consensus — ends 15 April at 12:30pm Boston time.
>
>
>
> The Working Group has discussed a reorganization of a few SC, specifically:
>
>    - Moving: Orientation into 1.3
>    - Moving: Character Key Shortcuts into 2.1
>    - Renaming 2.5 to Input Modalities and including the description: *Make
>    it easier for users to operate functionality through various inputs beyond
>    keyboard*
>    - Including SC in 2.5:
>
> 2.5.1 Pointer Gestures
>
> 2.5.2 Pointer Cancellation
>
> 2.5.3 Label in Name (was 2.4.12)
>
> 2.5.4 Target Size
>
> 2.5.5 Concurrent Input Mechanisms
>
> 2.5.6 Motion Actuation (was 2.6.1)
>
>    - Removing 2.6
>
>
>
> Here is the rendered HTML version with the changes:
> https://rawgit.com/w3c/wcag21/bigreshuffle/guidelines/
>
>
>
> The specific changes are detailed here: https://github.com/w3c/
> wcag21/pull/862/files?diff=split
>
>
>
> Call minutes: https://www.w3.org/2018/04/12-ag-minutes.html#item02
>
>
>
> If you have concerns about this proposed consensus position that have not
> been discussed already and feel that those concerns result in you “not
> being able to live with” this decision, please let the group know before
> the CfC deadline.
>
>
>
> Thanks,
>
> AWK
>
>
>
> Andrew Kirkpatrick
>
> Group Product Manager, Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> http://twitter.com/awkawk
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7C%7C54093524ef264326424008d51cd66c05%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446629619786436&sdata=c5UP0xiniJIppvd6Esu1XA%2FbX1ykpABkhgCCmBp%2Fht8%3D&reserved=0>
>
>
>
>
>
>
>