W3C home > Mailing lists > Public > w3c-wai-au@w3.org > January to March 2012

RE: ATAG2 Action item re: documenting features

From: Richards, Jan <jrichards@ocadu.ca>
Date: Thu, 12 Jan 2012 16:36:47 +0000
To: "Boland Jr, Frederick E." <frederick.boland@nist.gov>
CC: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <0B1EB1C972BCB740B522ACBCD5F48DEB039FABAE@ocadmail-maildb.ocad.ca>
Hi Tim,

> Minor Questions: Do the categories taken together cover all possible features of the authoring tool?  

I think so, because we start with the inclusive "For each authoring tool feature" and then carve out the exceptions. I suppose the question for the group is really, should there be any other exceptions?

> Do they overlap at all! 

Yes - a feature might be explained in the UI and the documentation, so it's an inclusive OR.

> I assume for c that the feature (service) is explained (documented) elsewhere?  

One would hope, but even if it isn't on a particular platform, it's an issue of division of responsibility. Applications shouldn't have to document their platforms.

> Also what constitutes a sufficient explanation for testing purposes?

That would be hard to specify normatively. We can provide a bit more information in the informative intent. BTE: There similar requirement in the new draft Section 508 refresh (http://www.access-board.gov/sec508/refresh/draft-rule.htm#_Toc310327603)

Cheers,
Jan
-- 
(Mr) Jan Richards, M.Sc.
jrichards@ocadu.ca | 416-977-6000 ext. 3957 | fax: 416-977-9844
Inclusive Design Research Centre (IDRC) | http://idrc.ocad.ca/
Faculty of Design | OCAD University




From: Boland Jr, Frederick E. [mailto:frederick.boland@nist.gov] 
Sent: January 12, 2012 9:52 AM
To: Richards, Jan
Cc: w3c-wai-au@w3.org
Subject: RE: ATAG2 Action item re: documenting features

Thanks - good work

Minor Questions: Do the categories taken together cover all possible features of the authoring tool?   Do they overlap at all! I assume for c that the feature (service) is explained (documented) elsewhere?   Also what constitutes a sufficient explanation for testing purposes?

Tim Boland

From: Richards, Jan [mailto:jrichards@ocadu.ca] 
Sent: Wednesday, January 11, 2012 11:17 PM
To: w3c-wai-au@w3.org
Subject: ATAG2 Action item re: documenting features

On Monday's call I took this action:
"JR to To propose something for A.4.2.1 that includes user interactive features and a note on platform conventions being documented elsewhere"

Here's my proposal (affecting both A.4.2.1 and A.4.2.2). I've tried to move to "explain" from "document" to avoid appearing to require a formal help system:
A.4.2.1 Explain Accessibility Features:  For each authoring tool feature that is used to meet Part A of ATAG 2.0, at least one of the following is true:
(a) Explained in documentation: use of the feature is explained in the authoring tool's documentation; or
(b) Explained in interface: use of the feature is explained in the user interface; or
(c) Platform service: the feature is a service provided by an underlying platform; or
(d) Not used by authors: the feature is not used directly by authors (e.g., passing information to a platform accessibility service)
Note: The accessibility of the documentation is covered by Guideline A.1.1 and Guideline A.1.2.

A.4.2.1 Explain All Features:  For each authoring tool feature, at least one of the following is true:
(a) Explained in documentation: use of the feature is explained in the authoring tool's documentation; or
(b) Explained in interface: use of the feature is explained in the user interface; or
(c) Platform service: the feature is a service provided by an underlying platform; or
(d) Not used by authors: the feature is not used directly by authors (e.g., passing information to a platform accessibility service)
Note: The accessibility of the documentation is covered by Guideline A.1.1 and Guideline A.1.2.


EXISTING TEXT:
A.4.2.1 Document Accessibility Features:  All features of the authoring tool @@that are used to must be present to meet Part A of ATAG 2.0 (e.g., keyboard shortcuts, text search) are documented. (Level A)
Note: The accessibility of the documentation is covered by Guideline A.1.1 and Guideline A.1.2.

A.4.2.2 Document All Features: The authoring tool includes documentation for its author-level user interface features. (Level AA)
Note: The accessibility of the documentation is covered by Guideline A.1.1 and Guideline A.1.2.

Cheers,
Jan

(MR) JAN RICHARDS
PROJECT MANAGER
INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)

T 416 977 6000 x3957
F 416 977 9844
E jrichards@ocadu.ca

Twitter @OCAD
Facebook www.facebook.com/OCADUniversity 

OCAD UNIVERSITY
205 Richmond Street West, 2nd Floor, Toronto, Canada  M5V 1V3
www.ocadu.ca
idrc.ocadu.ca
Received on Thursday, 12 January 2012 16:38:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 12 January 2012 16:38:48 GMT