E-mail List Archives
Re: HTML Fieldset missing a Legend
From: wolfgang.berndorfer@zweiterblick.at
Date: Nov 4, 2021 9:00AM
- Next message: Patrick H. Lauke: "Re: HTML Fieldset missing a Legend"
- Previous message: Laurence Lewis: "HTML Fieldset missing a Legend"
- Next message in Thread: Patrick H. Lauke: "Re: HTML Fieldset missing a Legend"
- Previous message in Thread: Laurence Lewis: "HTML Fieldset missing a Legend"
- View all messages in this Thread
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.
Wolfgang
-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Laurence Lewis
Sent: Thursday, November 4, 2021 4:06 AM
To: <EMAIL REMOVED>
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.
Regards
Laurence Lewis
Accessibility Senior Specialist - Telstra
- Next message: Patrick H. Lauke: "Re: HTML Fieldset missing a Legend"
- Previous message: Laurence Lewis: "HTML Fieldset missing a Legend"
- Next message in Thread: Patrick H. Lauke: "Re: HTML Fieldset missing a Legend"
- Previous message in Thread: Laurence Lewis: "HTML Fieldset missing a Legend"
- View all messages in this Thread