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

Re: role="text" and text frames

From: James Teh <jamie@nvaccess.org>
Date: Wed, 20 Jan 2016 08:26:12 +1000
To: Richard Schwerdtfeger <schwer@us.ibm.com>, surkov.alexander@gmail.com
Cc: wai-xtech@w3.org, public-aria@w3.org
Message-ID: <569EB804.2050600@nvaccess.org>
I'm even more convinced that static text is the more correct role 
recently, especially because ATK made the same decision.

That said, I'd argue that IA2_ROLE_TEXTFRAME should never be treated as 
inherently block. NVDA certainly never does this; it always makes that 
decision based on the display object attribute.


On 20/01/2016 6:47 AM, Richard Schwerdtfeger wrote:
> Jamie and Alex,
> We reviewed this topic and we agree with Jamie that role="text" should 
> map to a static text role:
> https://lists.w3.org/Archives/Public/wai-xtech/2015Sep/0017.html
> The reason is that IA2 text frames are treated as separate blocks by 
> ATs such as when role="presentation" being applied to tables where the 
> fallout is TDs become IA2_ROLE_TEXTFRAME.
> If we were to treat role="text" as a separate block then it would not 
> be read inline with the surrounding text.
> Rich
> Rich Schwerdtfeger

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 Tuesday, 19 January 2016 22:26:39 UTC

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