Rename 3.3.8 Accessible Authentication (add "(Minimum)")

[patrickhlauke]

I think this should cover all necessary changes to rename the SC. Also corrected a few minor errors/omissions in related understanding/techniques

See https://www.w3.org/2023/04/11-ag-minutes.html#resolution03

Closes #3087
Closes #3519

---

Preview | Diff

[patrickhlauke]

apologies @cwadamsoforacle ... only just seen #3132 ... but I think this one's more complete/supersedes it

[rachaelbradley]

I am not sure why we are seeing a dif for the wcag.json but otherwise these changes look good to merge.

[patrickhlauke]

I am not sure why we are seeing a dif for the wcag.json

I manually updated it as part of this PR (as I was unclear how this is generated)

[patrickhlauke]

@rachaelbradley assuming the .json thing is not a problem (cc @michael-n-cooper ?) do you mind merging this as well (unless this is controversial/touches on things it shouldn't)

[patrickhlauke]

@rachaelbradley @michael-n-cooper I removed the wcag.json file from this PR (assuming this would get regenerated if there were substantive changes to names of SCs etc)

@alastc @mbgower any chance to get this looked at/merged? it patches a few minor things left over when 3.3.8 was made "Minimum"

[mbgower]

I'm a little confused by this PR, to tell you the truth. I'm seeing the wording correct in the Understanding doc titles already.
I've made some basic comments on styling that can be applied to all documents, depending on the decision.

[patrickhlauke]

@mbgower ok, it seems that <title> and <h2>s get ignored and modified by XSLT (presumably?) scripting when this gets actually published. not sure why the original files actually had them then (probably easier while doing reviews I guess?) - you can see those long headings etc in other understanding docs in the repo, even right back to the 2.0 days ... see https://github.com/w3c/wcag/blob/main/understanding/20/abbreviations.html

so for internal consistency, possibly worth carrying on with this weird tradition (despite it not actually doing anything for publication), which this PR does... or we start stripping the source understanding files for 2.0, 2.1, and 2.2 to shorten all the <h2>s and <h3>s altogether...

the changes to links and techniques should be valid though

[patrickhlauke]

i'm less concerned about the <title> and <h2>/<h3> changes here (though for consistency it would be good if they were right), and more about the links that currently don't include the right/correct wording

[patrickhlauke]

ping once more, as currently there's some blatantly broken links (like the first one in https://www.w3.org/WAI/WCAG22/Understanding/accessible-authentication-enhanced.html#examples)

[fstrr]

I mentioned a couple of your typo PRs from 2022, a PR I have that, coincidentally, has the same fix in as this, and some other typo PRs in last Friday's backlog meeting. I'm hoping that'll get those merged in.

[mbgower]

I've put this in the WCAG 2.x project with a draft status to be reviewed. Or @alastc maybe this has already been sufficiently reviewed?

[patrickhlauke]

Would be great if this could be merged soon (before it diverges more from main changes), as currently we have 404 links (see #3519)