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

AUWG Action to add a note about flagging as auto-generated

From: Richards, Jan <jrichards@ocadu.ca>
Date: Wed, 27 Jun 2012 18:23:49 +0000
To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <0B1EB1C972BCB740B522ACBCD5F48DEB03AB56D6@ocadmail-maildb.ocad.ca>
Hi all,

I had an action to add a note about flagging as auto-generated...however, while adding that, I also want to propose combining B.2.3.2 and B.2.3.3 as follows (which I don't believe will result in a substantive change)...except possibly for (b). For (b), the WG should decide if we meant this as part of the original author control requirement.

B.2.3.2 Generation of Text Alternatives: If the authoring tool automates generation of text alternatives for non-text content, then the following are all true: (Level A) 
(a) Author Control: If authors are available (i.e. an authoring session is open), then authors have the opportunity to accept, modify, or reject the generated text alternatives prior to the alternatives being inserted into the content. [APPROVED]
(b) Identified as Auto-Generated: If authors are not available (i.e. an authoring session has ended), then the generated text alternative is identified such that authors have the opportunity to accept, modify, or reject the generated text alternative during a subsequent authoring session.
 (c) Contextual Information: Use of descriptive context information possessed by the authoring tool (e.g. that an image is a user's profile picture) is acceptable.
(d) Pattern Recognition: Use of the results of pattern recognition algorithms (e.g. Optical Character Recognition) is acceptable. 
(e) Relevant Properties: Use of text properties of the non-text content that have been defined as being intended for the provision of text alternatives (e.g., metadata "description" field) is acceptable.
(f) Irrelevant Properties: Use of text properties of the non-text content that have not been defined as being intended for the provision of text alternatives (e.g., file name, file format, date) is not acceptable.
(g) No Generic Strings: Use of generic text strings (e.g. "image") is not acceptable. 
Note: For automatic generation of other types of content, see success criteria B.1.1.1 and B.1.1.2.

Cheers,
Jan
Received on Wednesday, 27 June 2012 18:24:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 June 2012 18:24:18 GMT