Re: Changes not yet in the editors' draft Re: CFC - Advance WCAG 2.1 to Proposed Recommendation

My response depends on those changes being made, assuming the Director
agrees.

On Fri, Apr 13, 2018, 7:22 PM Michael Cooper <cooper@w3.org> wrote:

> In the CfC to advance to Proposed Recommendation, we said what will be
> published as a PR is the content of the editors' draft. However, changes
> from other open CfCs are not yet incorporated into that, so I wanted to
> clarify what content would be included in the Proposed Recommendation if
> this CfC passes.
>
> If your response on this CfC to transition to PR depends on the outcome of
> one of the CfCs below, please say so in your response to this one, so we
> can take that into consideration.
>
> The Proposed Recommendation would include the content currently in the
> editors' draft (
> https://rawgit.com/w3c/wcag21/791ae8c74f3a13346d1d3d018f194baf73c8953d/guidelines/).
> In addition, it would include the changes from the following diff views
> *if* the relevant CfC for each passes:
>
>    - Add "to" and note in pointer cancellation
>    https://github.com/w3c/wcag21/pull/860/files?diff=split
>    - SC reorganization
>    https://github.com/w3c/wcag21/pull/862/files?diff=split
>    - Introduction changes
>    https://github.com/w3c/wcag21/compare/intro-dits-coga3?expand=1
>
> By default, if the CfC for one of the above changes does not pass, but the
> CfC to transition to Proposed Recommendation does pass, the Proposed
> Recommendation would still go forward, but without the change from the
> failed CfC. If people express concern on the PR CfC about that, we will
> evaluate the input.
>
> Michael
>
> On 12/04/2018 1:38 PM, Andrew Kirkpatrick wrote:
>
> Call for Consensus - ends Tuesday April 17 at 1:30 pm Boston time
>
>
>
> This is a Call for Consensus to advance WCAG 2.1 to Proposed
> Recommendation. A few tasks related to the transition are not quite
> complete but we expect them to be by the time the CfC closes, and to stay
> on timeline we are running the CfC in parallel. These along with key review
> points are described below.
>
>
>
> The Editors' Draft which includes the content proposed to be published as
> a Proposed Recommendation is available at:
> https://w3c.github.io/wcag21/guidelines/
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwcag21%2Fguidelines%2F&data=02%7C01%7Cakirkpat%40adobe.com%7Ce156f78bc15a4db1f02d08d5a0953d14%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636591485197275475&sdata=GcaBt4EVRDazIDUV0oTF%2BpOBSnNLAaSEmp2chaEDtlA%3D&reserved=0>
>
>
>
> Active responses to this CfC are helpful, particularly from implementers.
> Please reply with "+1" to support or "-1" along with an explanation to
> oppose. 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.
>
>
>
> The Working Group agreed on the teleconference on 4/12/18 to conduct a CFC
> to advance to PR, as indicated in the minutes:
> https://www.w3.org/2018/04/12-ag-minutes.html
>
>
>
> Tasks still to be completed before the CfC closes:
>
>    - Document 8 AA and 2 AAA implementations in the implementation report
>    https://www.w3.org/WAI/WCAG21/implementation-report/
>    <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FWCAG21%2Fimplementation-report%2F&data=02%7C01%7Cakirkpat%40adobe.com%7Ce156f78bc15a4db1f02d08d5a0953d14%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636591485197275475&sdata=%2B7i%2FPdHEqyFzsUZqSI1qRi41GtoX3TBoEB4Guq7lyEM%3D&reserved=0> (3
>    more AA needed at time the CfC was sent, but these are in progress)
>    - Address and close all public comments filed on the CR
>    https://github.com/w3c/wcag21/issues?q=is%3Aopen+is%3Aissue+label%3A%22Public+Comment%22+label%3A%22CR+Comment%22
>    <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwcag21%2Fissues%3Fq%3Dis%253Aopen%2Bis%253Aissue%2Blabel%253A%2522Public%2BComment%2522%2Blabel%253A%2522CR%2BComment%2522&data=02%7C01%7Cakirkpat%40adobe.com%7Ce156f78bc15a4db1f02d08d5a0953d14%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636591485197275475&sdata=bY%2BwMIsQSys4jRJA%2B98vqhaTjn6WdVXAcFs9LeGQ%2BPE%3D&reserved=0>
>    - Approve changes to the introduction in CfC sent after the meeting on
>    Thursday 4/12/18.
>
>
>
> Key review points:
>
>    - Some guidelines and success criteria have been moved or renamed, in
>    what we believe is an editorial manner which does not impact implementation.
>    - The Introduction is rewritten to apply to the final standard and
>    includes more information about the limitations of WCAG 2.1 and refers to
>    additional resources.
>    - No features at risk have been removed.
>
>
>
> Thanks,
>
> AWK
>
>
>
> Andrew Kirkpatrick
>
> Group Product Manager, Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> http://twitter.com/awkawk
>
>
>