dai11y 29/09/2021

Your daily frequent11y newsletter, brought to you by @ChrisBAshton:

Three radio buttons. One is selected. The selected one has a text input associated with it; hence "conditional reveal".
Screenshot of the ‘conditional reveal’ behaviour.

An update on the accessibility of conditionally revealed questions

  • A GOV.UK blog about the ‘conditional reveal’ option in the GDS Design System’s radio and checkbox components.
  • The GOV.UK Accessibility Team discovered that the implementation failed WCAG 2.1 Success Criterion 4.1.2: Name, Role, Value, as the act of conditionally revealing content would not notify some screen reader users.
  • This came down to the use of aria-expanded, which the team later realised was “not supported for the role of a radio button or checkbox in the ARIA specification.”
  • Further user research found that some users were in fact notified of changes, despite it not being supported. Additionally, the notification did help users; so they brought their findings to the ARIA Working Group for consideration.
  • The team then prototyped a few different ways of improving the relationship between the question and the revealed content. The conclusion was to avoid using “multiple fields or text content (like warning text) within reveals”. Simple questions with a single input were fine.

Prefer longer newsletters? You can subscribe to week11y, fortnight11y or even month11y updates! Every newsletter gets the same content; it is your choice to have short, regular emails or longer, less frequent ones. Curated with ♥ by developer @ChrisBAshton.

Loading...