W3C home > Mailing lists > Public > public-aria@w3.org > February 2016

Re: role="text" and text frames

From: James Teh <jamie@nvaccess.org>
Date: Wed, 10 Feb 2016 11:47:29 +1000
To: Rich Schwerdtfeger <richschwer@gmail.com>, Matt King <a11ythinker@gmail.com>
Cc: Joseph Scheuhammer <clown@alum.mit.edu>, Cynthia Shelly <cyns@microsoft.com>, Alexander Surkov <surkov.alexander@gmail.com>, Rich Schwerdtfeger <schwer@us.ibm.com>, wai-xtech@w3.org, public-aria@w3.org
Message-ID: <56BA96B1.5050700@nvaccess.org>
On 10/02/2016 2:52 AM, Rich Schwerdtfeger wrote:
> If we make this the text role the AT should have enough knowledge that 
> it is either a raster image or a vector drawing
How does it get this knowledge? By looking at the role of ancestors? 
Certainly, the static text role isn't sufficient to communicate this.

> Static text is important in that it would allow the text to be read to 
> the user when placed in a line of text. Text frame would not work that 
> way. It would be treated as a separate entity much the same way we 
> handle TDs when role=“presentation”  is applied to a  table.
I disagree. As I've pointed out before, text frame (at least as it's 
used in web browsers today) shouldn't be treated as a block element; 
it's actually inline. ATs might *choose* to present it on a separate 
line, but that's a choice, not something inherent in the role. Take the 
following example:

|<p>foo <span onClick=";">bar</span> bas</p>|

Firefox exposes "bar" with a role of text frame, but it's still very 
much inline and can thus be rendered on the same line unless an AT 
chooses to render it separately for UX reasons.


James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: jamie@nvaccess.org
Received on Wednesday, 10 February 2016 01:47:53 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:19 UTC