WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [EXTERNAL]Exposing the selected state of buttons

for

From: Mark Magennis
Date: Dec 9, 2019 9:23AM

Birkir,

I'm afraid I'm one of these lazy people who grumble about defects but never file them as issues. You've prompted me to change my ways. Could you tell me, where do I file issues with JAWS, NVDA, and VoiceOver? And presumably if I find thst the defect is in the accessibility tree, I should file it against the browser? Where do I do that for Firefox, Chrome, and Safari?

I know there's no point in filing issues against IE11 but is it possible to view its accessibility tree? Does it even have one?

Mark

Mark Magennis
Skillsoft | mobile: +353 87 60 60 162
Accessibility Specialist


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Birkir R. Gunnarsson
Sent: 09 December 2019 13:51
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] [EXTERNAL] Re: Exposing the selected state of buttons

IE11 can't be helped I think, the browser is no longer being updated.
For the rest, we need to file issues, this pattern needs to be supported going forward.


On 12/9/19, Mark Magennis < <EMAIL REMOVED> > wrote:
> Sudheer,
>
> Be particularly careful if any of your users are likely to be using IE11.
> aria-pressed hardly works in IE11. JAWS reads the state only when
> aria-pressed=true, not when it is false, and doesn't announce state
> changes (when you press the button). NVDA only reads the state and
> announces state changes when aria-pressed=true, not false.
>
> JAWS/Firefox doesn't work well either. Like NVDA/IE11, it only reads
> the state and announces state changes when aria-pressed=true, not
> false. I haven't looked to see what happens in Chrome.
>
> For these reasons, my company's Toggle Button coding pattern doesn't
> use aria-pressed. There are other ways to reliably give a similar
> experience. A pity, because aria-pressed should be perfect for toggle buttons.
>
> Mark
>
> Mark Magennis
> Skillsoft | mobile: +353 87 60 60 162
> Accessibility Specialist
>
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> Sudheer Babu
> Sent: 22 November 2019 10:19
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: [EXTERNAL] Re: [WebAIM] Exposing the selected state of
> buttons
>
> Thanks Detlev!, you are right..Aria-selected works well on tab panels
> aria-pressed seems to be working fine but just don't want the button
> to be announced as "toggle buttons"
>
> On Fri, Nov 22, 2019 at 3:45 PM Detlev Fischer
> < <EMAIL REMOVED> >
> wrote:
>
>> It is possible that I am missing something but a quick test seems to
>> indicate that on <button>, aria-pressed is better supported than
>> aria-selected.
>>
>> See
>> http://3needs.org/en/testing/code/button-states.html
>>
>> In NVDA,
>> - IE will render both (selected / pressed)
>> - Firefox will just render pressed
>> - Chrome will just render pressed
>> - Edge ( 42.17134.1038.0) will just render pressed
>>
>> Detlev
>>
>> Am 22.11.2019 um 10:58 schrieb Patrick H. Lauke:
>> > On 22/11/2019 09:50, Sudheer Babu wrote:
>> > [...]
>> >> Now, please help me with the appropriate aria attributes to be
>> >> used to make the screen reader announce the selected state of
>> >> these buttons.
>> >
>> > aria-selected="true"
>> >
>>
>> --
>> Detlev Fischer
>> Testkreis
>> Werderstr. 34, 20144 Hamburg
>>
>> Mobil +49 (0)157 57 57 57 45
>>
>> http://www.testkreis.de
>> Beratung, Tests und Schulungen für barrierefreie Websites
>>
>> >> >> archives at http://webaim.org/discussion/archives
>> >>
> > > archives at http://webaim.org/discussion/archives
> > > > archives at http://webaim.org/discussion/archives
> >


--
Work hard. Have fun. Make history.