RE: role="text" and text frames

I think you’d get “f” moving by character, and caret navigation would move to the “f”. Basically, it becomes just some text in the text pattern, with nothing special about it. We could decide to put a format break there, or not.

I should be clear, though. I don’t especially like role=text.  I’m not convinced it’s needed, the issue in 1011 scares me, and there are many details like those you raise to work out.

From: James Teh [mailto:jamie@nvaccess.org]
Sent: Tuesday, February 2, 2016 2:40 PM
To: Cynthia Shelly <cyns@microsoft.com>; Alexander Surkov <surkov.alexander@gmail.com>; Joseph Scheuhammer <clown@alum.mit.edu>
Cc: Richard Schwerdtfeger <schwer@us.ibm.com>; wai-xtech@w3.org; public-aria@w3.org
Subject: Re: role="text" and text frames

On 3/02/2016 7:53 AM, Cynthia Shelly wrote:

Once upon a <img alt=”foo”> time
For role=text, the text pattern for the page would be “Once upon a foo time”
What would happen if you move by character from the space after the "a"? Would you get "f" or "foo"? And what will pressing right arrow when using browser caret navigation (including contentEditable) do? These are the sort of questions that make techniques like this very problematic. The answers to these questions need to be well defined.

If UIA is really mapping this to the text pattern alone, it could be argued that IA2 should actually do the same; i.e. don't expose an accessible, just expose it in IAccessibleText. However, see the above potential gotchas.

Jamie



--

James Teh

Executive Director, NV Access Limited

Ph +61 7 3149 3306

www.nvaccess.org<http://www.nvaccess.org>

Facebook: http://www.facebook.com/NVAccess


Twitter: @NVAccess

SIP: jamie@nvaccess.org<mailto:jamie@nvaccess.org>