Skip to content

Conversation

shawna-slh
Copy link
Contributor

@kfranqueiro
Copy link
Contributor

Checking on this old PR which targets the wcag20 folder which currently doesn't affect builds; if we want to make this change, we should probably also update the same wording in understanding/20/use-of-color.html.

@bruce-usab
Copy link
Contributor

Discussed and had consensus on backlog call 10/25.

@kfranqueiro kfranqueiro self-assigned this Jan 16, 2025
Copy link

netlify bot commented Feb 13, 2025

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit 82437da
🔍 Latest deploy log https://app.netlify.com/sites/wcag2/deploys/67ec086e99bf610008765174
😎 Deploy Preview https://deploy-preview-2143--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 site configuration.

@kfranqueiro
Copy link
Contributor

I have ported this PR's original change to where the same wording occurred under the understanding/ folder.

My question to the Backlog TF is: do we still want the update under wcag20/, given that we do not perform any builds of content under that folder? Or should we only update the content under understanding/?

…olorblind"

This reverts commit 286a0d9.

Discussed with Backlog TF on 2025-02-14, we would prefer to
only change files under understanding/ (not wcag20/) at this point.
@kfranqueiro
Copy link
Contributor

RE my previous question: discussed with backlog TF on 2025-02-14, and there was agreement to remove the old change under /wcag20/ to avoid confusion and noise. I have updated the PR accordingly so it only applies the equivalent update under /understanding/.

@mbgower mbgower changed the title update terminology per https://www.w3.org/WAI/EO/wiki/Style#colorblind update terminology: color blind Mar 10, 2025
@mbgower mbgower merged commit 6248dfb into main Apr 1, 2025
1 check passed
@mbgower mbgower deleted the colorblind-update branch April 1, 2025 15:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants