WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Question on Drop-down with MAC VoiceOver

for

From: Mark Magennis
Date: Mar 25, 2022 6:47AM

Hi Alysa,

If I understand you correctly, you are asking why does a W3C example drop down coded using ARIA not behave the same way as a standard <select>.

It's because the keyboard behaviour of <select> controls varies a lot between different browsers (and often seems illogical). When you code an ARIA widget you have to code one set of keyboard behaviours, so which do you choose? Do you code it to work the way a <select> works in Safari? Or the way it works in Chrome? I imagine (I'm guessing because I haven't looked at the example) the answer is that you try to follow the standard approach for keyboard behaviour of ARIA widgets, e.g. Tab in, Arrow within, Tab out, ESC to close, etc. You may also take into account ways in which a <select> behaves that are consistent across browsers and try to stick with them to emulate the native control better. But sometimes there is a clash between the standard ARIA widget behaviour and the way the standard HTML controls works, as in what happens with Tab and ESC while a <select> is open in different browsers. It's very variable and not at all logical in my opinion.

Mark

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Ramshif .
Sent: 25 March 2022 08:44
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: [EXTERNAL] Re: [WebAIM] Question on Drop-down with MAC VoiceOver

[You don't often get email from <EMAIL REMOVED> . Learn why this is important at http://aka.ms/LearnAboutSenderIdentification.]

Hi Ramshif,

Since the drop down is not a customized one I would agree with Glen. However, I am confused with a Customized drop down with the behavior you mentioned as well as @Glen if it's a native drop down as you confirmed then how does the drop down which are available as an example in W3 and ARIA not having the same issue?

Regards,
Allysa.

On Mar 25, 2022, at 11:12 AM, Ramshif . < <EMAIL REMOVED> > wrote:


Thanks for your response Glen.

Yes, I have both options turned on and I am using Safari browser.


Get Outlook for Android<https://aka.ms/AAb9ysg> From: WebAIM-Forum < <EMAIL REMOVED> > on behalf of glen walker < <EMAIL REMOVED> >
Sent: Friday, March 25, 2022 12:36:19 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Question on Drop-down with MAC VoiceOver

Looks like you are using a native select/option element so whatever behavior you are seeing should be native to the Mac.

Ignoring voiceover for the moment, do you have the option turned on to allow the tab key to navigate to all elements? There's a general Mac setting and a Safari setting (you didn't say which browser you were using).

The general setting is in system preferences > keyboard > shortcuts.
Select the "use keyboard navigation..." checkbox.
The Safari setting is in preferences > advanced. Select the "Press TAB to highlight..." checkbox.



On Thu, Mar 24, 2022 at 11:47 AM Ramshif . < <EMAIL REMOVED> > wrote:

> Hello,
>
> This is to understand if below issue is a failure of WCAG?
> I have a drop-down (attached) when opened and by pressing Tab key
> keeps the focus to the drop-down (by closing the list) instead of
> going to the next interactive element. Is this a WCAG failure or an
> actual behavior of VoiceOver on MAC? I haven't seen this behavior with
> other drop-down which are present in w3c/ARIA pages.
>
> Thanks in advance.
>
>
> > > archives at http://webaim.org/discussion/archives
> >