Backport October 2025 errata to 2.1#4716
Merged
Merged
Conversation
Apply proposed styles from #1130 (comment) Closes #1130 Live preview: https://deploy-preview-4590--wcag2.netlify.app/guidelines/#text-alternatives --------- Co-authored-by: Kenneth G. Franqueiro <kfranqueiro@users.noreply.github.com> Co-authored-by: Mike Gower <mikegower@gmail.com> (cherry picked from commit a3fc8d8)
…lowercase (#4461) Split out normative-only version of #4428 Relates to #4427 Changes unnecessary capitalisation of "Web" to "web", a few straggler cases where lowercase "success criterion/criteria" was referring to specific ones, where we do want title case --------- Co-authored-by: Mike Gower <mikegower@gmail.com> (cherry picked from commit bc709a4)
Fixes #4436. This fixes the markup for the first top-level note in the abbreviations definition to use a `div`, so that it can properly wrap the ordered list that is supposed to exist inside of it (as it did in [WCAG 2.0](https://www.w3.org/TR/WCAG20/#abbreviationsdef)). This also relegates the nested note to an inline annotation in a paragraph (suggested by Alastair), to avoid needing to worry about an unimplemented nesting edge case. The diff will be easier to view with whitespace ignored (`?w=1`). @netlify /guidelines/#dfn-abbreviations Co-authored-by: Patrick H. Lauke <redux@splintered.co.uk> Co-authored-by: Mike Gower <mikegower@gmail.com> (cherry picked from commit 172fe84)
…step to address `transaction-amount` issue in 1.3.5) (#4458) * this is not a success criterion - it should not contain normative *must* statements that create specific "new" requirements by the backdoor * the *must* here is contradicted in the sentence immediately following, where it starts with "Where applicable"? This is related to #4362 (comment) For info, this may also be relevant #3777 Co-authored-by: Mike Gower <mikegower@gmail.com> (cherry picked from commit 9e20466)
Noticed this as part of #4384 but then found a few more occurrences. The predominant use across all documents is "email" (not hyphenated), but there are a few stragglers that use "e-mail". Strangely, this is not covered in https://www.w3.org/guide/manual-of-style/ but in various places across W3C the non-hyphenated version is used. Note: this PR contains changes to both normative and non-normative documents Co-authored-by: Mike Gower <mikegower@gmail.com> (cherry picked from commit 0d7237b)
✅ Deploy Preview for wcag21 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
mbgower
approved these changes
Oct 31, 2025
bruce-usab
reviewed
Oct 31, 2025
Contributor
bruce-usab
left a comment
bruce-usab
left a comment
There was a problem hiding this comment.
Looks great! Here's a preview diff.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reminder: I plan to rebase-merge this to maintain 1 commit per erratum as well as the cherry-picking breadcrumb trail.
This backports the relevant parts of PRs referenced in #4659 from the latest CFC for errata, to the 2.1 guidelines.
All backports were performed with
git cherry-pick -xto include information on the originating commit.Additional notes:
Preview