WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Fixing WAI's writing styleDoes WCAG require ...

for

From: Andrew Kirkpatrick
Date: Dec 1, 2015 8:22AM

>As Chaals stated, you should file bugs against the materials. While
>the spec itself is not going to be changed anytime soon (sad, IMO) you
>can still contribute to the numerous additional materials.
>
>WCAG does (most of) its work out in the open. You merely need to take
>the time to identify specific shortcomings and log them as issues in
>their Github repository at https://github.com/w3c/wcag/issues
>...
>As Chaals said: "Every "W3C Recommendation" has a section called
>"Status of This Document" right near the front, that says how to file
>comments on it. Please do so."

I'm writing in response to this thread as one of the co-chairs of WCAG, and I do agree that there is plenty of room for improvement in the WCAG techniques and understanding documents and in the WCAG 2.0 standard. As Karl and others have indicated, please do submit comments.

If anyone submits a comment via the <EMAIL REMOVED> email address or submits an issue via github, we will log any email comment as a github issue and then we will work to resolve the issue. Sometimes the resolution is easy (bad links, typos), sometimes not (requests for interpretation for a new situation, ideas for new techniques, blanket condemnation of the original writing style). In the latter case, suggestions may be added to a backlog list or to the "post WCAG 2.0" list (for suggestions that exceed the scope of the existing standard but that we want to capture for future extensions or revisions).

There are many opinions and we are happy to listen to and work with anyone who is interested enough to weigh in. Please do send in comments and questions via email or GitHub.

Thanks,
AWK


Andrew Kirkpatrick
Group Product Manager, Adobe Accessibility
Co-Chair, Web Content Accessibility Guidelines Working Group