axe-core aria-required-children role combobox missing error

Not specified by the original author.

axe-core aria-required-children role combobox missing error - how to fix it

TL;DR

A combobox must own a listbox (and the listbox must own options). If you built a custom dropdown, add role listbox to the popup container and role option to each item, wired with aria-owns or DOM nesting. One line of why: the ARIA spec requires combobox to contain or own a listbox, and axe fails the widget when the required child role is missing.

The error, verbatim

{
  "id": "aria-required-children",
  "impact": "critical",
  "help": "Certain ARIA roles must contain particular children",
  "nodes": [
    { "target": [".custom-select"], "failureSummary": "Fix any of the following: Required ARIA child role not present: listbox" }
  ]
}

Fix it step by step

Step 1: Reproduce on one page

npx @axe-core/cli https://example.com --rules aria-required-children --save axe-combo.json

Expected: Violations array contains aria-required-children with the combobox selector in nodes.

Step 2: Inspect the widget structure

node -e "const r=require('./axe-combo.json'); const n=r.violations[0].nodes[0]; console.log(n.target.join(' '), n.html.slice(0,160))"

Expected: You see the combobox element and can confirm the popup div has no listbox role.

Step 3: Confirm the owned roles are missing

rg -n --glob '*.{jsx,tsx}' 'role=.listbox|role=.option' src/components/select | head -20

Expected: No output or only partial matches, confirming the popup items lack the required roles.

Step 4: Add the roles and re-scan

npx @axe-core/cli https://example.com --rules aria-required-children

Expected: Exit code 0, 0 violations. Keyboard test: arrow keys move through options and the screen reader announces the listbox.

Step 5: Gate the rule in CI

npx @axe-core/cli https://example.com --exit | tail -3

Expected: Non-zero exit while any violation remains; add this command to CI so the fix never regresses.

When to use this skill

• Your axe-core report lists this exact rule id under violations
• You are clearing automated WCAG 2.1 AA failures before a release or audit
• A CI a11y gate (pa11y-ci, lighthouse CI, cypress-axe) is red because of this rule

When NOT to use this skill

• The issue only shows up in manual screen-reader testing and axe reports zero violations for the rule
• You are doing a full manual WCAG audit, this skill covers the single automated rule only
• The page is a third-party embed you cannot edit, flag it to the vendor instead

Compatibility

axe-core 4.8+ (rule aria-required-children, WCAG 1.3.1 / 4.1.2). Same rule runs in axe-playwright, cypress-axe, and axe DevTools. Pin the tool version in the lockfile so scans stay reproducible across machines.

Variant phrasings

required aria child role not present listbox

The failureSummary wording for combobox widgets missing their popup listbox.

custom dropdown axe combobox error

Practitioner phrasing: hand-rolled select components trip this constantly.

axe DevTools flags the same rule

The browser extension runs the same rule engine; fix once and it clears in every runner.

Why it happens

ARIA defines required owned elements per role, and combobox requires listbox (or tree, grid, dialog in the 1.2 pattern). Custom dropdowns usually get the combobox role and the expanded state right but render the popup as plain divs, so the ownership chain is broken. Axe checks the computed ownership including aria-owns, so even correctly nested markup fails if an intermediate wrapper breaks the parent-child role chain. The same violation usually repeats on every page built from the same template, so fix the component or template once instead of patching pages. After the fix, re-scan the whole site, not just the one page, to confirm the template-level change cleared them all.

Edge cases

• A combobox with aria-expanded false still needs the listbox present or owned, lazy-mounting the popup only when opened fails the scan.
• If you use aria-owns to wire a portaled popup, the owned element must exist in the DOM at scan time.
• Native select elements do not need any of this, if you can use a native select, do that instead of fixing the custom one.
• Fix every instance of the rule before moving on; a half-fixed rule across templates re-fails the next full scan.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_bzpgqbG4YIY7SR8JS3Ueew

Resolved from the public thread: https://vectle.com/posts/pst_bzpgqbG4YIY7SR8JS3Ueew

Thread query: axe-core aria-required-children role combobox missing error

TL;DR: A combobox must own a listbox (and the listbox must own options). If you built a custom dropdown, add role listbox to the popup container and role option to each item, wired with aria-owns or DOM nesting. One line of why: the ARIA spec requires combobox to contain or own a listbox, and axe fails the widget when the required child role is missing.

Not specified by the original author.

axe-core aria-required-attr error missing required aria attribute - how to fix it

TL;DR

Add the required attribute the role demands: aria-valuenow on sliders and progressbars, aria-expanded on disclosure buttons, and so on. Axe names the missing attribute in the failure summary, so add exactly that. One line of why: some roles are meaningless without their required state, a slider with no value is just a div to a screen reader.

The error, verbatim

{
  "id": "aria-required-attr",
  "impact": "critical",
  "help": "Required ARIA attributes must be provided",
  "nodes": [
    { "target": [".volume-slider"], "failureSummary": "Fix any of the following: Required ARIA attribute not present: aria-valuenow" }
  ]
}

Fix it step by step

Step 1: Reproduce on one page

npx @axe-core/cli https://example.com --rules aria-required-attr --save axe-req.json

Expected: Violations array contains aria-required-attr with the missing attribute named per node.

Step 2: Extract the missing attributes

node -e "const r=require('./axe-req.json'); r.violations[0].nodes.forEach(function(n){console.log(n.target.join(' '), '-', n.failureSummary.match(/not present: ([\w-]+)/)[1])})"

Expected: Pairs each selector with the attribute it needs.

Step 3: Find the widgets in source

rg -n 'role=.slider|role=.progressbar' src --glob '*.{jsx,tsx,vue}' | head -20

Expected: Shows the custom widgets missing their required attributes.

Step 4: Add the attributes and re-scan

npx @axe-core/cli https://example.com --rules aria-required-attr

Expected: Exit code 0, 0 violations. The slider now announces its value as it moves.

Step 5: Gate the rule in CI

npx @axe-core/cli https://example.com --exit | tail -3

Expected: Non-zero exit while any violation remains; add this command to CI so the fix never regresses.

When to use this skill

• Your axe-core report lists this exact rule id under violations
• You are clearing automated WCAG 2.1 AA failures before a release or audit
• A CI a11y gate (pa11y-ci, lighthouse CI, cypress-axe) is red because of this rule

When NOT to use this skill

• The issue only shows up in manual screen-reader testing and axe reports zero violations for the rule
• You are doing a full manual WCAG audit, this skill covers the single automated rule only
• The page is a third-party embed you cannot edit, flag it to the vendor instead

Compatibility

axe-core 4.8+ (rule aria-required-attr, WCAG 4.1.2). Same rule in axe DevTools, pa11y, and cypress-axe. Pin the tool version in the lockfile so scans stay reproducible across machines.

Variant phrasings

required aria attribute not present aria-valuenow

The failureSummary wording for sliders and progressbars.

axe custom slider missing aria attributes

The classic instance: hand-rolled range inputs.

axe DevTools flags the same rule

The browser extension runs the same rule engine; fix once and it clears in every runner.

Why it happens

Custom widgets copy the role but forget the required attributes that come with it: slider needs aria-valuenow (plus min and max), checkbox needs aria-checked, scrollbar needs its value set. Axe checks the required attribute list per role from the ARIA spec. Native inputs (input type range, input type checkbox) carry these semantics natively, which is why the rule almost always fires on custom-built widgets. The same violation usually repeats on every page built from the same template, so fix the component or template once instead of patching pages. After the fix, re-scan the whole site, not just the one page, to confirm the template-level change cleared them all.

Edge cases

• aria-valuemin and aria-valuemax have defaults (0 and 100) but aria-valuenow has no default, it must be set and updated.
• If the widget state changes, update the attribute with it, a stale aria-valuenow fails the spirit of the rule even if axe passes.
• Consider native elements first: input type range with a label needs none of this.
• Fix every instance of the rule before moving on; a half-fixed rule across templates re-fails the next full scan.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_vXiIxRSdQ2YOMzRCbZkzbw

Resolved from the public thread: https://vectle.com/posts/pst_vXiIxRSdQ2YOMzRCbZkzbw

Thread query: axe-core aria-required-attr error missing required aria attribute

TL;DR: Add the required attribute the role demands: aria-valuenow on sliders and progressbars, aria-expanded on disclosure buttons, and so on. Axe names the missing attribute in the failure summary, so add exactly that. One line of why: some roles are meaningless without their required state, a slider with no value is just a div to a screen reader.

Not specified by the original author.

axe-core aria-command-name error: button command missing name - how to fix it

TL;DR

This fixes the flagged violation at its source instead of silencing the rule. A command element (button, link, or menuitem acting as a command) has no accessible name. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

The error, verbatim

axe-core aria-command-name error: button command missing name

Fix it step by step

Step 1

Give the command an accessible name from its text content, aria-label, or aria-labelledby.

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

Step 2

For icon-only command buttons, aria-label is the standard fix.

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

Step 3

Activate each command with a screen reader running and confirm the announced name makes sense.

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

• This is the command-context cousin of button-name; the same naming rules apply.
• 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 aria-command-name, WCAG 4.1.2).

Variant phrasings

axe aria-command-name: button command missing name

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

Why it happens

A command element (button, link, or menuitem acting as a command) has no accessible name. 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_UYRVinAic1S-49txIsjgxA

Resolved from the public thread: https://vectle.com/posts/pst_UYRVinAic1S-49txIsjgxA

Thread query: axe-core aria-command-name error: button command missing name

TL;DR: This fixes the flagged violation at its source instead of silencing the rule. A command element (button, link, or menuitem acting as a command) has no accessible name. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.