WebAIM - Web Accessibility In Mind

E-mail List Archives

Opinions on Custom Select Menu Behavior


From: Vincent Young
Date: Oct 27, 2011 5:51PM

Select menus seem to have no consistency in terms of interaction and
identification within screen readers. For example:


In Safari/VoiceOver this select menu is identified as a pop-up button and
opens via down-arrow. In Firefox/Jaws it is identified as a combobox and
opens via alt+down arrow. What I'm wondering is when you are creating a
custom select menu with ARIA (e.g. Filament Group Custom Select
should you try to mimic the interaction/identification found in the native
control across different user agents/Assistive Technology or should you
attempt to standardize across the board. If you standardize, what should
you standardize on? Separate implementation is possible, but a total pain.

Thoughts please. Thanks.


WebHipster Interactive, ltd.
Vincent Young - Principal
742 N Sweetzer
West Hollywood, CA 90069
p: 614.607.3400
f: 339-674-3400
w: http://www.webhipster.com