WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: 3.2.1 On focus

for

From: Mallory
Date: Jun 16, 2020 6:23AM

Sumit,
your devs can get around this by, after the radios, offering a dedicated "apply" (submit if this is a form) button. Users pressing this would get that dialog if the user had clicked Apply while the Decline Features radio was selected.
Because you're right: for keyboarders (not just SR users), focus and selection states are simultaneous with radios. Since they cannot distinguish between merely focussing and actively selecting, you don't want developers writing code that acts as if selection is a user intent. The "Apply" button can ensure users truly intend to choose that radio control.

cheers,
_mallory

On Tue, Jun 16, 2020, at 12:53 PM, Patrick H. Lauke wrote:
> On 16/06/2020 10:44, Sumit Patel wrote:
> > Hi all,
> >
> > I am back with a doubt regarding 3.2.1 On focus.
> > If a screen reader user reaches at a radio group, it will change to
> > focus or forms mode from virtual or browse mode. SoThen, using arrow
> > keys, they can navigate through each options. But, with the
> > navigation, based on the focus the respective radio button will be
> > selected. This is the behavior of radio buttons with screen reader.
> >
> > Just imagine, a group of radio buttons have provided to choose any of
> > the features. "Decline features" is the last option in the radio
> > group. Thus, when the Decline features option receives focus, it will
> > get selected and an overlay will open - similarly an alert dialogue
> > box such as Are you sure do you want to decline features?.
> >
> > Is it a failure of On focus.
>
> It's a failure of 3.2.2 On input in this case, I'd say.
>
> P
> --
> Patrick H. Lauke
>
> https://www.splintered.co.uk/ | https://github.com/patrickhlauke
> https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > > >