Skip to content

Conversation

shawna-slh
Copy link
Contributor

@shawna-slh shawna-slh commented Apr 2, 2022

Copy link

netlify bot commented Oct 21, 2024

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...

QR Code

Use your smartphone camera to open QR code link.

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

@kfranqueiro kfranqueiro self-requested a review October 21, 2024 17:15
Copy link
Contributor

@dbjorge dbjorge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bruce-usab
Copy link
Contributor

Discussed on backlog call, add to CFC.

@patrickhlauke patrickhlauke changed the title link directly to new supplmental guidance link directly to new supplemental guidance Nov 8, 2024
@bruce-usab
Copy link
Contributor

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

@shawna-slh
Copy link
Contributor Author

/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:

  1. 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>.
  1. 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
Copy link
Contributor Author

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
Copy link
Contributor

mbgower commented Nov 15, 2024

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 mbgower added ErratumRaised Potential erratum for a Recommendation and removed Normative labels Nov 21, 2024
@mbgower
Copy link
Contributor

mbgower commented Nov 21, 2024

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

@detlevhfischer
Copy link
Contributor

detlevhfischer commented Nov 21, 2024

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
Copy link
Contributor

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
Copy link
Contributor Author

including the W3C's own translations of WCAG.

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

@bruce-usab
Copy link
Contributor

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

@mbgower
Copy link
Contributor

mbgower commented Nov 22, 2024

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
Copy link
Contributor

mbgower commented Dec 13, 2024

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.

@mbgower mbgower removed the Editorial label Feb 7, 2025
@mbgower mbgower added the Non-Normative Informative language in the specification or supporting materials label Apr 28, 2025
@mbgower mbgower merged commit 80ba129 into main Jun 27, 2025
6 checks passed
@mbgower mbgower deleted the new-supplemental-guidance branch June 27, 2025 19:05
kfranqueiro added a commit that referenced this pull request Jun 27, 2025
<!--
    This comment and the below content is programmatically generated.
    You may add a comma-separated list of anchors you'd like a
    direct link to below (e.g. #idl-serializers, #idl-sequence):

    Don't remove this comment or modify anything below this line.
    If you don't want a preview generated for this pull request,
    just replace the whole of this comment's content by "no preview"
    and remove what's below.
-->
***
<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 <[email protected]>
Co-authored-by: Kenneth G. Franqueiro <[email protected]>
(cherry picked from commit 80ba129)
kfranqueiro added a commit that referenced this pull request Jul 7, 2025
<!--
    This comment and the below content is programmatically generated.
    You may add a comma-separated list of anchors you'd like a
    direct link to below (e.g. #idl-serializers, #idl-sequence):

    Don't remove this comment or modify anything below this line.
    If you don't want a preview generated for this pull request,
    just replace the whole of this comment's content by "no preview"
    and remove what's below.
-->
***
<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 <[email protected]>
Co-authored-by: Kenneth G. Franqueiro <[email protected]>
(cherry picked from commit 80ba129)
mbgower added a commit that referenced this pull request Jul 15, 2025
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 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ErratumRaised Potential erratum for a Recommendation Non-Normative Informative language in the specification or supporting materials

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants