Don't just refer to SCs by their number, don't use colon - #4939
Conversation
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
821ccad to
e1bbe4f
Compare
For consistency: * don't use a colon between the SC number and its title * don't just refer to SCs by number alone
e1bbe4f to
719d242
Compare
|
+1 to no colon to match the punctuation in the WCAG standard; for example:
|
|
I did a pass through the PR, found and fixed additional typos, made a couple of tweaks to front-load expansions found multiple times within the same paragraph, and removed colons added within the build system. I do think we should split this; IMO it makes sense to keep the informative changes in this PR since that applies to the majority of changes, and move the |
|
Reviewed on TF call 20 Feb. Consensus on Ready for approval, but needs to be split into two PRs to address TR space files separately. |
|
with thanks to @kfranqueiro the normative part is now split out into #4947 moving this and the other one to "Ready for approval" |
bruce-usab
left a comment
There was a problem hiding this comment.
I didn't realize how much I disliked the colons until you got rid of them! Thank you!
|
I tagged as “substantive” to highlight that there is a bit more to go through than is typical for editorial changes. |
Normative counterpart to #4939 > For consistency: > > * don't just refer to SCs by number alone - (at least for first mentions in a document) this helps documents be more readable without assuming that the reader walks around remembering what each SC number is/what criterion it actually represents. Co-authored-by: Kenneth G. Franqueiro <kfranqueiro@users.noreply.github.com>
For consistency:
It would be good to get something decided/officially mentioned in the style guide (particularly for the use of
:or not)EDIT: normative changes split into #4947