- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Fri, 25 Sep 2015 09:25:09 -0400
- To: James Teh <jamie@nvaccess.org>, Alexander Surkov <surkov.alexander@gmail.com>, Richard Schwerdtfeger <schwer@us.ibm.com>
- Cc: W3C WAI-XTECH <wai-xtech@w3.org>
Thanks Jamie,
On 2015-09-23 7:55 PM, James Teh wrote:
> On 24/09/2015 2:44 AM, Joseph Scheuhammer wrote:
>> If it matters, two use cases of role="text" entail that caret
>> navigation doesn't make sense.
> Right. However, I see that there are cases where it *might* make
> sense, such as this example from the spec:
> <div role="text">
> <p>I</p>
> <p>like</p>
> <p>turtles</p>
> </div>
> In that case, the accessible *does* need IAccessibleText. And now
> things get confusing: should the AT expect IAccessibleText or not for
> this role? Where IAccessibleText is present, an AT certainly shouldn't
> just use the name.
>
> FWIW, NVDA should handle either case with no problems as it is.
Cool. I think there is enough here to fill in the role mapping table
with respect to IA2.
--
;;;;joseph.
'Array(16).join("wat" - 1) + " Batman!"'
- G. Bernhardt -
Received on Friday, 25 September 2015 13:25:44 UTC