Skip to content

"Web" to "web", "Success criteria" to "success criteria" #4428

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 26 commits into
base: main
Choose a base branch
from

Conversation

patrickhlauke
Copy link
Member

@patrickhlauke patrickhlauke commented Jun 4, 2025

Also includes:

  • change "web based" to "web-based"
  • change "Web Unit" to "web unit"
  • change "Web Page" to "web page" (where appropriate)
  • a few straggler cases where lowercase "success criterion/criteria" was referring to specific ones, where we do want title case

Closes #4427

EDIT: see the matching #4461 that takes care of normative documents

…s criteria"

Also includes:

* change "web based" to "web-based"
* change "Web Unit" to "web unit"
* change "Web Page" to "web page" (where appropriate)

Closes #4427
Copy link

netlify bot commented Jun 4, 2025

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit 41e4405
🔍 Latest deploy log https://app.netlify.com/projects/wcag2/deploys/6840b7564d258000080d37cc
😎 Deploy Preview https://deploy-preview-4428--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.

Copy link

netlify bot commented Jun 4, 2025

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit f9f0cd6
🔍 Latest deploy log https://app.netlify.com/projects/wcag2/deploys/6840b7a720af8c0008d74bfa
😎 Deploy Preview https://deploy-preview-4428--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.

Copy link

netlify bot commented Jun 4, 2025

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit 161fd94
🔍 Latest deploy log https://app.netlify.com/projects/wcag2/deploys/6840b808525d1600081b591f
😎 Deploy Preview https://deploy-preview-4428--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.

Copy link

netlify bot commented Jun 4, 2025

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit b433d7e
🔍 Latest deploy log https://app.netlify.com/projects/wcag2/deploys/68593884f350b80008b47b53
😎 Deploy Preview https://deploy-preview-4428--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.

@patrickhlauke patrickhlauke changed the title Change "Web" to "web", two instances of "Success criteria" to "success criteria" Editorial: "Web" to "web", "Success criteria" to "success criteria" Jun 4, 2025
@kfranqueiro
Copy link
Contributor

We should skip the HTML files under conformance-challenges and requirements

@gundulaniemann
Copy link
Contributor

I learned that terms like "section" and "success criterion" are supposed to be written starting with a capital letter if a number follows, like "Section 4" or "Success Criterion 1.4.11".
Is that not true? (or has changed over the past decades?)

@patrickhlauke
Copy link
Member Author

I learned that terms like "section" and "success criterion" are supposed to be written starting with a capital letter if a number follows, like "Section 4" or "Success Criterion 1.4.11". Is that not true? (or has changed over the past decades?)

and are any of the changes here contradicting that?

actually, though i wasn't specifically looking for that case, it seems there's some cases in the current wording of certain files where it's right now lowercase when it shouldn't be, so will actually tackle that now here too

@patrickhlauke
Copy link
Member Author

@kfranqueiro

We should skip the HTML files under conformance-challenges and requirements

done

Copy link
Contributor

@mbgower mbgower left a comment

Choose a reason for hiding this comment

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

I flagged situations where "web" is being used as a noun, not an adjective.
I am fine with putting these lower case, but our style guidance is a little unclear in its wording:

lowercase except if proper noun meaning World Wide Web

To me, these seem to be examples where it is meant as a proper noun? Maybe our guidance is intended to mean 'only when it is used in the phrase World Wide Web'?

@kfranqueiro
Copy link
Contributor

I flagged situations where "web" is being used as a noun, not an adjective. I am fine with putting these lower case, but our style guidance is a little unclear in its wording:

lowercase except if proper noun meaning World Wide Web

To me, these seem to be examples where it is meant as a proper noun? Maybe our guidance is intended to mean 'only when it is used in the phrase World Wide Web'?

I checked with the WAI team RE the original rule this was inspired by, and lowercase is fine when web is used as a single-word noun, so I don't think we need to un-lowercase these.

From the WAI style guide:

web - lowercase when used by itself, including as an adjective (such as "web accessibility", "web page", "web application") and a noun ("making the web accessible")

This is also stated in the W3C style guide:

web (on its own): lowercase
Web (as part of a phrase): always capitalize in "World Wide Web", "World Wide Web Consortium", "Web Consortium"

@patrickhlauke
Copy link
Member Author

thanks for checking @kfranqueiro ... I'm glad, as the whole "the Web..." usage feels archaic (and always makes me think of "the Grid" https://www.youtube.com/watch?v=lILHEnz8fTk)

@patrickhlauke
Copy link
Member Author

patrickhlauke commented Jun 16, 2025

so, unless there's any more quirks/corrections ... i'm happy to split this into two (normative and non-normative) for the next meeting

edit: @kfranqueiro also "happy" to report that your new PR check for normative/non-normative mixed updates kicked in as it should https://github.com/w3c/wcag/actions/runs/15681204166/job/44172828352?pr=4428

@patrickhlauke patrickhlauke self-assigned this Jun 16, 2025
@bruce-usab bruce-usab self-assigned this Jun 17, 2025
@bruce-usab
Copy link
Contributor

It could be a separate PR, but "web unit" should be deleted or replaced with "web page". The term was a placeholder while AG wrestled with a putative last call working draft, see 2006 glossary.

Per @bruce-usab's comment, removed one instance altogether as it was unnecessary, and replaced another with "set of web pages" which is the correct term here that matches the wording of the related SC
@patrickhlauke
Copy link
Member Author

@bruce-usab killed off those two straggler "web unit"s

Any more? Otherwise, will proceed to disentangle and make two separate PRs out of this

@bruce-usab
Copy link
Contributor

Discussed on backlog call 6/20, and @patrickhlauke ready to close this out.

@patrickhlauke
Copy link
Member Author

@kfranqueiro I've split this out now, so the PR here is only non-normative. Normative changes are in #4461

@patrickhlauke patrickhlauke changed the title Editorial: "Web" to "web", "Success criteria" to "success criteria" Editorial (Non-normative): "Web" to "web", "Success criteria" to "success criteria" Jun 22, 2025
@mbgower mbgower changed the title Editorial (Non-normative): "Web" to "web", "Success criteria" to "success criteria" "Web" to "web", "Success criteria" to "success criteria" Jun 24, 2025
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.

Some missed editorial changes from the Dec 2024 WCAG publication
5 participants