stomme_poes — 2013-02-25T12:51:52-05:00 — #1
He shows that right now, there are various differences between browsers and AT's handling of ARIA in trees, so it's not very stable right now. But he does have a best-choice example which bascially works with current browsers and screen readers.
In my opinion, VoiceOver not keeping the cursor in check with keyboard cursor and moving tabIndexes is indeed a bug. I would think this, combined with webkit's in-page link bug would make thing pretty hair-pulling for Mac users.
Good work Jason.
mat30 — 2013-02-25T14:09:48-05:00 — #2
That's a jolly fine article.
So the reopening of that bug has not thus far gone anywhere? Just as Opera announces a switch to Webkit. Dumb on both counts. More user JS ahead for me, I think.
ralphm — 2013-02-25T19:16:35-05:00 — #3
A great read, although a lot to take in. Although I've never been interested in trees like that, this gives a good insight into how ARIA works to make the web more accessible. Thanks for keeping us aware of this stuff, poes.
stomme_poes — 2013-02-26T05:25:06-05:00 — #4
I'd say it's good to know for any dashboard-style application, since those usually have trees in a sidebar.