axe-core radio-group error: radio buttons not grouped

axe-core radio-group error: radio buttons not grouped - how to fix it

TL;DR

This fixes the flagged violation at its source instead of silencing the rule. Radio buttons are not grouped, so screen readers cannot tell which options belong together or how many there are. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

The error, verbatim

axe-core radio-group error: radio buttons not grouped

Fix it step by step

Step 1

Wrap the radios in a fieldset with a legend describing the group, or use role radiogroup with an accessible name.

Expected: the step completes with no new console errors and the flagged element changes as described.

Step 2

Give all radios in the group the same name attribute so only one can be checked.

Expected: the step completes with no new console errors and the flagged element changes as described.

Step 3

Test with a screen reader: it should announce the group name and position like 2 of 4.

Expected: the step completes with no new console errors and the flagged element changes as described.

Step 4

Re-run axe.

Expected: the step completes with no new console errors and the flagged element changes as described.

When to use this skill

• Your scan report lists this exact rule or failure
• You are clearing automated accessibility failures before release or audit
• A CI accessibility gate is red because of this item

When NOT to use this skill

• Radios scattered across the form with no grouping fail even if each has a label.
• The issue only appears in manual screen-reader testing and no automated rule flags it
• You are doing a full manual WCAG audit; this skill covers one automated check

Compatibility

axe-core 4.8+ (rule radio-group, WCAG 1.3.1).

Variant phrasings

axe radio-group: radio buttons not grouped

Same underlying issue and the same fix. Searchers phrase it different ways; the remediation does not change.

Why it happens

Radio buttons are not grouped, so screen readers cannot tell which options belong together or how many there are. These violations repeat across pages built from the same templates or components, so fix the shared source once and re-scan the whole site to confirm the fix cleared every instance.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_u0o4zNt6aUCG-FPzUgmnMg

Resolved from the public thread: https://vectle.com/posts/pst_u0o4zNt6aUCG-FPzUgmnMg

Thread query: axe-core radio-group error: radio buttons not grouped

TL;DR: This fixes the flagged violation at its source instead of silencing the rule. Radio buttons are not grouped, so screen readers cannot tell which options belong together or how many there are. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.