WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Styling Radio elements to look like Button element?

for

From: Scott González
Date: Nov 3, 2014 4:58AM

The keyboard interaction is always based on the semantic meaning, not the
visual presentation. When the visual presentation of checkbox groups and
radio groups are the same, the developer should make sure that users know
whether the options are mutually exclusive (radio) or not (checkbox). The
user can know this from common/prior knowledge (e.g., a group of bold,
italic, underline settings in a text editor), or via a note in the user
interface.

On Mon, Nov 3, 2014 at 5:05 AM, Maraikayar Prem Nawaz < <EMAIL REMOVED> >
wrote:

> Is the keyboard interactions differ for 2 different components which looks
> the same, wouldn't it confuse Keyboard only users?
>
> Should the keyboard interaction match the hidden control or the one which
> is visually shown. For example, span element shown as a link imitates a
> link behavior correct?
>
> On Mon, Nov 3, 2014 at 12:06 PM, Bryan Garaventa <
> <EMAIL REMOVED> > wrote:
>
> > Since the checkbox role maps to equivalent control types on the OS, as
> > with the radio role, then the keyboard model should match the
> > functionality of each accordingly.
> >
> > So, checkbox controls should have separate tab stops unless otherwise
> > disabled, and grouped radio controls should have one tab stop
> > and the arrow keys should switch between them or skip one if otherwise
> > disabled.
> >
> > Basically, the keyboard functionality should match the equivalent control
> > type observed on the native OS.
> >
> >
> >