Re: CFC - WCAG 3 explainer and requirements

Hi Murata-san,

Thank you for the comment. The following was added in the editors note in the Goals for Inclusion <https://www.w3.org/TR/2026/DNOTE-wcag-3.0-explainer-20260303/#goals-for-inclusion>:

 Part of our upcoming focus is exploring using registries to broaden support for scripts other than Latin.

This acknowledges the working groups commitment <https://www.w3.org/2026/02/03-ag-minutes.html#3e5e> to address the issues you have raised without the Explainer trying to explain something that is not actually included in the referenced document.

The use of registries will take a bit of setting up and checking but it seems to offer a viable approach to addressing the issues. This topic will be a focus of the Text and wording subgroup <https://github.com/w3c/wcag3/wiki/Text-and-wording>. 

Thanks

Kevin
 

> On 24 Feb 2026, at 01:43, MURATA Makoto <founder@info-a11y.jp> wrote:
> 
> -1 since internationalization (including the lack of I18N in WCAG 2) is not mentioned.  Even the draft charter provides much more information about I18N.
> 
> Regards,
> MURATA Makoto
> 
> 2026年2月24日(火) 7:10 Alastair Campbell <alastair.campbell@thisisgain.com <mailto:alastair.campbell@thisisgain.com>>:
>> 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
>> 
>>