Fields with errors are not marked as invalid

Why does it matter?

Screen reader users move from field to field to find what needs fixing. With aria-invalid="true" they hear "invalid entry" on each field in error; without it, a red border is all there is, and they cannot see it.

Who it affects: Keyboard and screen reader users filling in forms, people with low vision who rely on clear hover and focus styles, people distracted or made unwell by motion, and anyone who finds their way around a site by its menus and help links.

What does Lumtera flag?

Found by Lumtera Pro's form tests (the Forms card of Lumtera → Checks → Page checks, "Test form"): a field that shows an error message after the empty submission but has no aria-invalid="true". For review; fields with the same problem are grouped. Nothing is sent: a safety guard stops any email, form entry or order while the test runs.

Check ID form-error-no-invalid, as shown in review mode and saved results.

How do I fix it in WordPress?

Add aria-invalid="true" to each field that has an error, and remove it once the error is fixed. Many form plugins do this in their accessibility settings; if yours does not, ask its developer.

Example

<input id="email">
<span class="error">Enter your email address.</span>

<input id="email" aria-invalid="true" aria-describedby="email-error">
<span id="email-error" class="error">Enter your email address.</span>

How do I check the fix?

1. Run the page check again from Lumtera Pro's Page checks screen. The finding disappears once the page passes.
2. Submit the form with the required fields empty, using only the keyboard and then a screen reader: the errors should be announced, focus should move to them, and each message should say what to fix. Hover over and Tab to links and buttons to see that they stay readable, and compare the menus on a few pages.