Which accessibility technique helps screen readers describe form errors to users?

• A. Include an aria-label on the input element
• B. Use an inline error message
• C. Hide errors from assistive technologies
• D. Use aria-describedby to reference the error message for the field

Answer: (D)

Describing form errors to screen readers hinges on linking the error text to the specific field so the reader can announce both the field and what is wrong. Using a descriptive reference with aria-describedby allows you to point the input to an element that contains the error message. When a user focuses or navigates to the field, the screen reader reads the input and then the additional description, delivering the exact error details inline with the field. This provides clear, contextual feedback that helps users understand and correct the issue.

Just adding an accessible label on the input doesn’t convey the error itself. An inline error message looks helpful visually, but without a proper association, screen readers may not automatically read that message in connection with the field. Hiding errors from assistive technologies eliminates the needed feedback altogether. Marking the field as invalid is useful, but it doesn’t supply the explicit description of what’s wrong unless it’s connected to an error message via aria-describedby.