WebAIM - Web Accessibility In Mind

E-mail List Archives

Dynamic fields - disabled CSS experience?

for

From: Judith.A.Blankman@wellsfargo.com
Date: Nov 4, 2016 5:10PM

When an experience relies on CSS to deliver a dynamic experience, is it reasonable (and/or required by WCAG) to expect an exactly matched experience when CSS is turned off?

For example, in a fieldset, the selection of an option in a drop down, or the selection of a radio button, initiates the list of options presented in a subsequent field. It might even determine the display of a secondary field. CSS drives whether fields are hidden or present.

A tester identified a confusing experience in a complex interaction when CSS was turned off. The secondary field choices were available prior to the first field selection being made. While this doesn't prevent the completion of a task, I realize it's confusing when fields are populated out of order.

Should developers dynamically disable a field vs. just hiding it until the selection in the first field is made?

I'm also wondering if turning off CSS when using online forms is a likely use case for people with low vision, who have display preferences for a range of needs, or prefer their own style sheets, etc. Or, do people with display preferences choose to not turn off CSS when using online forms due to their complexity?

I definitely don't want to deliver something that is confusing. Am trying to gauge the impact.

Just another Friday afternoon scratching my head ...

Thanks!

Judith Blankman