-
Notifications
You must be signed in to change notification settings - Fork 34
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
Add tags for WCAG 2.1 SC #166
Comments
This is on the list of things to do for WCAG 2.1. @awkawk , @alastc , @sharronrush , @bakkenb , @yatil, Please provide clear direction on specifically what is needed. My guess is:
Sharron & Eric, I think you were on the team who did the tags for 2.0. Do you have any hard or soft guidance on assigning tags for SCs? Is there someone else who was on that team that we might want to ask? Alastair & Andrew, Please confirm that AG will take this on. Thanks all! p.s. /me apparently can't assign awkawk & alastc |
Someone is going to need to explain what actually needs to be done: What are "dev", "int", "vis", and "con"? non-text-content: |
From the quickref, I'd guess they drive the left-nav:
But it would help to have a complete list of the possible values, and know whether the order matters? I.e. stick them on the end, or put in SC/POUR order? |
Urgh. Yes, @awkawk. I wanted to provide more context before pinging y’all.
The tags are free form (hence tags) and there is no complete list (we can add new) although EOWG bundled and simplified similar tags. The tag order in the document does not matter, they are sorted alphabetically when they are yielded in the Quickref. I can't give more context today as I’m supposed to be in a meeting right now. |
Task moved to https://github.com/w3c/wai-wcag-quickref/pull/181/files |
@jake-abma via email:
Actually, we don’t have any tags for the new WCAG 2.1 SCs. We should have tags for them.
(FTR: Tags can be added in this file: https://github.com/w3c/wai-wcag-quickref/blob/gh-pages/_data/tags-sc.yml)
The text was updated successfully, but these errors were encountered: