Re: CFC Move WCAG 2.2 to Candidate Recommendation (Revised)

Although I agree that normative tweaks ARE allowed after CR if they are carefully justified and then pass an OK at a higher level in the W3C — why would we delay putting them in BEFORE  CR - so that thee field can see them and approve the CR with them in it

I don’t think we should put off any normative tweaks til after CR if we know about them now.

Just my opinion 

Gregg Vanderheiden
gregg@vanderheiden.us



> On Aug 11, 2022, at 11:46 AM, Andrew Kirkpatrick <akirkpat@adobe.com> wrote:
> 
> +1
>  
> I do agree with two of the three small normative tweaks, but these can also be dealt with during CR and none of them are consequential enough to hold up the release of WCAG 2.2.
>  
> Thanks,
> AWK
>  
> Andrew Kirkpatrick
> Director, Accessibility
> Adobe 
>  
> akirkpat@adobe.com <mailto:akirkpat@adobe.com>
> http://twitter.com/awkawk <http://twitter.com/awkawk>
>  
>  
> From: "Bradley-Montgomery, Rachael" <rmontgomery@loc.gov <mailto:rmontgomery@loc.gov>>
> Date: Tuesday, August 2, 2022 at 10:03 AM
> To: WCAG <w3c-wai-gl@w3.org <mailto:w3c-wai-gl@w3.org>>
> Subject: Re: CFC Move WCAG 2.2 to Candidate Recommendation (Revised)
> Resent-From: WCAG <w3c-wai-gl@w3.org <mailto:w3c-wai-gl@w3.org>>
> Resent-Date: Tuesday, August 2, 2022 at 10:03 AM
>  
> EXTERNAL: Use caution when clicking on links or opening attachments.
>  
> My apologies, I used the incorrect URI. Please review https://w3c.github.io/wcag/guidelines/22/ <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwcag%2Fguidelines%2F22%2F&data=05%7C01%7Cakirkpat%40adobe.com%7C1afcd5e988c945c7ea6e08da748fb80a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637950457878546123%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Z%2FiQ8%2B83UAVVo0jMc8Cq22mCwYZWEZemnzzKNduNFjA%3D&reserved=0>
>  
> The revised CFC is below. 
>  
> Call for Consensus – ends Thursday August 11th at 23:59pm Boston time.
> The Working Group has approved CFCs for all new normative content in WCAG 2.2 and it is ready to move to Candidate Recommendation.
> The draft is at https://w3c.github.io/wcag/guidelines/22/ <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwcag%2Fguidelines%2F22%2F&data=05%7C01%7Cakirkpat%40adobe.com%7C1afcd5e988c945c7ea6e08da748fb80a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637950457878546123%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Z%2FiQ8%2B83UAVVo0jMc8Cq22mCwYZWEZemnzzKNduNFjA%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.