Missing accessible names: DonutChart, List, ListItem and several stories warn in every dev run

[mfal]

50 react-aria warnings across the docs site and Storybook, all variations of "this element has no accessible name". Each one is a real a11y gap, not console noise.

If you do not provide a visible label, you must specify an aria-label or aria-labelledby attribute for accessibility

Stack traces put the warning inside react-aria's own components, reached from ours:

Origin	Where it shows
DonutChart renders react-aria ProgressBar with no label	data-visualisation-donutchart--default, --with-unit, --with-text-value
Slider	form-controls-slider--default, --with-format-options, 04-components/form-controls/slider
Select	form-controls-select--with-country-options, --with-country-options-and-custom-sort
Modal	overlays-modal--long-content
ProgressBar	04-components/status/progress-bar

The docs examples for Slider and ProgressBar do pass a <Label>, so the warning comes from an inner react-aria element that never receives it — worth checking whether the label is forwarded, not just adding labels at the call site.

DonutChart has no label API at all today. Deciding what its ProgressBar should be called (or whether it should be aria-hidden with the value exposed elsewhere) is a UX question.

An aria-label or aria-labelledby prop is required for accessibility

15 occurrences, all from react-aria's GridListInner — i.e. List rendering a GridList with no accessible name:

structure-list-listitem--with-content, --with-action-group, --with-custom-tile-max-width, --with-checkbox, --with-column-layout

A textValue prop is required for <GridListItem> elements with non-plain text children

33 occurrences — the largest single group. Type-to-select does not work on these items.

structure-list--with-summary, --infinite-scroll, --with-accordion, structure-list-edge-cases--custom-sorting

Scope note

Fixing this properly needs decisions the code cannot make: any label that ships inside a component becomes UI text and belongs in locales/de-DE.locale.json + locales/en-US.locale.json, which follows product voice. Story-level labels are free.

Found while clearing the warnings in #3019.

[mfal]

A second console sweep — all 443 Storybook stories, loaded and clicked through (up to 12 interactions each, overlays opened), two full passes with identical results — confirms this issue's findings and adds three origins it does not list yet.

LightBox renders a dialog with no title — overlays-lightbox--with-controller, two warnings at once:

• If a Dialog does not contain a <Heading slot="title">, it must have an aria-label or aria-labelledby attribute for accessibility.
• A dialog must have a title for accessibility.

Only reachable by opening the lightbox, which is why a load-only sweep misses it.

Menu without an accessible name — status-badge--with-context-menu. Stack frame is react-aria's MenuInner, not the GridListInner this issue attributes the whole group to. Same message, different origin.

Slider also warns through the react-hook-form integration — integrations-react-hook-form-slider--default, --with-field-error, --with-focus, on top of the form-controls-slider--* stories already listed. Adds --with-initial-marker too.

Two notes on method, since the counts here differ from the original sweep:

• Storybook compiles story modules on demand, so a fixed wait after page.goto reads the console before the story has rendered. Waiting for actual render turned 6 hits into 241. A sweep with a fixed timeout reports "clean" when it is not.
• Modal stories render into a portal and never fill #storybook-root, so a render-wait keyed to that element times out and silently skips them.

Not filed separately, since they are the same class this issue already tracks. The two systemic findings from the same sweep that are not in scope here went to #3027 (useControlledHostValueProps) and #3028 (Option losing textValue and value).