Bundle: Request form: Screen reader output

[AnnaGingle]

Story

As an assistive technology enabled uder, I want the screen reader output on the "Other employees from your organization" and "Add'l details" sections of the domain request form to be properly formatted and accessible, so that I can navigate and complete the form efficiently and without confusion.

Acceptance Criteria

• Purpose of your request domain screen reader output #2914
• Other employees from your organization radio screen reader output #2915
• Other employees from your organization text area radio output #2918
• On the Other employees from your organization page, move the Required fields are marked with an asterisk (*). below We typically don’t reach out to these employees, but if contact is necessary, our practice is to coordinate with you first.
• Add'l details screen reader output Are you working with a CISA regional representative on your domain request? #2921
• Add'l details screen reader output Is there anything else you’d like us to know about your domain request? #2922
• Add'l details screen reader output screen reader output text area #2923

Additional Context

Reminder: no unit tests are required for screen reader output
How to view screen reader output using ANDI

• Download ANDI
• Open ANDI
• Navigate to focusable elements
• Use the ⏪ ⏩ buttons to navigate through the page or hover over the element you want to inspect
• Use this handy ANDI key to understand how the ANDI output colors map to code attributes and <elements>.

NOTE: No unit tests are required for screen reader output.

Issue Links

• Caused by Request form: Accessibility audit #2866
• Relates to Request form: Screen reader output pt 2 #2924

Prioritization Comments

WCAG Conformance Level: 2.1 AA
WCAG Standard that applies:
1.3.1 - Info and Relationships (Critical)
3.3.2 - Labels or Instructions (Critical)
4.1.2 - Name, Role, Value (Critical)
Critical Failure if Not Met?: Yes
Prioritization: Blocker
Reason: This story addresses critical accessibility issues that affect users relying on assistive technologies. In this context, the reader output is not properly formatted and does not provide effective form navigation and completion. Mis-formatted outputs can lead to confusion, resulting in a negative user experience and potential failure to submit necessary information.

[AnnaGingle]

@abroddrick has reviewed and approved this ticket.