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

I wonder if it might make more sense to change the definition of presentation or none to cover this scenario

<p>I <img src="heart.gif" alt="love" role="none"> New York.</p>

to read "I love New York" instead of "I New York"

I think I would achieve that by not creating an accessible api node for the image, and just having a paragraph with text that reads "I love New York"

The glyph scenario is different, because it is text, and is often read as a single character.  But, do we need a role for that?  Would this work instead?

<p>I <span aria-label="love">♥</span> New York.</p>

Then, in the AAPI rendering, we would replace the ♥ with the string "love".  I'm not sure we need a role to do that.

-----Original Message-----
From: White, Jason J [mailto:jjwhite@ets.org] 
Sent: Tuesday, November 11, 2014 1:53 PM
To: Fred Esch; Matthew King
Cc: Steve Faulkner; James Craig; Joanmarie Diggs; W3C WAI Protocols & Formats
Subject: RE: First draft of ARIA 1.1. "text" role



>-----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 Wednesday, 12 November 2014 01:42:25 UTC