Re: CFC - Responses to issues 657, 677, and 685 on text spacing

+1

Yet another minor editorial quibble, with no intention for this to be a
blocker...

*Current:*
Human languages and scripts which do not make use of one or more of these
text style properties in written text can conform using only the properties
that are used.

*Proposed:*
Human languages and scripts which do not make use of one or more of these
text style properties in written text can conform using only the properties
that are supported by that language or script. (another alternative might
be required by that language or script).

JF

On Tue, Jan 16, 2018 at 4:50 PM, Andrew Kirkpatrick <akirkpat@adobe.com>
wrote:

> I’ve updated the pull request for this CFC per the discussion on the call
> today (https://www.w3.org/2018/01/16-ag-minutes.html#item03).
>
>
>
> The responses at https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_
> WD_Issues#657_and_677_and_685 also incorporated the editorial changes.
>
>
>
> Thanks,
>
> AWK
>
>
>
> Andrew Kirkpatrick
>
> Group Product Manager, Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> http://twitter.com/awkawk
>
>
>
> *From: *Andrew Kirkpatrick <akirkpat@adobe.com>
> *Date: *Sunday, January 14, 2018 at 23:25
> *To: *WCAG <w3c-wai-gl@w3.org>
> *Subject: *CFC - Responses to issues 657, 677, and 685 on text spacing
>
>
>
> Call For Consensus — ends Tuesday January 16th at 11:59pm Boston time.
>
>
>
> The Working Group has discussed responses to the following issues:
>
> 657: When vertical text mode, are SC 1.4.8/1.4.12 applicable as they are? (
> https://github.com/w3c/wcag21/issues/657)
>
> 677: Letter/Word spacing for CJK languages - SC 1.4.12 Text Spacing (
> https://github.com/w3c/wcag21/issues/677)
>
> 685: Internationalization implications of 1.4.12 (https://github.com/w3c/
> wcag21/issues/685)
>
>
>
> Response to Issue 657/677/685: https://www.w3.org/WAI/GL/
> wiki/Draft_Responses_to_Dec_WD_Issues#657_and_677_and_685
>
>
>
> The changes to the SC are implemented in this pull request:
> https://github.com/w3c/wcag21/pull/729
>
> The changed SC can be viewed here: http://rawgit.com/w3c/
> wcag21/issue657/guidelines/index.html#text-spacing
>
>
>
> 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>
>
>
>
>
>



-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion