Re: CFC - WCAG 3 explainer and requirements

+1

On Tue, Feb 24, 2026 at 10:57 AM Jen Goulden <jgoulden@crawfordtech.com>
wrote:

> +1
>
>
>
> JEN GOULDEN, M.A., EDP, UEB Technical
>
> Accessibility Compliance Support Manager
>
> Chair, Braille Authority of North America
>
> Vice-President, International Council on English Braille
>
> 613-552-4191 (Cell)
>
> 343-804-0333 (Office)
>
> jgoulden@crawfordtech.com
>
> Crawford Technologies Inc.
>
> 20 Bay Street, Suite 1105
>
> Toronto, ON M5J 2N8
>
> www.crawfordtech.com
>
> This e-mail may be privileged and/or confidential, and the sender does not
> waive any related rights and obligations. Any distribution, use or copying
> of this e-mail or the information it contains by other than an intended
> recipient is unauthorized. If you received this e-mail in error, please
> advise me (by return e-mail or otherwise) immediately.
>
>
>
> Please consider our environment before printing this email.
>
>
>
> Ce courrier électronique est confidentiel et protégé. L'expéditeur ne
> renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion,
> utilisation ou copie de ce message ou des renseignements qu'il contient par
> une personne autre que le (les) destinataire(s) désigné(s) est interdite.
> Si vous recevez ce courrier électronique par erreur, veuillez m'en aviser
> immédiatement, par retour de courrier électronique ou par un autre moyen.
>
>
>
> *From:* Alastair Campbell <alastair.campbell@thisisgain.com>
> *Sent:* February 23, 2026 5:09 PM
> *To:* WCAG list <w3c-wai-gl@w3.org>
> *Subject:* CFC - WCAG 3 explainer and requirements
> *Importance:* High
>
>
>
> 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
>
>
>
>
>