-
Notifications
You must be signed in to change notification settings - Fork 94
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
Specification needs to be compliant with WCAG 2.0 #118
Comments
I will do a first pass through applying these guidelines this |
(WIP - flagged with ** things I'm not sure about, input gratefully received)
|
(Will complete this audit closer to CR, but if anyone knows which of the markup/structure related things respec covers automatically please say so) |
Unfortunately, I don't know... looking now in ReSpec's documentation... |
Still waiting on CR... |
I have done an WCAG2 analysis on the document. The readability scores are borderline... requiring ~11 years of education (or 7th grade US level) to understand. That said, we pass all checks. Closing. |
We are required to ensure that the document, when published, satisfies the WCAG 2.0 requirements. See https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0
At a minimum this must be done before CR publication. If done earlier, it needs to be kept up to date. While technically editorial, this is a non-trivial piece of work, especially as we add diagrams, so additional volunteers are encouraged.
The text was updated successfully, but these errors were encountered: