- From: Richard Schwerdtfeger <schwer@us.ibm.com>
- Date: Sat, 20 Sep 2014 23:10:53 -0500
- To: James Craig <jcraig@apple.com>
- Cc: PF <public-pfwg@w3.org>
- Message-ID: <OF6982218B.29E191D8-ON86257D5A.0016F4FF-86257D5A.0016F701@us.ibm.com>
+1 Rich Schwerdtfeger From: James Craig <jcraig@apple.com> To: Richard Schwerdtfeger/Austin/IBM@IBMUS Cc: PF <public-pfwg@w3.org> Date: 09/19/2014 09:34 PM Subject: Re: ACTION-1497 - Proposal for accessible description glossary definition On Sep 19, 2014, at 3:41 PM, Richard Schwerdtfeger <schwer@us.ibm.com > wrote: Accessible Description The accessible description provides help information about an interface element or how it is used in the form of a string. Probably no need for "in the form of a string." Each platform accessibility API provides an accessible description property. This is incorrect. I'd just remove the sentence. The value of the accessible description may be derived from a reference to content within a web page (visible or invisible) that is converted to a string. In some host languages the reference to the accessible description may be implied such as through the use of the <desc> element in SVG. Here's my draft two based on Rich's original: The accessible description provides help information about an interface element or about how it is used. The value of the accessible description may be derived from a reference to visible or invisible content within a web page, or the accessible description may be defined by host language features, such as the <desc> element in SVG.
Attachments
- image/gif attachment: graycol.gif
Received on Sunday, 21 September 2014 04:11:22 UTC