W3C home > Mailing lists > Public > wai-xtech@w3.org > September 2012

Re: suggest deprecating alertdialog role in ARIA 1.1

From: Alexander Surkov <surkov.alexander@gmail.com>
Date: Wed, 12 Sep 2012 16:14:38 +0900
Message-ID: <CA+epNsc3cxiE2YRbaDs3-kwtkDe0eFJxfXSoGwMRPOdVqoXqBA@mail.gmail.com>
To: "Schnabel, Stefan" <stefan.schnabel@sap.com>
Cc: Joshue O Connor <joshue.oconnor@cfit.ie>, Steve Faulkner <faulkner.steve@gmail.com>, W3C WAI-XTECH <wai-xtech@w3.org>, Richard Schwerdtfeger <schwer@us.ibm.com>, Marco Zehe <marco.zehe@googlemail.com>, James Teh <jamie@nvaccess.org>
I don't know whether they don't use it, I said that I didn't hear they
use it :) That means nobody was requested those states from Firefox
and that means either AT don't use them at all or Firefox don't have
controls where these states are used. Actually Firefox has a hack and
exposes these states on form controls due to MSAA states lack but it
shouldn't prevent Firefox to start to expose them on dialogs.

Anyway if dialog types are useful for AT user and thus ATs needs an
access to this information then UAIG people can take care of the best
way to expose it.

Thank you.
Alex.


On Wed, Sep 12, 2012 at 3:50 PM, Schnabel, Stefan
<stefan.schnabel@sap.com> wrote:
> Hi Alex,
>
> well I think offering something to be taken is better than doing nothing here.
> Do you know reasons why AT doesn't use these states?
>
> - Stefan
>
> -----Original Message-----
> From: Alexander Surkov [mailto:surkov.alexander@gmail.com]
> Sent: Mittwoch, 12. September 2012 08:34
> To: Schnabel, Stefan
> Cc: Joshue O Connor; Steve Faulkner; W3C WAI-XTECH; Richard Schwerdtfeger; Marco Zehe; James Teh
> Subject: Re: suggest deprecating alertdialog role in ARIA 1.1
>
> Hi, Stefan. Primarily I meant Firefox implementation but I didn't hear
> that these states are used by AT.
> Thank you.
> Alex.
>
> On Fri, Sep 7, 2012 at 8:47 PM, Schnabel, Stefan
> <stefan.schnabel@sap.com> wrote:
>> Alex,
>>
>> maps perfectly for me:
>>
>> additional" aria-dialogtype=Error/Warning/Info " ->  STATE_SYSTEM_ALERT_HIGH/MEDIUM/LOW
>>
>> I remember seeing those using Inspect32 with standard windows dialogs in the states enum listed, so I don't know what you mean with " but they weren't ever implemented."
>>
>> Stefan
>>
>>
>> -----Original Message-----
>> From: Alexander Surkov [mailto:surkov.alexander@gmail.com]
>> Sent: Freitag, 7. September 2012 11:39
>> To: Schnabel, Stefan
>> Cc: Joshue O Connor; Steve Faulkner; W3C WAI-XTECH; Richard Schwerdtfeger; Marco Zehe; James Teh
>> Subject: Re: suggest deprecating alertdialog role in ARIA 1.1
>>
>> As far as I know there's no difference. MSAA has states like
>> STATE_SYSTEM_ALERT_LOW/MEDIUM/HIGH but they weren't ever implemented.
>> I don't recall anything similar in other standards. Anyway many AT
>> APIs are extensible so it shouldn't be a problem.
>>
>> Alex.
>>
>>
>> On Fri, Sep 7, 2012 at 6:23 PM, Schnabel, Stefan
>> <stefan.schnabel@sap.com> wrote:
>>> Hi Josh, Alexander
>>>
>>> good point having an additional" type=Error/Warning/Info " parameter in ARIA 1.1 for dialog.
>>> But then we should go overboard and declare also modality (modal/non-modal dialog).
>>>
>>> Regarding API mappings, how is the situation in Windows MSAA and let's say typed MessageBoxes ?
>>> Isn't there a standard way to map these additional properties without borrowing from aria-label?
>>>
>>> Regards
>>> Stefan
>>>
>>>
>>> -----Original Message-----
>>> From: Joshue O Connor [mailto:joshue.oconnor@cfit.ie]
>>> Sent: Freitag, 7. September 2012 11:16
>>> To: Schnabel, Stefan
>>> Cc: Steve Faulkner; W3C WAI-XTECH; Richard Schwerdtfeger; Marco Zehe; James Teh
>>> Subject: Re: suggest deprecating alertdialog role in ARIA 1.1
>>>
>>> Hi Stefan,
>>>
>>>> It is not the fault of the ARIA spec that alertdialog is poorly supported in AT.
>>>
>>> I completely agree but devs need practical solutions right now.. not
>>> around the corner and to my mind anything that makes the practical
>>> accessible web development easier - is a good thing.
>>>
>>>> Role "alertdialog" has been invented to indicate simple ok/yes/no/cancel messageboxes in contrast to more
>>>> elaborated complex dialogs with role "dialog".
>>>>
>>>> Therefore, I recommend *NOT* to remove the role entirely, in contrary, it should even be extended to reflect the
>>>> *type* of "alert" dialog Error/Warning/Info etc. and its usage according to this should be reflected in the AP Guidelines documentation.
>>>
>>> Not a bad idea. However, I suggest removing it and actually using the
>>> role="dialog" as a generic role and allowing it to take the argument
>>> dialog Error/Warning/Info etc.
>>>
>>> Cheers
>>>
>>> Josh
Received on Wednesday, 12 September 2012 07:15:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 12 September 2012 07:15:07 GMT