fix(core): announce typed-invalid state in TimeInput

[bhamodi]

Summary

packages/core/src/TimeInput/TimeInput.tsx computes isInputValid (lines 440-451) — false when the typed value fails parseTimeInput or falls outside min/max — but before this change used it only for the red-border style (!isInputValid && styles.inputInvalid). The screen-reader signals were missing:

• aria-invalid was gated solely on status?.type === 'error' (line 638), so a typed out-of-range time never set aria-invalid.
• There was no live region announcing the rejected entry.

Because the value silently reverts on blur, a screen-reader user got no feedback that their entry was invalid — only sighted users saw the red border. This is a WCAG 3.3.1 (Error Identification) gap.

Every sibling typed-format input already handles this the same way — DateInput (aria-invalid at DateInput.tsx:613-615, alert at 633-635), NumberInput (NumberInput.tsx:643-644, 659-661), and DateTimeInput (DateTimeInput.tsx:1006-1008) — so TimeInput was the lone inconsistency. This fix brings it to parity.

Changes

• packages/core/src/TimeInput/TimeInput.tsx: OR the parsed-invalid flag into aria-invalid (status?.type === 'error' || !isInputValid) and add a VisuallyHidden assertive live region announcing "Invalid time" while the typed input is invalid, mirroring DateInput.
• packages/core/src/TimeInput/TimeInput.test.tsx: added 4 tests — aria-invalid="true" on out-of-range typed input, no aria-invalid on valid input, an alert announcing "Invalid time" when invalid, and an empty alert when valid.

Test plan

• node_modules/.bin/vitest run --root . packages/core/src/TimeInput — 35 pass (was 31), including the 4 new tests.
• Confirmed failing-first: ran the new tests before the fix — the aria-invalid, alert-message, and empty-alert tests all failed (no alert element existed and aria-invalid was never set), proving they catch the gap.
• node_modules/.bin/tsc --project packages/core/tsconfig.json --noEmit — clean.
• node_modules/.bin/eslint packages/core/src/TimeInput/TimeInput.tsx packages/core/src/TimeInput/TimeInput.test.tsx — clean.

Notes

Found during a broader a11y audit of the input components. Scoped to the aria-invalid change and the live region plus tests. DateInput.doc.mjs doesn't document this behavior (and the repo check:sync passes), so no doc change was needed to stay in parity with the siblings.

[vercel]

@bhamodi is attempting to deploy a commit to the Meta Open Source Team on Vercel.

A member of the Team first needs to authorize it.

[cixzhang]

Thanks @bhamodi — typed-invalid announcement is verbatim parity with the sibling inputs; fires on transition, not per keystroke. 🙏