Re: CFC - Adding errata and updating understanding documents for WCAG 2.0

Hey Rachael,
Can you clarify why the note that is being added to SC 4.1.1 for WCAG 2.0
is different from the note that was added to WCAG 2.1?

For reference, here is the diff that Alastair sent out for WCAG 2.1
https://services.w3.org/htmldiff?doc1=https://www.w3.org/TR/WCAG21/&doc2=https://labs.w3.org/spec-generator/?type%3Drespec%26url%3Dhttps://raw.githack.com/w3c/wcag/WCAG-2.1-catchup/guidelines/index.html#parsing

My understanding was that this note had already been approved for
publication on March 30th <https://www.w3.org/WAI/GL/wiki/Decisions>. Is
there a reason we need a different note in WCAG 2.0 from what is in WCAG
2.1?


On Mon, Aug 14, 2023 at 1:18 PM Bradley Montgomery, Rachael L <
rmontgomery@loc.gov> wrote:

> Call For Consensus — ends Friday August 18th at 2:00 Boston time.
>
>
>
> This call is to add a new errata and update the understanding document for
> WCAG 2.0.  This will address the removal of parsing to bring WCAG 2.0 more
> in line with WCAG 2.1 and 2.2.
>
>
>
> The *proposed updates are in the attachments*.
>
>
>    - *Errata:* See number 13 under Editorial Errata
>    - *Understanding Document:* The new text is at the top and the
>    original text is at the bottom, marked as historical.
>
> Because of changes to technology since WCAG 2.0 was published we cannot
> provide a diff.  The original content is at:
>
>
>    - *Errata (original):* https://www.w3.org/WAI/WCAG20/errata/ and
>    - *Understanding Document (original):*
>    https://www.w3.org/WAI/WCAG20/Understanding/parsing
>
> 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.
>
>
> Kind regards,
>
>
> Rachael
>
>
>
>

-- 
*Wilco Fiers*
Axe-core & Axe-linter product owner - WCAG 3 Project Manager - Facilitator
ACT Task Force