-
Notifications
You must be signed in to change notification settings - Fork 256
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
Harmonise wording for techniques checks/steps #3915
Harmonise wording for techniques checks/steps #3915
Conversation
177df34
to
f778431
Compare
Agree on the US-centric use of the |
Point to discuss in our next WCAG 2.x meeting then ... if we want to yoink |
I think aligning with the earlier examples is probably best (and the least amount of files changed), which is what you've done. That will also ruffle the least feathers. |
removed the word "both" as none of the other changes use this
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.
completed with a few changes
@shawna-slh Is there any style decision on use of the pound symbol (#) in front of ordered list references? |
Thanks for the ping @mbgower ! We don't currently have that in our Style guide. (I prefer without the # - yet don't have any support for or against that. update: I've noticed myself sometimes wanting to use "#" in such cases.) From a quick search, I don't find guidance in leading Style Guides -- so it needs more research. The good news is we have a new WAI staff person coming on the end of the month who will be great at citing sources for a decision. Are y'all comfortable leaving this issue open for a few weeks until we can get back to it? (p.s. thanks to @patrickhlauke I learned a new term, "octothorpe".) |
no rush from my perspective. I'd rather wait and then do all the changes in a oner, once we have a decision on the |
@shawna-slh Sorry, I missed those final comments when I brought this into our current review cycle. |
@tamsinewing555 will probably get to it within a few days :) |
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Currently, techniques use a mix of wording
If step X...
andIf check X...
, as well as a few outlier "If test procedure X...". Most prefix the step/check number with#
, but some don't. And conceptually, I think it makes more sense saying that a check is true/false, rather than a step being true/false.This PR tries to harmonise this, settling for
check
and adding missing#
(though, it has to be said, this use of the octothorpe is a bit US-centric, so maybe we want to harmonise to not having it?)