Skip to content

fix([issue-4282]): generalize repo-wide input accessible-name checks - #4301

Merged
atomantic merged 6 commits into
mainfrom
next/issue-4282
Aug 15, 2026
Merged

fix([issue-4282]): generalize repo-wide input accessible-name checks#4301
atomantic merged 6 commits into
mainfrom
next/issue-4282

Conversation

@atomantic

Copy link
Copy Markdown
Owner

Closes #4282

Summary

  • Generalize the client input accessible-name guard from Instances to all tracked JSX files.
  • Recognize usable ARIA names, hidden inputs, explicit and implicit labels, native button-like names, and first-child FormField associations.
  • Keep exact pre-existing source-anchor exceptions and track their remediation in Add accessible names to pre-existing unlabeled input controls #4297.

Tests

  • cd client && npm test -- --run src/a11yConventions.test.js
  • cd client && npm test -- --run
  • cd client && npm run lint
  • cd client && npm run build
  • git diff --check
  • Codex bounded audit: partial; 939 inputs scanned, 0 new offenders

@atomantic
atomantic merged commit 6ce2689 into main Aug 15, 2026
7 checks passed
@atomantic
atomantic deleted the next/issue-4282 branch August 15, 2026 18:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Generalize the Instances-only input-accessible-name a11y test repo-wide

1 participant