link directly to new supplemental guidance by shawna-slh · Pull Request #2296 · w3c/wcag

shawna-slh · 2022-04-02T15:38:10Z

netlify · 2024-10-21T16:58:03Z

✅ Deploy Preview for wcag2 ready!

Name	Link
🔨 Latest commit	`559c354`
🔍 Latest deploy log	https://app.netlify.com/projects/wcag2/deploys/685eeb2c67af6b00082d7224
😎 Deploy Preview	https://deploy-preview-2296--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.

dbjorge

LGTM

bruce-usab · 2024-10-25T15:08:37Z

Discussed on backlog call, add to CFC.

bruce-usab · 2024-11-08T23:52:59Z

Discussed on TF call 11/8, might be OBE. @kfranqueiro will check in again with @shawna-slh

Co-authored-by: Mike Gower <mikegower@gmail.com>

shawna-slh · 2024-11-09T15:05:42Z

/me looks up OBE ... officer (of the Order) of the British Empire / Order of the British Empire ... out-of-body experience ... overcome / overtaken by events

After revision this PR now:

changes the link directly to the Supplemental Guidance About page, which includes important context such as "Following this guidance is not required to meet WCAG. And, we encourage you to follow this guidance in order meet more user needs."

the current link would take them 3 steps to get there (which is on purpose for other use cases, but would be bad for this use case... though we could add a new section just for this use case if there is a reason not to update the link...)
if it's better to make a bit less of a change, the link could include the rest of the phrase: <a href="https://www.w3.org/WAI/WCAG2/supplemental/about/">supplemental guidance on improving inclusion for people with disabilities, including cognitive and learning disabilities, low vision, and more</a>.

fixes sentence structure and PWD terminology

Neither are dangerously wrong if not fixed. I happily leave it to others to determine the appropriateness for this change or not. :)

fyi brief history: we planned to do something like 'supplemental guidance' but didn't know if we would end up calling it that. the link used to go to a section in WCAG 2 Overview that explained that some kind of supplemental guidance was coming. after it existed and when we updated WCAG 2 Overview and The WCAG 2 Documents, that was changed. (to be honest, we forgot about the link from WCAG)

shawna-slh · 2024-11-09T15:19:21Z

related comment that gets hidden in resolved thread:

alastc
There was (and is) and agreement to link to the COGA supplemental guidance, but I think that's taken care of in the "Layers of guidance" section in WCAG.

shawna-slh
Ah, I didn't realize that a link to [Making Content Usable for People with Cognitive and Learning Disabilities] had been added to that section (last paragraph).
Is it too late to fix the sentence structure? (especially since it's about cognitive disabilities, the irony is unfortunate :) @iadawn fyi

Should we create a new issue for fixing that sentence structure? Or should I just let it go? (I'm fine doing either.)

mbgower · 2024-11-15T16:34:19Z

Should we create a new issue for fixing that sentence structure? Or should I just let it go? (I'm fine doing either.)

@shawna-slh If you want to fix it, create a new issue, otherwise you can just let it go :)

mbgower · 2024-11-21T00:31:35Z

I removed the Normative label since this is clearly part of the introduction and is clearly marked as being non-normative.

detlevhfischer · 2024-11-21T08:39:47Z

One probably minor problem is that the link promises more than the page linked to can hold. There is, for example, currently no low vision guidance. May suggest adapting the link text.

WilcoFiers · 2024-11-21T10:31:14Z

I don't think this is worth publishing an errata for. Don't forget that this link will forever be in use in all the thousands of copies that exist of WCAG, including the W3C's own translations of WCAG.

shawna-slh · 2024-11-22T16:40:41Z

including the W3C's own translations of WCAG.

just fyi, we are pursuing updates of WCAG translations when appropriate

bruce-usab · 2024-11-22T17:58:20Z

Discussed on TF call 11/22 and all parties satisfied that we have correct link and that this can be included with republication.

mbgower · 2024-11-22T19:17:43Z

Discussed on TF call 11/22 and all parties satisfied that we have correct link and that this can be included with republication.

In the context of this PR, we agreed that this is non-normative and so can be addressed through errata; in fact, that it does not require a republication or CFC process.

mbgower · 2024-12-13T22:03:18Z

Moving to Errata for CFC, since that is our defined column for errata, but note that this does not need to go to CFC. It is non-normative. Intend to hold it in that column until we resolve the errata and publishing cadence with Faciltators.

*** <a href="https://pr-preview.s3.amazonaws.com/w3c/wcag/pull/2296.html" title="Last updated on Nov 9, 2024, 2:26 PM UTC (1e590d8)">Preview</a> | <a href="https://pr-preview.s3.amazonaws.com/w3c/wcag/2296/84d1219...1e590d8.html" title="Last updated on Nov 9, 2024, 2:26 PM UTC (1e590d8)">Diff</a> --------- Co-authored-by: Mike Gower <mikegower@gmail.com> Co-authored-by: Kenneth G. Franqueiro <kfranqueiro@users.noreply.github.com> (cherry picked from commit 80ba129)

This PR adds four changes to the list of errata for WCAG 2.2 and 2.1 TR documents. The changes are from: #4256, #4040, #4165, and #2296. Three of the changes are to notes and examples in the specification, which are non-normative according to the [5.1 Interpreting Normative Requirements](https://www.w3.org/TR/WCAG22/#interpreting-normative-requirements). One of the changes is a normative change, restricted to correcting the alphabetical order for the list of defined terms. As such, it falls under [Changes that do not functionally affect interpretation of the document](https://www.w3.org/policies/process/#correction-classes). Previews: [2.1](https://deploy-preview-4370--wcag2.netlify.app/errata/21#since-current), [2.2](https://deploy-preview-4370--wcag2.netlify.app/errata/22#since-current) --------- Co-authored-by: Kenneth G. Franqueiro <kfranqueiro@users.noreply.github.com>

shawna-slh added 3 commits April 2, 2022 10:38

link directly to new supplmental guidance

cf795fb

(typo fix)

29e5544

update links

6497f97

kfranqueiro self-requested a review October 21, 2024 17:15

kfranqueiro approved these changes Oct 21, 2024

View reviewed changes

dbjorge approved these changes Oct 25, 2024

View reviewed changes

patrickhlauke reviewed Oct 25, 2024

View reviewed changes

Comment thread guidelines/index.html Outdated

patrickhlauke changed the title ~~link directly to new supplmental guidance~~ link directly to new supplemental guidance Nov 8, 2024

patrickhlauke assigned alastc Nov 8, 2024

bruce-usab added Normative Editorial labels Nov 8, 2024

Update guidelines/index.html

1e590d8

Co-authored-by: Mike Gower <mikegower@gmail.com>

mbgower assigned iadawn Nov 15, 2024

mbgower added ErratumRaised Potential erratum for a Recommendation and removed Normative labels Nov 21, 2024

bruce-usab approved these changes Nov 21, 2024

View reviewed changes

mbgower removed the Editorial label Feb 7, 2025

Merge branch 'main' into new-supplemental-guidance

4ce8050

mbgower added the Non-Normative Informative language in the specification or supporting materials label Apr 28, 2025

alastc mentioned this pull request May 8, 2025

Add new errata to both 2.1 and 2.2 #4370

Merged

Merge branch 'main' into new-supplemental-guidance

559c354

mbgower merged commit 80ba129 into main Jun 27, 2025

mbgower deleted the new-supplemental-guidance branch June 27, 2025 19:05

github-project-automation Bot moved this from Errata for quarterly refresh to Done in WCAG 2.x Jun 27, 2025

jamesreimer mentioned this pull request Sep 2, 2026

Define bounded authoring of the Web Accessibility Standard jamesreimer/standards-templates#17

Closed

6 tasks

Conversation

shawna-slh commented Apr 2, 2022 • edited by pr-preview Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

netlify Bot commented Oct 21, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for wcag2 ready!

Uh oh!

dbjorge left a comment

Choose a reason for hiding this comment

Uh oh!

bruce-usab commented Oct 25, 2024

Uh oh!

Uh oh!

bruce-usab commented Nov 8, 2024

Uh oh!

shawna-slh commented Nov 9, 2024

Uh oh!

shawna-slh commented Nov 9, 2024

Uh oh!

mbgower commented Nov 15, 2024

Uh oh!

mbgower commented Nov 21, 2024

Uh oh!

detlevhfischer commented Nov 21, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

WilcoFiers commented Nov 21, 2024

Uh oh!

shawna-slh commented Nov 22, 2024

Uh oh!

bruce-usab commented Nov 22, 2024

Uh oh!

mbgower commented Nov 22, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mbgower commented Dec 13, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

10 participants

shawna-slh commented Apr 2, 2022 •

edited by pr-preview Bot

Loading

netlify Bot commented Oct 21, 2024 •

edited

Loading

detlevhfischer commented Nov 21, 2024 •

edited

Loading

mbgower commented Nov 22, 2024 •

edited

Loading