GSA Issues Guidance on Clear Instructions and Error Messages for Accessible Digital Forms

The U.S. General Services Administration (GSA), via Section508.gov, released guidance on writing effective instructions and error messages to improve digital form accessibility.

Forms are routinely used across digital platforms for tasks such as event registration, service requests, searches, and application submissions. Clear instructions and error messages reduce user frustration and help users avoid mistakes when specific formats are required.

Providing Instructions in Advance

When a form field has specific formatting constraints or unusual requirements, guidance should be provided through form labels or instructions prior to data entry.

• Advance Clarification: Rather than providing a basic label such as "Date of birth," specify the expected format directly, for example: "Date of birth (MM/DD/YYYY)."
• Preventing Errors: Providing formatting criteria upfront prevents users from having to guess requirements before submitting.

Delivering Actionable Error Feedback

When errors occur, notifications should clearly explain the problem and provide concrete instructions for fixing it.

• Avoid Vague Notifications: Phrases like "Error," "Invalid entry," or "There was a problem with your submission" fail to explain how to resolve the problem.
• Provide Specific Corrections: Clear messages state the necessary resolution, such as "Enter the date using MM/DD/YYYY, for example, 08/10/2026," "Enter an email address in the format name@example.gov," or "Select at least one contact method before continuing."

Locating Errors and Color Independence

Systems must clearly show where an error happened so users can navigate to the affected field:

• Visual and Text Indicators: Do not rely solely on color, such as changing a field border to red, to indicate an invalid entry. Text must accompany the visual indicator so users do not depend on color perception or color contrast.
• Error Summaries: When multiple errors occur, an error summary can assist users in finding every issue.

Plain Language and System Terminology

Instructions and error messages must be written in plain language for the end user rather than reflecting underlying system diagnostics. Technical terms such as "Validation error: Required parameter missing" should be replaced with straightforward directions like "Enter your last name before continuing."

These practices assist all users, including individuals with cognitive disabilities, screen reader users, and people unfamiliar with the requested information.

Self-Review Checklist

The guidance suggests testing forms by intentionally entering incorrect data and reviewing against these criteria:

1. Are instructions presented before data entry?
2. Does the message explain what went wrong?
3. Does the message provide instructions on how to resolve the issue?
4. Can the field with the error be located easily?
5. Are errors communicated without relying solely on color?
6. Are all instructions and messages written in plain language?

Further information regarding form validation and error recovery is available through WebAIM: Usable and Accessible Form Validation and Error Recovery.