- From: White, Jason J <jjwhite@ets.org>
- Date: Tue, 11 Nov 2014 21:53:11 +0000
- To: Fred Esch <fesch@us.ibm.com>, Matthew King <mattking@us.ibm.com>
- CC: Steve Faulkner <faulkner.steve@gmail.com>, James Craig <jcraig@apple.com>, Joanmarie Diggs <jdiggs@igalia.com>, W3C WAI Protocols & Formats <public-pfwg@w3.org>
>-----Original Message----- >From: Fred Esch [mailto:fesch@us.ibm.com] >Sent: Tuesday, November 11, 2014 4:45 PM >To: Matthew King >Cc: Steve Faulkner; James Craig; Joanmarie Diggs; W3C WAI Protocols & >Formats >Subject: Re: First draft of ARIA 1.1. "text" role > >+1 to what Matt said. >This has more down side than up side. Authors will be confused by >declaring text as text with a text alternative and/or aria-label. >Accessibility does not benefit from being this complex. > To clarify my position, the use cases are real and important. However, ARIA isn't the right means of addressing them, as it's too broad - it works via the accessibility interfaces and does not target, for example, speech output or braille output specifically or independently of one another. ________________________________ This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ________________________________
Received on Tuesday, 11 November 2014 21:53:42 UTC