E-mail List Archives
Re: Multiple choice with radio buttons - WCAG conformant markup
From: Jared Smith
Date: Apr 5, 2018 4:55PM
- Next message: Jonathan Cohn: "Re: Permanent A11Y Opportunity in New York City"
- Previous message: Jared Smith: "Re: Spell out "Q&A""
- Next message in Thread: Detlev Fischer: "Re: Multiple choice with radio buttons - WCAG conformant markup"
- Previous message in Thread: Detlev Fischer: "Re: Multiple choice with radio buttons - WCAG conformant markup"
- View all messages in this Thread
The <h3> in this case does provide a semantic relationship between the
question and the possible responses. I think it may be a stretch to
call this a WCAG 1.3.1 failure, though a fieldset/legend is clearly
much better (though these weren't supported by many screen readers
until recently - and are still not supported in Chrome).
> 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). It
could be very confusing to the user why they are navigating to
something that doesn't do anything.
Thanks,
Jared
- Next message: Jonathan Cohn: "Re: Permanent A11Y Opportunity in New York City"
- Previous message: Jared Smith: "Re: Spell out "Q&A""
- Next message in Thread: Detlev Fischer: "Re: Multiple choice with radio buttons - WCAG conformant markup"
- Previous message in Thread: Detlev Fischer: "Re: Multiple choice with radio buttons - WCAG conformant markup"
- View all messages in this Thread