What fresh hell is THIS now? - Patrick Lauke
aria-activedescendant
on the parent to set to the id of the child element as user goes through the list
<math> <mrow> <mrow> <mrow> <mi>a</mi> <mo aria-label="times">⁢ <!-- invisible times --></mo> <msup aria-label="x squared"> <mi role="presentation">x</mi> <mn role="presentation">2</mn> </msup> </mrow> <mo>+</mo> <mrow> <mi>b</mi> <mo aria-label="times">⁢ <!-- invisible times --></mo> <mi>x</mi> </mrow> <mo>+</mo> <mi>c</mi> </mrow> <mo>=</mo> <mn>0</mn> </mrow> </math>
To answer myself
Do any ATs have a shortcut for something like "put focus on last focusable element you read out to me"?
I found what made me think there is. According to http://doccenter.freedomscientific.com/doccenter/archives/training/jawskeystrokes.htm JAWS has "Move to Previous Clickable Element" (default SHIFT+SLASH). (cc @garcialo )
I guess it's not clear to me if the spec is supposed to describe the reality of what works or also describe what AT should do.
@MichielBijl wrote
@pkra: The APG is based on current and future ARIA attributes/roles. So there is a good chance that something that is in there won't work in all AT. There are some AT folk in the ARIA WG. However, AT folk don't want the ARIA/APG spec to tell them what to do.
Ok. Let me ask differently: once it's published, what is it supposed to represent? For example, it seems reasonable that no AT should react to role=math with "I'm not going to read this at all". Or perhaps even that's too much for AT to handle ;-)
[karlgroves] >well it does add whole nodes to the dom
In that case it might not hurt to throw together a POC and test it.
<main>
, <footer>
, <nav>
, etc without adding the aria role?