- From: Richards, Jan <jrichards@ocadu.ca>
- Date: Tue, 17 Apr 2012 21:11:10 +0000
- To: "w3c-wai-ua@w3.org" <w3c-wai-ua@w3.org>
My action on the last call was take another kick at the 712 can (perhaps making use of some ATAG2-derived wording): https://www.w3.org/WAI/UA/tracker/actions/712 Proposal: B.1.2.1 Support Repair by Assistive Technologies: If text alternatives for non-text content are missing or empty then both of the following are true: (Level A) (a) the user agent does not attempt to repair the text alternatives with text values that would also be available to assistive technologies. (b) the user agent makes metadata related to the non-text content available through the platform accessibility architecture. Note: Examples of text values that are also available to user agents, and should be avoided, include the filename, the file format, and generic phrases (e.g. "image"). Ed. See http://www.w3.org/TR/ATAG20/#sc_b233 Ed. This leaves open UAs generating captions for instance. 1.2.2 Repair Missing Structure: The user can specify whether or not the user agent should attempt to predict the following relationships from author-specified presentation attributes (i.e. position and appearance): (Level AAA) (a) Labels (b) Headers Cheers, Jan
Received on Tuesday, 17 April 2012 21:11:36 UTC