Related form controls not grouped with fieldset — the fix
Groups of related form controls (such as radio buttons or checkboxes) are not wrapped in a <fieldset> element with a <legend>. This makes it difficult for screen reader users to understand the relationship between controls.
Where this fits: accessibility in SEO
Accessibility overlaps heavily with SEO because both depend on machine-readable structure: alt text, heading hierarchy, labels, contrast. Screen readers and search crawlers consume the same signals. Accessible sites rank better not by special treatment but because the same fixes — descriptive alt attributes, proper headings, real link text — are exactly what search engines parse for meaning. It is also, in a growing number of jurisdictions, the law.
Why related form controls not grouped with fieldset hurts your rankings
Without fieldset and legend, screen reader users hear individual radio buttons or checkboxes without understanding what group they belong to. For example, a user might hear 'Red, radio button' without knowing it is part of a 'Choose a color' group. This is a WCAG 2.1 Level A requirement.
This is a low-severity issue: a polish item. Fix it in batches during scheduled maintenance; the win is cumulative quality, not a step change.
How to fix it
Wrap groups of related form controls in a <fieldset> element and provide a <legend> that describes the group's purpose.
<fieldset>
<legend>Choose a color</legend>
<label><input type="radio" name="color" value="red" /> Red</label>
<label><input type="radio" name="color" value="blue" /> Blue</label>
</fieldset>Accessibility best practices
- Give every informative image an alt attribute that describes its content; decorative images get alt="".
- Maintain heading hierarchy — never skip levels for styling reasons.
- Make link text meaningful out of context; screen readers list links in isolation.
- Keep text contrast at WCAG AA (4.5:1) minimum.
- Make everything keyboard-operable with a visible focus state.
The full library: SEO best practices, by category.
Frequently asked questions
What does "Related form controls not grouped with fieldset" mean?
Groups of related form controls (such as radio buttons or checkboxes) are not wrapped in a <fieldset> element with a <legend>. This makes it difficult for screen reader users to understand the relationship between controls.
Why does related form controls not grouped with fieldset matter for SEO?
Without fieldset and legend, screen reader users hear individual radio buttons or checkboxes without understanding what group they belong to. For example, a user might hear 'Red, radio button' without knowing it is part of a 'Choose a color' group. This is a WCAG 2.1 Level A requirement.
How do I fix related form controls not grouped with fieldset?
Wrap groups of related form controls in a <fieldset> element and provide a <legend> that describes the group's purpose.
How serious is this issue?
This is a low-severity issue: a polish item. Fix it in batches during scheduled maintenance; the win is cumulative quality, not a step change. It belongs to the accessibility family of checks.
How do I find every page affected by this on my site?
Run a free Dr Urls audit: it crawls your site, detects related form controls not grouped with fieldset on every affected page, shows example URLs, and generates a ready-to-use fix task. Re-scan after fixing to verify the issue is gone.
Does your site have this issue?
A free Dr Urls audit crawls your site, finds every page affected by related form controls not grouped with fieldset, and hands you a ready-made fix task.
Check my site free