-
Notifications
You must be signed in to change notification settings - Fork 292
"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
base: main
Are you sure you want to change the base?
Conversation
…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
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…nto patrickhlauke-Web-web
We should skip the HTML files under |
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". |
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 |
done |
There was a problem hiding this 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'?
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:
This is also stated in the W3C style guide:
|
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) |
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 |
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
@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 |
Discussed on backlog call 6/20, and @patrickhlauke ready to close this out. |
Keep this PR non-normative only
@kfranqueiro I've split this out now, so the PR here is only non-normative. Normative changes are in #4461 |
…nto patrickhlauke-Web-web
Also includes:
Closes #4427
EDIT: see the matching #4461 that takes care of normative documents