WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Radio Buttons Not Functioning

for

From: Aaron Cannon
Date: Jan 30, 2017 3:46PM

You wrote:
"Thank you Aaron. I want to keep it as the default for JAWS and NVDA."

I understand. The only reason I suggested doing the other
non-standard things was just for helping to troubleshoot what was
going on. I wasn't suggesting that that is what the end-user should
be expected to do.

Let us know what you discover.

Aaron

On 1/30/17, JP Jamous < <EMAIL REMOVED> > wrote:
> Thank you Aaron. I want to keep it as the default for JAWS and NVDA. I did
> not test it with NVDA, but I will tomorrow.
>
> It is weird, but I am sure that something is making the SR become stuck on
> one radio button in forms mode.
>
> That's old markup though. We have more accessible markup in our pattern
> library. It won't stop me from making the page accessible, I just think it
> is interesting as to why it is locking the SR on one radio button.
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf
> Of Aaron Cannon
> Sent: Monday, January 30, 2017 2:31 PM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] Radio Buttons Not Functioning
>
> A couple things I might try: Can you look at the markup of one of the radio
> buttons that doesn't have focus? I'm just wondering if there is some JS that
> is setting the name when a radio button is focused or checked. Probably a
> longshot.
>
> Is this happening in more than one browser?
>
> Does anything happen differently if you turn off the virtual cursor mode
> with insert+z? Any difference with NVDA? Again these are longshots.
>
> Luck.
>
> Aaron
>
> --
> This message was sent from a mobile device
>
>
>> On Jan 30, 2017, at 14:23, JP Jamous < <EMAIL REMOVED> > wrote:
>>
>> No it does not.
>>
>> -----Original Message-----
>> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf
>> Of Bossley, Peter A.
>> Sent: Monday, January 30, 2017 2:14 PM
>> To: WebAIM Discussion List < <EMAIL REMOVED> >
>> Subject: Re: [WebAIM] Radio Buttons Not Functioning
>>
>> When you tab onto the radio group, does jaws properly report the number of
>> options in the radio grouping and make the sound to indicate forms mode
>> triggering?
>>
>>
>> -----Original Message-----
>> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
>> Behalf Of JP Jamous
>> Sent: Monday, January 30, 2017 11:11 AM
>> To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
>> Subject: Re: [WebAIM] Radio Buttons Not Functioning
>>
>> I am only auditing and this is a nasty dynamic page. I have N amount of
>> time or it would expire on me.
>>
>> -----Original Message-----
>> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf
>> Of Swift, Daniel P.
>> Sent: Monday, January 30, 2017 9:42 AM
>> To: WebAIM Discussion List < <EMAIL REMOVED> >
>> Subject: Re: [WebAIM] Radio Buttons Not Functioning
>>
>> I don't think this is the answer that you are looking for --- why not just
>> remove the divs and style the input/labels as appropriate?
>>
>> *big grin*
>>
>> All the best,
>> Dan
>>
>> -----Original Message-----
>> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
>> Behalf Of JP Jamous
>> Sent: Monday, January 30, 2017 10:36 AM
>> To: 'WebAIM Discussion List'
>> Subject: [WebAIM] Radio Buttons Not Functioning
>>
>> Folks,
>>
>>
>>
>> I have various radio buttons that populate dynamically, which is not an
>> issue. However, if I go into forms mode, JAWS is unable to toggle between
>> the radio buttons using arrow keys.
>>
>>
>>
>> 1. Proper HTML semantic is being used.
>> 2. Input fields have the same unique name.
>> 3. No tabindex on any of the radio buttons, leaving the browser to
>> handle that.
>>
>>
>>
>> The only thing that popped up at me was separate div tags. Here is how the
>> structure is in the DOM.
>>
>>
>>
>> <div>
>>
>> <input type="radio" id="radio1" name="offer" />
>>
>> </div>
>>
>> <div>
>>
>> <label for="radio1">
>>
>> 1 year plan
>>
>> </label>
>>
>> </div>
>>
>>
>>
>> <div>
>>
>> <input type="radio" id="radio2" name="offer" />
>>
>> </div>
>>
>> <div>
>>
>> <label for="radio2">
>>
>> 2 year plan
>>
>> </label>
>>
>> </div>
>>
>>
>>
>>
>>
>> My assumption is that the div tags are causing JAWS not to be able to
>> toggle between the radio buttons via arrow keys. Although the input fields
>> have the same name attribute, the div is identifying to JAWS that this is
>> a different block of HTML. Therefore, the arrow key script is failing.
>>
>>
>>
>> What are your thoughts?
>>
>> >> >> archives at http://webaim.org/discussion/archives
>> >> >> >> archives at http://webaim.org/discussion/archives
>> >>
>> >> >> archives at http://webaim.org/discussion/archives
>> >> >> >> archives at http://webaim.org/discussion/archives
>> >>
>> >> >> archives at http://webaim.org/discussion/archives
>> > > > http://webaim.org/discussion/archives
> >
> > > > >