WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: 3.2.1 On focus

for

From: Moore,Michael (Accessibility) (HHSC)
Date: Jun 16, 2020 8:11AM

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