SC 332 -- Fieldset issue on tenant and homeowner pages

[damiansian]

URL

https://demo.fileyourstatetaxes.org/en/questions/nj-eligibility-health-insurance

Issue

Each checkbox option has its own fieldset so the grouping semantics is read aloud as each option were its own group instead of all the options belonging to a larger group.

Screen shot

Screen shot shows each input has its own fieldset

WCAG Success Criterion

SC 3.3.2: Labels or Instructions (Level A)

Impacted users

Screen reader users rely on labels and instructions to understand how to fill out form elements properly.

Suggested fix

You can reference these solutions on CodePen:
https://codepen.io/dsian108/pen/YPKEoje?editors=1000

[mmazanec22]

@damiansian on these pages we've got some checkboxes that show and hide other checkboxes. How should we handle that? I had aria-controls on there to associated the showing checkbox with the shown but axe flagged it as a misapplied role.

[damiansian]

@mmazanec22

This page was a bit odd to me for several reasons:

1. The first response is not a question, it's a statement.
2. Two responses (two and three) that are in fact questions do not create any conditional outcome like the fourth response.
3. Now the fourth response's question does spawn a conditional response that is a statement like response number one.

One question I have is this... How important is it to make the last statement response conditional when the first response is also a statement and not a question? What is the level of importance in making this conditionally visible?

Also, might it be preferable to expose the relationship of Single-unit properties versus Multi-unit properties?

I have a proposal here in CodePen
https://codepen.io/dsian108/pen/ogvEWeR?editors=1000