Request form: Senior official fields need helper text to communicated required data formats

[AnnaGingle]

Story

Email * field does not communicate expected data formats. An error is not sufficient to meet Section 508 standards.

Email * error state does not include the error message in the screen reader/ ANDI output:

Acceptance Criteria

• Email * error state for an empty field should have this screen reader output: Who is the senior official for your organization? Email * invalid entry, Enter an email address in the required format, like [email protected], required.

Additional Context

The code label or screen reader output should be:
<legend> Who is the senior official for your organization?
<label> Email *
required: required

In an error state this should be:
<legend> Who is the senior official for your organization?
<label> Email *
required Enter an email address in the required format, like [email protected].

Issue Links

Relates to Request form labels communicate required data format #2699

Prioritization Comments

WCAG Conformance Level: 2.1 AA
WCAG Standard that applies:
3.3.2 - Labels or Instructions (Critical)
3.3.3 - Error Suggestion (Critical, partially supports)
Critical Failure if Not Met?: Not in this case, see below
Prioritization: High/Must Do
Reason: This issue addresses essential guidance on input formats that is necessary for users to enter accurate data without confusion. Currently, users who rely on form hints, especially those with screen readers or cognitive disabilities, may struggle with incorrect input if the expected format is only communicated after an error. Providing clear, descriptive labels and hints directly on the form fields significantly improves usability and aligns with Section 508 and WCAG standards. Given that this issue does not entirely prevent form submission but still impacts usability and compliance, it is rated as High / Must Do.

[AnnaGingle]

This issue will be completed as a part of issue #2848