Login submit error message missing `aria-live`, not announced by screen readers

[Nixxx19]

p5.js version

Latest

What is your operating system?

Mac OS

Web browser and version

all

Actual Behavior

The submit-level "invalid credentials" error in LoginForm.tsx (line 108) is missing an aria-live attribute:

{submitError && !modifiedSinceLastSubmit && (
  <span className="form-error">
    {t('LoginForm.Errors.invalidCredentials')}
  </span>
)}

Screen readers do not announce this error when it dynamically appears after a failed login. The per-field error in the same file (line 101) already has aria-live="polite" correctly, so this is an inconsistency within the same component.

This violates WCAG 2.2 SC 4.1.3 (Status Messages).

Expected Behavior

The submit error span should include aria-live="assertive" so screen readers announce the login failure:

{submitError && !modifiedSinceLastSubmit && (
  <span className="form-error" aria-live="assertive">
    {t('LoginForm.Errors.invalidCredentials')}
  </span>
)}

Steps to reproduce

1. Go to the login page
2. Use a screen reader (e.g., VoiceOver on macOS)
3. Enter invalid credentials and submit the form
4. The error appears visually but is not announced by the screen reader

[Nixxx19]

Hi @raclim!

I'd love to work on this issue and submit the fix for it.

[raclim]

Thanks for catching this @Nixxx19! Just assigned it to you!

[Nixxx19]

Hi @raclim!

While working on the fix for the LoginForm.tsx submit error, I did a full audit of the codebase and found that several other components also have form-error spans missing the aria-live attribute - same WCAG 2.2 SC 4.1.3 violation:

File	Missing aria-live spans
ResetPasswordForm.tsx	1 (field error)
AccountForm.tsx	4 (field errors)
NewPasswordForm.tsx	2 (field errors)
CollectionCreate.jsx	2 (1 submit error + 1 validation error)
NewFileForm.jsx	1 (field error)
NewFolderForm.jsx	1 (field error)

I've already prepared fixes for all of these - using aria-live="polite" for per-field validation errors (consistent with the existing pattern in LoginForm.tsx and SignupForm.tsx) and aria-live="assertive" for submit-level errors.

Would it be okay to include these in my PR for this issue, since they're the same type of fix?
Or would you prefer I open a separate issue to track them?