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

RE: Draft checklist for accessibility of technology, comment by 17 March

From: Katie Haritos-Shea GMAIL <ryladog@gmail.com>
Date: Tue, 21 Feb 2017 10:34:07 -0500
To: "'Phill Jenkins'" <pjenkins@us.ibm.com>, <public-apa@w3.org>
Cc: "'Janina Sajka'" <janina@rednote.net>, "'Michael Cooper'" <cooper@w3.org>
Message-ID: <0b5301d28c57$f13e21b0$d3ba6510$@gmail.com>
Great comments Phill, thanks!


​​​​​* katie *


Katie Haritos-Shea 
Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)


Cell: 703-371-5545 |  <mailto:ryladog@gmail.com> ryladog@gmail.com | Oakton, VA |  <http://www.linkedin.com/in/katieharitosshea/> LinkedIn Profile | Office: 703-371-5545 |  <https://twitter.com/Ryladog> @ryladog

NOTE: The content of this email should be construed to always be an expression of my own personal independent opinion, unless I identify that I am speaking on behalf of Knowbility, as their AC Rep at the W3C - and - that my personal email never expresses the opinion of my employer, Deque Systems.


From: Phill Jenkins [mailto:pjenkins@us.ibm.com] 
Sent: Monday, February 20, 2017 5:53 PM
To: public-apa@w3.org
Cc: Janina Sajka <janina@rednote.net>; Michael Cooper <cooper@w3.org>
Subject: Re: Draft checklist for accessibility of technology, comment by 17 March


Some initial quick comments:

1. Add a note in the W3C Editor's Draft itself on how to submit comments, e.g send email to , public-apa@w3.org <mailto:public-apa@w3.org> , 

2. Define all acronyms, such as "AAPI", which I assume means "Accessibility API, Application Programming interface".  Why are there A-APIs and not just API's?

3. Add the end users responsibility for settings and configurations to the list, such as "...describes how technologies, content authoring, user agents and end user settings work together ...".

4. Add example of each checkpoint, such as from HTML 5.1, CSS or some web technology to which the checkpoint is referring.  

5. Love the acronym of the doc - FAST.

6. Change "Authors can ..." to "Technology specification provides for ..." in the Document semantics section.

7. Merge sections on Visual Media with Audio.

8. Add "Alternative user input modalities" to User Input section, such as Sign Language video input as an alternative to text keyboard, or gesture alternative to mouse clicks, etc.

Phill Jenkins
+1 512-791-4517 mobile
pjenkins@us.ibm.com <mailto:pjenkins@us.ibm.com> 
Senior Engineer & Accessibility Executive
IBM Research Accessibility
 <http://www.ibm.com/able> ibm.com/able
 <http://www.facebook.com/IBMAccessibility> facebook.com/IBMAccessibility
 <https://twitter.com/IBMAccess> twitter.com/IBMAccess
 <http://ageandability.com/> ageandability.com

From:        Janina Sajka <janina@rednote.net <mailto:janina@rednote.net> >
To:        w3c-wai-ig@w3.org <mailto:w3c-wai-ig@w3.org> , chairs@w3.org <mailto:chairs@w3.org> , spec-prod@w3.org <mailto:spec-prod@w3.org> , public-html@w3.org <mailto:public-html@w3.org> , www-style@w3.org <mailto:www-style@w3.org> , public-svg-wg@w3.org <mailto:public-svg-wg@w3.org> , public-webauthn@w3.org <mailto:public-webauthn@w3.org> , www-international@w3.org <mailto:www-international@w3.org> , www-tag@w3.org <mailto:www-tag@w3.org> , public-digipub-ig@w3.org <mailto:public-digipub-ig@w3.org> , public-payments-wg@w3.org <mailto:public-payments-wg@w3.org> , public-secondscreen@w3.org <mailto:public-secondscreen@w3.org> , w3t@w3.org <mailto:w3t@w3.org> , public-wot-wg@w3.org <mailto:public-wot-wg@w3.org> 
Date:        02/20/2017 03:55 PM
Subject:        Draft checklist for accessibility of technology, comment by 17 March


The Accessible Platform Architectures (APA) Working Group is developing a checklist to guide specification developers in the features needed to ensure their technology enables accessibility to people with disabilities. This is to address not only content markup languages that describe primary content, but also styling languages that impact presentation, APIs that enable manipulation and data interchange, and protocols that tie it all together. Like similar checklists addressing Internationalization, Privacy, and Security, this would enable self-review as a first stage in the "horizontal review" process of ensuring W3C specifications have broad applicability. Using it should reduce effort in providing basic accessibility coverage, and it will aid early identification of more complex issues that may need direct exploration with the APA WG.

The draft checklist is available at:

 <http://w3c.github.io/pfwg/wtag/checklist.html> http://w3c.github.io/pfwg/wtag/checklist.html

This draft is not yet complete, in particular expanded details about each checklist item are yet to be added, but it shows how APA approaches its horizontal review responsibility. We request review from a variety of stakeholders, including accessibility groups who identify user needs and specification developers who might use this checklist.

The following questions may help guide your review:

* Is it understandable how these checkpoints apply to technologies?
* Is this format useful in considering accessibility needs during technology development?
* Would this guidance help inform your interaction with the APA WG on horizontal review?
* Are the checkpoints relevant to *specifications*?
* Are there any missing types of issues specs might have that impact accessibility?
* Within each section, are there any missing checkpoints?
* Is the overall order logical?

We appreciate review of this first version by 17 March 2017, so the APA WG can incorporate feedback in time for an updated draft in April. Comments can be sent:

* by email to public-apa@w3.org <mailto:public-apa@w3.org> ,
* as an issue at  <https://github.com/w3c/pfwg/issues> https://github.com/w3c/pfwg/issues,
* or as pull requests against the master branch at  <https://github.com/w3c/pfwg/blob/master/wtag/checklist.html> https://github.com/w3c/pfwg/blob/master/wtag/checklist.html

Janina Sajka, APA WG Chair
Michael Cooper, APA WG W3C Staff Contact
Received on Tuesday, 21 February 2017 15:34:45 UTC

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