WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: HTML Fieldset missing a Legend


From: Mark Magennis
Date: Nov 4, 2021 9:53AM


The latest versions of JAWS and NVDA seem to no longer announce the legend for each field in the fieldset. Is that your experience too? I always suspected this could be a bit of a pain.


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of <EMAIL REMOVED>
Sent: 04 November 2021 15:00
To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
Subject: [EXTERNAL] Re: [WebAIM] HTML Fieldset missing a Legend

If I navigate in an option group (e.g., Yes/No) without fieldset and legend, a Screen Reader can't technically announce the associated Question.

So, for me it would be a clear failure of 1.3.1 and 4.1.2.

An exception probably would be if You gave each option a clarifying name with aria-label etc.
I wouldn't generally advice this technique because of double needs for managing updates.

But also: For UX for SR keep the legend short and precise:
Listening to a verbose description for each item of a group of options or checkboxes is annoying.


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Laurence Lewis
Sent: Thursday, November 4, 2021 4:06 AM
Subject: [WebAIM] HTML Fieldset missing a Legend

The HTML Spec says that the <legend> element is optional for a <fieldset>.
I am interested to understand if not having a Legend is a WCAG 1.3.1 Info and Relationships or 3.2.2 Labels or Instructions.
I do not believe not naming a Fieldset is a WCAG fail for either sc, and would appreciate the opinions of others. Thanks.

Laurence Lewis
Accessibility Senior Specialist - Telstra