Some light boxes: http://www.ajaxrain.com/tagcloud.php?tag=lightbox
Thanks
Rani
If all focusable descendants of an alertdialog should be read in
addition to its text (as is done for alerts), then an alertdialog with
OK and Cancel buttons would also read the Cancel button even if the OK
button was focused, which is non-standard behaviour.
Also, if I recall correctly, Firefox gives alertdialogs a role of alert,
which has always seemed strange/incorrect to me. It is a dialog, not an
alert - an alert doesn't get focus automatically. Giving it a role of
alert causes screen readers to say "alert", which means the user may not
realise that it has gained focus. Is my understanding incorrect?
--
James Teh
Email/MSN Messenger/Jabber: ja...@jantrid.net
Web site: http://www.jantrid.net/
Since there is no alertdialog role in IA2, we use the role of alert to
indicate the whole container should be read when shown. However, it's
possible to get the raw ARIA role via the xml-roles object attribute. I
suppose we should have a role in IA2 for it.
- Aaron
As an interesting sidenote, we used to read all descendants for alert
events. However, we don't do this anymore because in Firefox's case,
there are duplicates - the leaf text nodes contain the same text as
their parents - so we were getting double speaking. Therefore, reading
all descendants actually isn't an option for Firefox without
special-case, hacky logic.
> Since there is no alertdialog role in IA2, we use the role of alert to
> indicate the whole container should be read when shown. However, it's
> possible to get the raw ARIA role via the xml-roles object attribute. I
> suppose we should have a role in IA2 for it.
I think we definitely need a different role in order to differentiate
alertdialogs from alerts (which are two different beasts).
- Aaron
For those who are interested, here is the Mozilla bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=472311