WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Multiple choice with radio buttons - WCAG conformant markup

for

From: Birkir R. Gunnarsson
Date: Apr 7, 2018 11:16AM

This accessibility comparison article says that Google Forms produces
accessible radiobuttons:
http://terrillthompson.com/blog/854

I've been able to create accessible survey questions using Survey
Monkey (admittedly I don't remember how) and Qualtrics (admittedly not
the free version)

I personally always call not using a legend or ARIA group +
aria-labelledby an accessibility defect. aXe does too if the form
controls in the group share a name attribute.
If we look at 1.3.1 the question is how clear the association is
visually, if there is a box around the question and answers we need
something equally strong programmatically, if not, I guess it can be
argued that marking the question as a heading may be good enough. This
is why accessibility is, and remains, a judgment call.
I am privileged in that I can make key decisions for my program but I
am always looking for better decisions, either stricter or more
reasonable, so I like seeing how other accessibility folks interpret
common situations.

Cheers
-B


On 4/7/18, Glen Walker < <EMAIL REMOVED> > wrote:
> While the headings help, if you tab through the form, all you'll hear is
> "yes"/"no" with no context. You can shift+"H" on every question to go back
> to the heading to hear the question, but only once you've figured out the
> pattern.
>
> If you were building the survey yourself, then it'd be easy to add a <div
> role="radiogroup" aria-labelledby="q1heading"> around the list of radio
> buttons. But I'm not sure you'll find a survey that does that.
>
> Sent from my iPad
>
>> On Apr 5, 2018, at 9:50 PM, Detlev Fischer < <EMAIL REMOVED> >
>> wrote:
>>
>>
>>>> Am 06.04.2018 um 00:55 schrieb Jared Smith < <EMAIL REMOVED> >:
>>>>
>>>> I have seen forms like this with tabindex=0 put on the question so as
>>>> you tab through the form the context is pretty clear.
>>>
>>> I'd advise against this approach. Anything that is navigable via Tab
>>> key should also be actionable (almost always a link or button).
>>
>> Maybe I should have been clearer that this was not meant as recommended
>> practice. All I meant was that in a survey context with a repeating
>> pattern of questions and answers, it may still be preferable to *no*
>> proper markup of the radio inputs at all. Others may disagree.
>> >> >> >> > > > > >


--
Work hard. Have fun. Make history.