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

AGWG’ers,

As we have received substantially positive feedback leading up to this CfC and no responses indicating that group members could not live this this decision, this CfC is agreed on as a consensus opinion of the working group.

This decision will be recorded at https://www.w3.org/WAI/GL/wiki/Decisions<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FGL%2Fwiki%2FDecisions&data=02%7C01%7C%7C1ab6006ec2be48e88f9008d4a210961e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636311639507586899&sdata=IafGoKjeQf7zBqxVj8m380hh8%2BWgU1VfPa2tZjq0Bx8%3D&reserved=0>
Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe

akirkpat@adobe.com<mailto:akirkpat@adobe.com>
http://twitter.com/awkawk



From: Andrew Kirkpatrick <akirkpat@adobe.com>
Date: Tuesday, January 16, 2018 at 16:52
To: WCAG <w3c-wai-gl@w3.org>
Subject: Re: CFC - Responses to issues 657, 677, and 685 on text spacing
Resent-From: WCAG <w3c-wai-gl@w3.org>
Resent-Date: Tuesday, January 16, 2018 at 16:51

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)<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2018%2F01%2F16-ag-minutes.html%23item03)&data=02%7C01%7Cakirkpat%40adobe.com%7C88c4d4f0fca646d4c8b208d55d2b687e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636517363376716827&sdata=X%2BeTQNJ2ZwYNnOHYnrwBpO9lSnphnuRwNIPBvfEc0L0%3D&reserved=0>.

The responses at https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#657_and_677_and_685<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FGL%2Fwiki%2FDraft_Responses_to_Dec_WD_Issues%23657_and_677_and_685&data=02%7C01%7Cakirkpat%40adobe.com%7C88c4d4f0fca646d4c8b208d55d2b687e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636517363376716827&sdata=d%2BN0RQM40%2BnWAobp0AwmF7NvRMW5d6Ifp7ruRqI4B1s%3D&reserved=0> 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<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frawgit.com%2Fw3c%2Fwcag21%2Fissue657%2Fguidelines%2Findex.html%23text-spacing&data=02%7C01%7Cakirkpat%40adobe.com%7C88c4d4f0fca646d4c8b208d55d2b687e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636517363376716827&sdata=RKh8O0dPdlTjuDEyPcnfK%2F1t2rHmNa812qMlA7oW2T0%3D&reserved=0>

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<mailto: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>