Re: CFC - Advance WCAG 2.1 to Proposed Recommendation

+1

** katie **

*Katie Haritos-Shea*
*Principal ICT Accessibility Architect *

*WCAG/Section 508/ADA/AODA/QA/FinServ/FinTech/Privacy,* *IAAP CPACC+WAS = *
*CPWA* <http://www.accessibilityassociation.org/cpwacertificants>

*Cell: **703-371-5545 <703-371-5545>** |* *ryladog@gmail.com
<ryladog@gmail.com>* *| **Oakton, VA **|* *LinkedIn Profile
<http://www.linkedin.com/in/katieharitosshea/>*

People may forget exactly what it was that you said or did,
but people will never forget how you made them feel.......

Our scars remind us of where we have been........they do not have to
dictate where we are going.

On Thu, Apr 12, 2018 at 1:40 PM, Léonie Watson <tink@tink.uk> wrote:

> +1
>
>
> On 12/04/2018 19:33, Abma, J.D. (Jake) wrote:
>
>> +1
>>
>> *From:*Andrew Kirkpatrick [mailto:akirkpat@adobe.com]
>> *Sent:* donderdag 12 april 2018 19:38
>> *To:* WCAG <w3c-wai-gl@w3.org>
>> *Subject:* CFC - Advance WCAG 2.1 to Proposed Recommendation
>> *Importance:* High
>>
>> 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/g
>> uidelines/ <https://na01.safelinks.protection.outlook.com/?url=https%
>> 3A%2F%2Fw3c.github.io%2Fwcag21%2Fguidelines%2F&data=02%7C01%
>> 7Cakirkpat%40adobe.com%7Ce156f78bc15a4db1f02d08d5a0953d14%7C
>> fa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63659148519727547
>> 5&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%7Ce156f
>> 78bc15a4db1f02d08d5a0953d14%7Cfa7b1b5a7b34438794aed2c178dece
>> e1%7C0%7C0%7C636591485197275475&sdata=%2B7i%2FPdHEqyFzsUZqSI
>> 1qRi41GtoX3TBoEB4Guq7lyEM%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%7C
>> fa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63659148519727547
>> 5&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 <mailto:akirkpat@adobe.com>
>>
>> http://twitter.com/awkawk
>>
>> -----------------------------------------------------------------
>> ATTENTION:
>> The information in this e-mail is confidential and only meant for the
>> intended recipient. If you are not the intended recipient, don't use or
>> disclose it in any way. Please let the sender know and delete the message
>> immediately.
>> -----------------------------------------------------------------
>>
>>
> --
> @LeonieWatson @tink@toot.cafe Carpe diem
>
>