"Web" to "web", "Success criteria" to "success criteria" #4428
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
patrickhlauke
changed the title
|
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 |
|
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 |
patrickhlauke
changed the title
…nto patrickhlauke-Web-web
mbgower
changed the title
| @@ -133,7 +133,7 @@ <h2>Examples of Images of Text</h2> | |||
| <h2>Resources for Images of Text</h2> | |||
| <ul> | |||
| <li><a href="https://developer.mozilla.org/en-US/docs/Learn_web_development/Core/Text_styling/Fundamentals">Fundamental text and font styling</a></li> | |||
| <li><a href="https://developer.mozilla.org/en-US/docs/Learn_web_development/Core/Text_styling/Web_fonts">MDN Web fonts</a></li> | |||
| <li><a href="https://developer.mozilla.org/en-US/docs/Learn_web_development/Core/Text_styling/Web_fonts">MDN: Web fonts</a></li> | |||
There was a problem hiding this comment.
Line 126 in previous file (images of text no exception) uses web (lowercase) fonts
There was a problem hiding this comment.
decide which one we should use. The title of the page itself is "Web fonts". Prefixing it with "MDN:" it probably makes sense to keep the uppercase "W" (so we need to change it in the no exception variant?)
There was a problem hiding this comment.
I'm inclined to leave this as is. It is the title of the page. I don't think we inflict our style on referenced material.
Update: the page is titled "Web fonts". The "MDN" has been prefixed for context. It doesn't look to me like we normally cite the source in our reference links, so my inclination is to removed "MDN"
| @@ -123,7 +123,7 @@ <h2>Resources for Images of Text (No Exception)</h2> | |||
|
|
|||
| <li> | |||
|
|
|||
| <a href="http://alistapart.com/article/cssatten">CSS Web fonts</a> | |||
| <a href="http://alistapart.com/article/cssatten">CSS web fonts</a> | |||
There was a problem hiding this comment.
Line 136 next in file list (images of text) uses Web (uppercase) fonts.
There was a problem hiding this comment.
ah, this is the "other" file. In this case makes sense to keep lowercase.
There was a problem hiding this comment.
isn't the title of this article "CSS @ Ten: The Next Big Thing"? Do we normally make up our own link names, or use the title of the source?
Also includes:
Closes #4427
EDIT: see the matching #4461 that takes care of normative documents