WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Question on Drop-down with MAC VoiceOver

for

From: allyssa jessicon
Date: Mar 25, 2022 7:07AM

Hello Mark.

I could see <li> has been used in ARIA example whereas the attached HTML used <select> instead. As per my understanding you conclude that it's just fine?


Get Outlook for iOS<https://aka.ms/o0ukef>
From: WebAIM-Forum < <EMAIL REMOVED> > on behalf of Mark Magennis < <EMAIL REMOVED> >
Sent: Friday, March 25, 2022 6:17:41 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Question on Drop-down with MAC VoiceOver

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