Skip to content

Don't just refer to SCs by their number, don't use colon#4939

Merged
patrickhlauke merged 9 commits intomainfrom
patrickhlauke-dont-use-sc-number-references-only
Mar 9, 2026
Merged

Don't just refer to SCs by their number, don't use colon#4939
patrickhlauke merged 9 commits intomainfrom
patrickhlauke-dont-use-sc-number-references-only

Conversation

@patrickhlauke
Copy link
Copy Markdown
Member

@patrickhlauke patrickhlauke commented Feb 17, 2026

For consistency:

  • don't use a colon between the SC number and its title - my main reason is that it looks somehow "stilted", and when used in a sentence it can end up "fighting" with the punctuation of the actual sentence (particularly when not part of a link), and just makes it harder to parse
  • 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.

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

@patrickhlauke patrickhlauke added Editorial Normative Non-Normative Informative language in the specification or supporting materials labels Feb 17, 2026
@netlify
Copy link
Copy Markdown

netlify bot commented Feb 17, 2026

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit dec74fe
🔍 Latest deploy log https://app.netlify.com/projects/wcag2/deploys/69a9dbf4acb9880008f9157a
😎 Deploy Preview https://deploy-preview-4939--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 force-pushed the patrickhlauke-dont-use-sc-number-references-only branch 2 times, most recently from 821ccad to e1bbe4f Compare February 17, 2026 23:45
For consistency:

* don't use a colon between the SC number and its title
* don't just refer to SCs by number alone
@patrickhlauke patrickhlauke force-pushed the patrickhlauke-dont-use-sc-number-references-only branch from e1bbe4f to 719d242 Compare February 17, 2026 23:48
@shawna-slh
Copy link
Copy Markdown
Contributor

+1 to no colon to match the punctuation in the WCAG standard; for example:

Success Criterion 1.1.1 Non-text Content

@kfranqueiro
Copy link
Copy Markdown
Contributor

kfranqueiro commented Feb 19, 2026

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 guidelines/ changes to a separate one. (If you want, I can help to do that.)

@bruce-usab
Copy link
Copy Markdown
Contributor

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.

@patrickhlauke
Copy link
Copy Markdown
Member Author

patrickhlauke commented Feb 20, 2026

with thanks to @kfranqueiro the normative part is now split out into #4947

moving this and the other one to "Ready for approval"

@patrickhlauke patrickhlauke self-assigned this Feb 20, 2026
@kfranqueiro kfranqueiro added Techniques Understanding and removed Non-Normative Informative language in the specification or supporting materials labels Feb 20, 2026
Copy link
Copy Markdown
Contributor

@bruce-usab bruce-usab left a comment

Choose a reason for hiding this comment

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

I didn't realize how much I disliked the colons until you got rid of them! Thank you!

@bruce-usab
Copy link
Copy Markdown
Contributor

I tagged as “substantive” to highlight that there is a bit more to go through than is typical for editorial changes.

@patrickhlauke patrickhlauke merged commit 807a6c2 into main Mar 9, 2026
8 checks passed
@patrickhlauke patrickhlauke deleted the patrickhlauke-dont-use-sc-number-references-only branch March 9, 2026 16:29
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.

5 participants