Add change log notes for removal of 4.1.1

[venkatvemuri28]

• Updates Appendix A. Change Log to reflect the November 10, 2019 entry (AA → A), now marked as superseded.
• Adds an April 7, 2023 entry noting the reversion to Level AA.
• Resolves Change log for Focus Visible SC #3468.

LIVE VIEW : https://deploy-preview-4668--wcag2.netlify.app/guidelines/

[netlify]

✅ Deploy Preview for wcag2 ready!

Name	Link
🔨 Latest commit	44249b0
🔍 Latest deploy log	https://app.netlify.com/projects/wcag2/deploys/68ef1d4007be890008a09ab6
😎 Deploy Preview	https://deploy-preview-4668--wcag2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[mbgower]

We do not normally record contents that change before the FPWD or between the FPWD and the publishing of the Rec that are not incorporated as part of the published rec (my emphasis in bold):

substantive changes incorporated into WCAG 2.2 since WCAG 2.1, as well as changes made to 2.2 since its original publication on 05 October 2023

Since the change in level of Focus Visible was reverted before publication date, I think neither entry is necessary.

As an example, the proposed Focus Appearance (Minimum) that was originally brought in as level AA is not recorded as moving to a AAA; we only record the addition and the name change. There is no mention of Focus Appearance (Enhanced) which also appeared in the August 2020 draft but was later removed.

[kfranqueiro]

The original issue reported in #3468 turns out to have been resolved by #4123. This is why you saw neither item in the change log and needed to add both, whereas the issue description indicated that one was present without the other. As Mike has explained, removing the two opposite change log items was our preferred resolution.

In the original issue, another point was raised RE the change log having no mention of 4.1.1 Parsing being marked as obsolete and removed, which first took effect in the 25 January 2023 Candidate Recommendation Draft publication. Would you be interested in repurposing this PR to add that to the change log instead?

Apologies for the confusion with the subsequent PR and the various comments across this PR and the associated issue.

[mbgower]

@venkatvemuri28 as mentioned in the issue, the 2.4.7 changes are not needed. Are you open to making this PR an update for 4.1.1's removal? Suggested text is:

2023-01-25: 4.1.1 Parsing marked as obsolete and removed.

[venkatvemuri28]

@venkatvemuri28 as mentioned in the issue, the 2.4.7 changes are not needed. Are you open to making this PR an update for 4.1.1's removal? Suggested text is:

2023-01-25: 4.1.1 Parsing marked as obsolete and removed.

Updated.

[mbgower]

Although this is a correction, the errata documentation files are not within the TR space, so I don't believe this can be considered normative, and have tagged it as such.

But I've just noticed that this PR does not change the errata files, but the change log, and that IS in the TR space. I've flagged this to be reviewed by the facilitators.