- From: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>
- Date: Tue, 10 Jun 2014 10:36:33 -0700
- To: "'PF'" <public-pfwg@w3.org>
http://connect.microsoft.com/IE/feedback/details/817699/ie10-and-ie-11-using -aria-activedescendant-attribute-to-control-focus-within-a-widget-does-not-w ork Hi, This isn't an IE specific question, but it's mentioned in the above referenced bug. A client was asking me about this today, saying that aria-activedescendant isn't supported in IE, but to my knowledge, it is. So, the bug sites the following two examples: http://oaa-accessibility.org/example/11/ and http://cookiecrook.com/test/aria/tree/ariatree2.html The first uses role=application and tabindex=-1 on the container, which appears to be screwing with screen reader tabability in JAWS15 and IE11, even though it's possible to arrow to it and press Enter to activate and use the arrow keys. The accessibility tree does look to be updated correctly when the arrow keys change the value on Win7. The second example shows an ARIA tree construct, which has a similar container, however there are multiple instances of aria-activedescendant on various nodes throughout the tree construct, which, to my knowledge, is a mis-use of aria-activedescendant in this instance. Is this the case? The way that focus is handled and the multiple aria-activedescendant attributes looks weird to me. Is this a valid construct? Thanks, Bryan
Received on Tuesday, 10 June 2014 17:37:34 UTC