520766 - revert alertdialog to expose role alert

Status: RESOLVED WONTFIX

(Core :: Disability Access APIs, defect)

Description

[David Bolter [:davidb] (NeedInfo me for attention)]

Attachment: trivial map change.

With changeset http://hg.mozilla.org/mozilla-central/rev/19e814487afb we had to map alertdialog to dialog, which might not be ideal in the long run. Let's discuss here.

Marco, can you see if Jaws still barfs when we expose alertdialogs as alerts? It sounds like NVDA is immune (from discussion on bug 472311).

Not the implementation guide currently recommends exposing alert (http://www.w3.org/WAI/PF/aria-implementation/#mapping_role)

Comment 1

[Marco Zehe (:MarcoZ)]

(In reply to comment #0)
> Marco, can you see if Jaws still barfs when we expose alertdialogs as alerts?

JAWS 10 definitely will barf, and JAWS 11 is still pretty shaky in that it sometimes loads all kinds of other UI stuff into its virtual buffer (already reported to FS), so results will most likely not be accurate until that is fixed.

> It sounds like NVDA is immune (from discussion on bug 472311).

Correct.

> Not the implementation guide currently recommends exposing alert
> (http://www.w3.org/WAI/PF/aria-implementation/#mapping_role)

Yeah this one is tricky. A 2dialog" usually implies a modal window. However on a web page or in web page-generated content, there is no such thing as a modal window. However, alerts are usually notifications that you can interact with, but don't have to, like our password reminder. I have yet to see a good example of an alertdialog that shows me the difference to an alert to give a final judgement on what I think is best to expose here.

Comment 2

[David Bolter [:davidb] (NeedInfo me for attention)]

Thanks Marco, I'll take that info to the group.

Comment 3

[David Bolter [:davidb] (NeedInfo me for attention)]

The group agrees, closing.