WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: Sending focus in a radio button group on error - visible focus indicator.

for

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

From: Laurence Lewis
Date: Sat, Mar 19 2022 3:16PM
Subject: Sending focus in a radio button group on error - visible focus indicator.
No previous message | Next message →

A decision was made in our Workplace in regard to error management for a
radio button group. If the group has an error, focus is moved to the
<legend> and the error message is located inside the legend element
Example: Radio button group - error message location
<https://codepen.io/Deafinitive/pen/RwjRReZ/30b2263b00edadb55840bfee19d76f9b>
.


When focus is moved to the legend element, is a visible focus indicator
needed, and why? If there is no visible focus indicator is this a failure
for 2.4.7 Focus Visible Level AA?


Regards

Laurence Lewis

From: Birkir R. Gunnarsson
Date: Sat, Mar 19 2022 4:28PM
Subject: Re: Sending focus in a radio button group on error - visible focus indicator.
← Previous message | Next message →

Hi

No, it's not a 2.4.7 fail, because the element the focus is moved to
is not operable (you can't click the legend to do anything).
Same as with skip links. Focus is typically placed on the container
for the main content of the page, not on the first focusable element
inside that container.

Personally I'd connect the error message to the radio button group
element using aria-describedby and place focus on the first radio
button in the group, but that's just a preference (aria-describedby on
grouping elements has pretty good support across browsers/screen
readers).


On 3/19/22, Laurence Lewis < = EMAIL ADDRESS REMOVED = > wrote:
> A decision was made in our Workplace in regard to error management for a
> radio button group. If the group has an error, focus is moved to the
> <legend> and the error message is located inside the legend element
> Example: Radio button group - error message location
> <https://codepen.io/Deafinitive/pen/RwjRReZ/30b2263b00edadb55840bfee19d76f9b>
> .
>
>
> When focus is moved to the legend element, is a visible focus indicator
> needed, and why? If there is no visible focus indicator is this a failure
> for 2.4.7 Focus Visible Level AA?
>
>
> Regards
>
> Laurence Lewis
> > > > >


--
Work hard. Have fun. Make history.

From: Patrick H. Lauke
Date: Sun, Mar 20 2022 3:47AM
Subject: Re: Sending focus in a radio button group on error - visible focus indicator.
← Previous message | Next message →

Lengthy back-and-forth discussion on whether focus being
programmatically moved to a static location needs to have a visible
focus indication or not https://github.com/w3c/wcag/issues/1001

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: David Farough
Date: Mon, Mar 21 2022 1:15PM
Subject: Re: Sending focus in a radio button group on error - visible focus indicator.
← Previous message | Next message →

I think that Birkir's solution might work better and avoid this issue.
I noticed when using Jaws with the codepen, that Jaws also indicated the not checked attribute for the radiobutton.
This could cause the user to try to activate the button even though it did not have focus.
I should also mention that NVDA did not do this.
Another difference to note on Jaws and NVDA.

From: David Farough
Date: Mon, Mar 21 2022 1:49PM
Subject: Re: Sending focus in a radio button group on error - visible focus indicator.
← Previous message | Next message →

I noticed a couple of other things.
For Jaws (current version) the previously mentioned behaviour occurred using Google Chrome and Microsoft Edge.
Jaws did not do this when using Firefox.
I noticed also, that when using NVDA with firefox, that when tabbing, I got to each of the unselected radiobuttons in the fieldset.
This also occurred using Jaws.
For Chrome and Edge, I went from the first of the radiobuttons directly to the submit button.
NVDA did not speak the unchecked status when focussed on the legend in any of the browsers used..
David

From: Laurence Lewis
Date: Tue, Mar 22 2022 3:04PM
Subject: Re: Sending focus in a radio button group on error - visible focus indicator.
← Previous message | No next message

Thanks for the feedback on radiology button error management. I will make
sure to pass this on.

On Tue, 22 Mar 2022 at 1:55 pm, < = EMAIL ADDRESS REMOVED = >
wrote:

> Send WebAIM-Forum mailing list submissions to
> = EMAIL ADDRESS REMOVED =
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://list.webaim.org/cgi-bin/mailman/listinfo/webaim-forum
> or, via email, send a message with subject or body 'help' to
> = EMAIL ADDRESS REMOVED =
>
> You can reach the person managing the list at
> = EMAIL ADDRESS REMOVED =
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WebAIM-Forum digest..."
> Today's Topics:
>
> 1. Re: Sending focus in a radio button group on error - visible
> focus indicator. (David Farough)
> 2. Re: Sending focus in a radio button group on error - visible
> focus indicator. (David Farough)
> 3. DOJ issues web accessibility guidance ( = EMAIL ADDRESS REMOVED = )
> 4. Re: DOJ issues web accessibility guidance (David Engebretson Jr.)
> 5. Re: Removing CSS Background image for legibility an
> Accessibility requirement? (Kevin Prince)
> 6. Re: Links that open new windows and/or go off site (Kevin Prince)
> 7. Re: Links that open new windows and/or go off site (Kevin Prince)
> 8. Re: Links that open new windows and/or go off site (Kevin Prince)
> 9. Re: Links that open new windows and/or go off site (glen walker)
> 10. Re: Removing CSS Background image for legibility an
> Accessibility requirement? (glen walker)
> 11. Re: Links that open new windows and/or go off site (Kevin Prince)
> 12. Re: Removing CSS Background image for legibility an
> Accessibility requirement? (Kevin Prince)
> 13. Re: Links that open new windows and/or go off site (Steve Green)
>
>
>
> ---------- Forwarded message ----------
> From: David Farough < = EMAIL ADDRESS REMOVED = >
> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> Cc:
> Bcc:
> Date: Mon, 21 Mar 2022 19:15:14 +0000
> Subject: Re: [WebAIM] Sending focus in a radio button group on error -
> visible focus indicator.
> I think that Birkir's solution might work better and avoid this issue.
> I noticed when using Jaws with the codepen, that Jaws also indicated the
> not checked attribute for the radiobutton.
> This could cause the user to try to activate the button even though it did
> not have focus.
> I should also mention that NVDA did not do this.
> Another difference to note on Jaws and NVDA.
>
>