E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 4 (In chronological order)

From: Sumit Patel
Date: Tue, Jun 16 2020 3:44AM
Subject: 3.2.1 On focus
No previous message | Next message →

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.


Or can we leave it since it is an alert dialogue box?

Regards,
Sumit patel

From: Patrick H. Lauke
Date: Tue, Jun 16 2020 4:53AM
Subject: Re: 3.2.1 On focus
← Previous message | Next message →

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

From: Mallory
Date: Tue, Jun 16 2020 6:23AM
Subject: Re: 3.2.1 On focus
← Previous message | Next message →

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
> > > > >

From: Moore,Michael (Accessibility) (HHSC)
Date: Tue, Jun 16 2020 8:11AM
Subject: Re: 3.2.1 On focus
← Previous message | No next message

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

In the case described by Sumit the behavior is designed to prevent user error and could be used to fulfil 3.3.4. To maintain compliance with 3.2.2, instructions could be included at the beginning of the form that indicate that the user may be asked to confirm certain selections before proceeding in the form. Using an alert dialog and properly managing focus appears to be a good balance of directing user focus while preventing unintended actions. I think it would be best to have the possible adverse action be the last choice in the group. Another alternative would be to place this type of selection on its own interface page and request the commitment on submission of the page.

Mike Moore