- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Fri, 2 Oct 2015 11:50:36 -0400
- To: Alexander Surkov <surkov.alexander@gmail.com>
- Cc: James Teh <jamie@nvaccess.org>, Richard Schwerdtfeger <schwer@us.ibm.com>, W3C WAI-XTECH <wai-xtech@w3.org>
Hi Alex,
That's my understanding. I've already made the edits to the core-aam:
http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-text
On 2015-10-02 11:34 AM, Alexander Surkov wrote:
> Do I understand right that we go with textframe role because of this
> example?
>
> On Fri, Sep 25, 2015 at 9:25 AM, Joseph Scheuhammer
> <clown@alum.mit.edu <mailto:clown@alum.mit.edu>> wrote:
>
> 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, 2 October 2015 15:51:09 UTC