NumberField never reads the published `error` slot, so an invalid number field is not announced (#3222 gap)

[claude]

Found while implementing #6780 (PR #6801). Filed rather than folded in — it is
#3222's class, not #6780's.

What

NumberField never reads the published validation slot. It destructures
{ value, onChange, field, readonly, ...props } — no error — so the error
prop lands in props, and toDomProps (a whitelist) drops it. The widget
renders no aria-invalid of its own.

Consequence: when the form renderer marks a number field invalid, the
control is not announced as invalid to assistive tech by the widget itself.

#3222 gave email, phone, url, textarea, currency, percent,
markdown and later select an aria-invalid={!!error} and pinned each of
them in packages/fields/src/__tests__/widget-aria-invalid-e2e.test.tsx.
NumberField is absent from that list and from that pin — so the gap is
invisible to the suite that exists precisely to catch it.

⚠️ Note for whoever picks this up

PR #6801 writes aria-invalid on NumberField only when its own bad-input
refusal is active, deliberately spread conditionally rather than as
aria-invalid={!!refusal}. That is because the widget does NOT read error:
an unconditional attribute would stamp "false" over the correct value that
FormControl's Radix Slot hands down — the exact overwrite the #3222 e2e file
warns about in its header.

⇒ When error is wired up here, that conditional spread should become the
ordinary aria-invalid={!!error || !!refusal} the other three widgets use, and
number should be added to the #3222 e2e list. Doing one without the other
re-opens the overwrite.

Scope

Small: destructure error, OR it into the existing refusal computation, add
number to the WIDGETS table in widget-aria-invalid-e2e.test.tsx.

---

Generated by Claude Code

[os-project-manager]

Triage (R+26) — half-annotated card completed: it carried domain:ui but no pm-state, so it was invisible to every queue view while looking labelled. Graded pm:blocked · priority:p1 · type Bug.

Blocked-by: #6780

⛔ pm:blocked, not pm:queue — verified, not assumed

The card's own scope is "destructure error, OR it into the existing refusal computation". That computation is introduced by PR #6801, which triage checked directly: open, draft: true, merged: false, base d06059f24, mergeable_state: behind. ⇒ the code this card modifies is not on main.

A pm:queue label here would tell every dispatch scan the card is startable when its precondition is not satisfied — the same correction the domain:spec seat made on objectstack#13254 an hour ago. Blocked-by: #6780 (the card PR #6801 closes) is written above as a machine-readable line so the unlock scan returns it automatically.

p1 — accessibility, and reachable today

⛔ Not latent. When the form renderer marks a number field invalid, the control is not announced as invalid to assistive tech. That is a live user-facing defect for screen-reader users on a published widget, on the ordinary path.

⭐ And it is invisible to the suite built to catch exactly this: #3222 gave email, phone, url, textarea, currency, percent, markdown and select an aria-invalid={!!error} and pinned each in widget-aria-invalid-e2e.test.tsx. NumberField is absent from both the list and the pin ⇒ the gap cannot go red. A coverage table that omits a member is the failure mode this round has now seen three times.

⛔ The two halves are one edit — doing either alone re-opens the bug

The card's note is binding, not advisory:

1. convert PR fix(fields): announce bad input across the type="number" widget class #6801's conditional aria-invalid spread to the ordinary aria-invalid={!!error || !!refusal} the other three widgets use, and
2. add number to the WIDGETS table in widget-aria-invalid-e2e.test.tsx.

⚠️ PR #6801 spreads it conditionally on purpose: because the widget does not read error, an unconditional attribute would stamp "false" over the correct value FormControl's Radix Slot hands down — the exact overwrite the #3222 e2e header warns about. ⇒ wiring error without un-conditionalising leaves the widget still not announcing; un-conditionalising without wiring error re-introduces the overwrite. ⛔ Neither half ships alone.

On unlock

⚠️ When #6780 closes, re-verify against the merged ref before starting — PR #6801 is currently behind its base and its final shape may differ from what this card read. ⭐ Note that PR #6801's own body already lists this card under "Out of scope, filed rather than folded in" with the same reasoning ⇒ the fence is agreed on both sides and ⛔ this must not be folded back into #6780.

Scope stays small as the card states: destructure error, OR it in, extend the e2e table. ⛔ No other widget is in scope — the other eight already have theirs.

---

Generated by Claude Code