W3C home > Mailing lists > Public > public-apa@w3.org > January 2017

Review draft of Web Technology Accessibility Guidelines checklist

From: Michael Cooper <cooper@w3.org>
Date: Fri, 6 Jan 2017 17:36:15 -0500
To: Accessible Platform Architectures Working Group <public-apa@w3.org>
Message-ID: <90b9dac8-450f-a9f1-90b7-302f6f90cab7@w3.org>
I have a draft of the Web Technology Accessibility Guidelines checklist 
that I think is credibly ready for review:


The structure is a table with several sections for different features 
technologies might provide. In each of those is a set of checklist items 
spec developers can check against their own technology. There are also 
columns for further explanation and references though those are mostly 
blank at this point.

I think this is starting to look semi complete. Some review questions I 
would ask are:

  * Are there any missing sections, i.e., types of issues specs might
    have that impact accessibility?
  * Within each section, are there any missing checkpoints?
  * Are there checkpoints that aren't relevant to *specifications* (even
    if they're relevant to authors, user agents, etc.)?
  * Do checkpoints belong in other sections?
  * Is the overall order logical?

I think the wording in this version is more oriented at ourselves, 
rather than at people who might actually use this checklist. That is, it 
uses accessibility jargon, and needs significant rephrasing to help non 
accessibility specialists who would be asked to use this checklist. I 
think this version is clear enough for our own review however.

For reference, some other checklists that I'm drawing some ideas from, 
and may converge with more down the road:

  * https://www.w3.org/International/techniques/developing-specs
  * http://gregnorc.github.io/ping-privacy-questions/
  * https://www.w3.org/TR/security-privacy-questionnaire/

Received on Friday, 6 January 2017 22:36:08 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:02 UTC