Re: role="text" and text frames

Hi Rich, Alex,

I've come to expect that text frame would have accessible text based on 
its current usage. I think I agree with Alex that ideally, it would have 
AccessibleText. However, I do understand why this role might be chosen 
for the purpose you describe. Looking at the NVDA code, I don't think 
there is anything that *depends* on this role having AccessibleText.

The text frame role is currently a generic container. As such, we would 
try to traverse inside it for browse mode, rather than just accepting 
its accessible name. Would servers be exposing children in this case? 
I'm guessing not, in which case this should be fine.

Was ROLE_SYSTEM_STATICTEXT considered?

Jamie

On 23/09/2015 6:06 AM, Alexander Surkov wrote:
> Hi. Small correction. Not really wanted but I was ok with that. I 
> think in ideal world role=text should be exposed via IAccessibleText.
> Thanks!
> Alex.
>
> On Tue, Sep 22, 2015 at 3:55 PM, Richard Schwerdtfeger 
> <schwer@us.ibm.com <mailto:schwer@us.ibm.com>> wrote:
>
>     Hi Jamie,
>
>     Is it your expectation is that an IA2 role of "textframe"
>     implements the IAccessibleText interface?
>
>     The reason we are asking in the Accessibility API Mapping group is
>     that Alex has wanted role="text" to map to a text frame when
>     role="text" is applied to an image with visible text in the image
>     and there no way to determine character positions with an image
>     without doing OCR.
>
>     Please advise.
>
>     Thanks,,
>     Rich
>
>
>     Rich Schwerdtfeger
>
>

-- 
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: jamie@nvaccess.org