Re: First draft of ARIA 1.1. "text" role

Hey Steve.

On 11/11/2014 06:29 AM, Steve Faulkner wrote:
> 
> On 11 November 2014 02:38, Joanmarie Diggs <jdiggs@igalia.com
> <mailto:jdiggs@igalia.com>> wrote:
> 
>     confuses me. Unlike the first set of examples, there is no actual
>     (rendered) text there because the element is an image. So why should
>     this non-textual object be exposed to accessibility APIs as plain text?
> 
> 
> Hi JoanMarie,
> 
> <img alt="some text">
> 
> I think, is one of the main use cases for role=text, what it does is
> ensure that when a developer (as if often the case unfortunately) uses
> images of text/symbols/icons to convey meaning, through the use of
> role=text the textual information is conveyed without the role=img
> noise. The fact that an image is being used to provide it is an artifact
> of design/technology constraints rather than being important information
> (role=img) that is conveyed. In these cases, the medium is not the message.

Understood. But to me, the solution to the problem means "don't present
'image'". It does not mean "present 'text'".

When you tell an assistive technology "this object is text," I think
it's reasonable for that assistive technology to assume that there is
text present, that the platform's accessible text interface is
implemented, etc. And that's not the case here.

--joanie

Received on Tuesday, 11 November 2014 12:45:17 UTC