Test case for radio buttons should not use list markup about accessible-forms HOT 2 CLOSED

Hey Rachel,

Thank you very much for raising this. I've added two new test cases, removing the lists inside the fieldsets:

https://russmaxdesign.github.io/accessible-forms/01-input-radio-group-without-list.html

https://russmaxdesign.github.io/accessible-forms/07-nested-fieldset-without-list.html

As you have said, the relevant legends are announced better using this method. In the case of the nested fieldsets, only the innner legends are announced.

I would like to tweet these two updates today and give you credit at your handle if ok: https://twitter.com/rleggos

One thing I would push back on slightly: I think it is an acceptable solution to use lists for radio groups, from a semantic perspectives. Fundamentally, I see radio groups and checkbox groups as lists of options. Regardless, this is personal opinion, and there is definite evidence that Voiceover support is far better when they are NOT housed in lists. :)

Thanks again!
Russ

from accessible-forms.

I think you're probably right that it is a matter of personal preference whether to include list markup in a group of radio buttons or checkboxes. My thinking is if radio buttons are already grouped by using the name attribute correctly, and further by using fieldset/legend to provide a group label, they don't also need to be a list. E.g. should they really show up in both the form and list pages in the VO rotor?

Anyway, that's just my two cents. :) Thanks for adding those test cases and thanks again for this great resource! I've referenced it several times since someone I work with shared it on Teams last week.

from accessible-forms.