WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Radio Button strange behaviour in Firefox.

for

From: Weston Thayer
Date: Jun 24, 2020 12:45PM

There was a thread
<https://web-a11y.slack.com/archives/C050D9NHZ/p1580492505053200> about
this on the web-a11y Slack earlier this year. Firefox's behavior does
appear to be in conflict with the spec <https://www.w3.org/wiki/RadioButton>
:

> When focus is on the group and when no radio button is selected:

- Tab key press moves focus to the first radio button in the group, but
does not select the radio button.
- Shift+Tab key press moves focus to the last radio button in the group,
but does not select the radio button.


Asa Dotzler mentioned that he'd shared this behavior with the dev team, but
I'm not aware of a Bugzilla for it. FWIW, it is a very old Firefox
behavior, I reproduced it back to at least Firefox v40.

On Wed, Jun 24, 2020 at 8:31 AM Birkir R. Gunnarsson <
<EMAIL REMOVED> > wrote:

> Shawn
>
> That is an expected behavior for a set of radio buttons where no radio
> button has been selected, (they're all focusable until one has been
> selected). You don't see this often because one of the radio buttons
> is typically selected by default (and that is the recommendation for
> the pattern).
> What I find odd on this page is that Chrome with Jaws announces "1 of
> 6" for the first radiobutton, there are 2 sets of 3. I thought they
> all had the same "name" attribute (which would cause a screen reader
> to perceive them as one set) but they don't.
> Granted they should be in two separate <fieldset> or anotehr grouping
> element, but I'm still surprised that Jaws perceives them as one set.
>
>
>
> On 6/24/20, Murphy, Sean < <EMAIL REMOVED> > wrote:
> > All,
> >
> > If you visit this site for a standard radio button:
> >
> >
> https://www.w3schools.com/tags/tryit.asp?filename=tryhtml5_input_type_radio
> >
> > Using Firefox with NVDA or Jaws. When an option in the radio button is
> not
> > selected. Using the tab key, takes you to each options within the radio
> > button component. Once the option is selected, then the tab order works
> as
> > expected. Using Chrome, this behaviour does not occur. Instead the tab
> key
> > takes you to the next control.
> >
> >
> > Note: If the option in the radio button is pre-selected, then the issue
> > described above does not occur.
> >
> > Is this a Firefox defect?
> >
> >
> >
> >
> > [cid:image001.png@01D64A6B.6F067AA0]
> >
> > Sean Murphy | Accessibility expert/lead
> > Digital Accessibility manager
> > Telstra Digital Channels | Digital Systems
> > Mobile: 0405 129 739 | Desk: (02) 9866-7917
> >
> > www.telstra.com
> >
> > This email may contain confidential information.
> > If I've sent it to you by accident, please delete it immediately
> >
> >
> >
> >
>
>
> --
> Work hard. Have fun. Make history.
> > > > >