Re: CFC - WCAG 3 explainer and requirements

+1
With explanation.

I have not yet had the opportunity to get up to speed on “that have not been discussed already”.
I have an editorial request that the Explainer §5.4 Best practices should have a glossary entry for ‘best practices’ with a link to it.

Charles Hall

Principal Consultant, Access.Today
Invited Expert, W3C Accessibility Guidelines Working Group & Authoring Tools Accessibility Guidelines Community Group
Member, Lathrup Village Communication Commission, Accessibility Expert


> On Feb 23, 2026, at 5:09 PM, Alastair Campbell <alastair.campbell@thisisgain.com> wrote:
> 
> Call For Consensus — ends 2nd March 2026 at midday Boston time.
> 
> The update is to publish updates to:
> WCAG 3 explainer (https://w3c.github.io/wcag3/explainer/ <https://urldefense.com/v3/__https://w3c.github.io/wcag3/explainer/__;!!EDx7F7x-0XSOB8YS_BQ!dtF1XfBpH1cZfkKLBYd1KlbtWXkv6eLmjXNkEx988htp2ES_v0woMAss9aNomY2gJgeTjRbVW76u8uo$>), and
> WCAG 3 Requirements (https://w3c.github.io/wcag3/requirements/ <https://urldefense.com/v3/__https://w3c.github.io/wcag3/requirements/__;!!EDx7F7x-0XSOB8YS_BQ!dtF1XfBpH1cZfkKLBYd1KlbtWXkv6eLmjXNkEx988htp2ES_v0woMAss9aNomY2gJgeTjRbVoT8JM8U$>)
> 
> This CFC does not replace the existing CFC for the working draft <https://urldefense.com/v3/__https://lists.w3.org/Archives/Public/w3c-wai-gl/2026JanMar/0079.html__;!!EDx7F7x-0XSOB8YS_BQ!dtF1XfBpH1cZfkKLBYd1KlbtWXkv6eLmjXNkEx988htp2ES_v0woMAss9aNomY2gJgeTjRbVOeAwH5o$>.
> 
> Updates to the explainer bring it in line with the current working draft for WCAG 3.
> Explainer diff <https://urldefense.com/v3/__https://services.w3.org/htmldiff?doc1=https:**Awww.w3.org*TR*wcag-3.0-explainer*&doc2=https:**Adeploy-preview-585--wcag3.netlify.app*explainer*__;Ly8vLy8vLy8v!!EDx7F7x-0XSOB8YS_BQ!dtF1XfBpH1cZfkKLBYd1KlbtWXkv6eLmjXNkEx988htp2ES_v0woMAss9aNomY2gJgeTjRbVpFTDvX8$>
> 
> Updates to the requirements were minimal to fix a broken link.
> Requirements diff <https://urldefense.com/v3/__https://services.w3.org/htmldiff?doc1=https:**Awww.w3.org*TR*wcag-3.0-requirements*&doc2=https:**Adeploy-preview-585--wcag3.netlify.app*requirements*__;Ly8vLy8vLy8v!!EDx7F7x-0XSOB8YS_BQ!dtF1XfBpH1cZfkKLBYd1KlbtWXkv6eLmjXNkEx988htp2ES_v0woMAss9aNomY2gJgeTjRbVeDbQZl4$>
>  
> To support the CFC please reply to the group with a “+1”.
> 
> 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 accept this decision, please reply with a “-1” and explanation before the CfC deadline.
> 
> Kind regards,
>  
> AG Chairs
> 
>