- From: James Teh <jamie@nvaccess.org>
- Date: Thu, 24 Sep 2015 09:55:54 +1000
- To: Joseph Scheuhammer <clown@alum.mit.edu>, Alexander Surkov <surkov.alexander@gmail.com>, Richard Schwerdtfeger <schwer@us.ibm.com>
- Cc: W3C WAI-XTECH <wai-xtech@w3.org>
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. However, this needs to be carefully considered and the behaviour for all potential use cases specified. Jamie -- 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
Received on Wednesday, 23 September 2015 23:56:15 UTC