Yes, if HTML 5 does not handle it we could at least provide an indicator to
it's modality in aria.next.
Rich Schwerdtfeger
CTO Accessibility Software Group
From: "Schnabel, Stefan" <stefan.schnabel@sap.com>
To: Joseph Scheuhammer <clown@alum.mit.edu>, James Nurthen
<james.nurthen@oracle.com>
Cc: W3C WAI-XTECH <wai-xtech@w3.org>
Date: 02/02/2011 09:21 AM
Subject: RE: Confusion about role of dialog
Sent by: wai-xtech-request@w3.org
>>> Aside: this might be an argument for an "aria-model" property.
I think you mean "aria-modal=true/false" for dialog with a default=false.
+1 to that.
Regards
Stefan
-----Original Message-----
From: wai-xtech-request@w3.org [mailto:wai-xtech-request@w3.org] On Behalf
Of Joseph Scheuhammer
Sent: Mittwoch, 2. Februar 2011 16:14
To: James Nurthen
Cc: W3C WAI-XTECH
Subject: Re: Confusion about role of dialog
James,
I thought of another issue -- modal dialogs. To make a dialog modal,
the web app has to capture *all* of the events, including mouse clicks,
and not let them bubble outside of the dialog element. This is
especially true of alertdialogs since they are typically modal. Quoting
from the spec:
"Content authors SHOULD make alert dialogs modal by ensuring that, while
the alertdialog is shown, keyboard and mouse interactions only operate
within the dialog." [1]
If modal dialogs are responsible for handling all events, then the AT
has to be informed to not override that. Having it assume that all
dialogs are applications would suffice.
Aside: this might be an argument for an "aria-model" property.
[1] http://www.w3.org/WAI/PF/aria/roles#alertdialog
--
;;;;joseph
'I had some dreams, they were clowns in my coffee. Clowns in my coffee.'
- C. Simon (misheard lyric) -
