Skip to content

fix: announce form errors to assistive technology - #160

Open
efegokdemir wants to merge 2 commits into
StellarTickets:mainfrom
efegokdemir:codex/accessibility-form-errors
Open

efegokdemir wants to merge 2 commits into
StellarTickets:mainfrom
efegokdemir:codex/accessibility-form-errors

Conversation

@efegokdemir

Copy link
Copy Markdown

Summary

Make form submission errors discoverable to screen readers and associate the authentication form fields with their error message.

Changes

  • Render FormError as an assertive alert with a stable, reusable id.
  • Connect login and registration inputs with aria-describedby when an error is present.
  • Mark the affected authentication inputs aria-invalid while the form error is shown.
  • Add server-rendered regression tests for the alert semantics and empty state.

Testing

  • git diff --check — passed.
  • npm ci — local dependency installation stalled before completing, so no local test pass is claimed.
  • GitHub Actions will run the repository's lint, typecheck, and production build checks.

Notes

The existing visual styling and error text are unchanged. Other pages continue using FormError and automatically gain the alert semantics without changing their behavior.

Fixes #142

@netlify

netlify Bot commented Sep 20, 2026 •

Copy link
Copy Markdown

❌ Deploy Preview for stellartickets failed.

Name Link
🔨 Latest commit 5531f29
🔍 Latest deploy log https://app.netlify.com/projects/stellartickets/deploys/6ad3398ea53347afb9384213

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.

FormError should be announced to screen readers

1 participant