Request form: Required fields are marked as required

[AnnaGingle]

Issue description

As a user who relies on accessibility features,
I want all required fields in the request form to be clearly indicated as required,
so that I can accurately and efficiently complete the form without confusion or errors, in compliance with Section 508 accessibility guidelines.

Acceptance Criteria

• Review the request form audit created as a part of Request form: Accessibility audit #2866
• Update the Type of organization page design to ensure that all required fields are clearly marked as required.
• Update the Federal Government branch page design to ensure that all required fields are clearly marked as required.
• Update the Election office page design to ensure that all required fields are clearly marked as required.
• Update the Purpose of your domain page design to ensure that all required fields are clearly marked as required.
• Update the Other employees from your organization page design to ensure that all required fields are clearly marked as required.
• Update the Requirements for operating a .gov domain page design to ensure that all required fields are clearly marked as required.
• Update the .gov domain page design to ensure that all required fields are clearly marked as required.
• The updated designs pass the Trusted Tester success criteria for 5.B Descriptive Label
• Create a dev ticket to implement the changes.

Additional Context

The request form has a few required fields without indicators that they are required. This fails the 508 trusted tester success criteria label descriptive.

Gaby mentioned these fields were not marked as required intentionally because of USWDS guidance. Here it is:

Note: One-field forms are the exception and do not need to be marked with a required label or symbol.

This contradicts the section 508 guidelines but also does not apply to the request form because it has more than one field even though some pages only have one.

Required fields

• Type of organization page: What kind of U.S.-based government organization do you represent?
• Election office: Is your organization an election office?
• Federal government branch page: Which federal branch is your organization in?
  • Note: The g in .gov should be capitalized according to our content guide. Try to sneak in that update if you can.

References for creating a dev ticket with accessibility requirements in the A/C

• Request form: Current website screen reader output #2871
• Bundle: DS data accessibility tickets #2849

Issue Links

• Contains Domain request: .gov domain step form field needs visual indicator that field is required
• Relates to Request form labels communicate required data format Request form: labels communicate required data format #2699
• Relates to Make the "x" in search bars an accessible button #301
• The .gov domain page also needs a visual indicator but that will be addressed in Request form: labels communicate required data format #2699

Prioritization Comments

WCAG Conformance Level: 2.1 AA
WCAG Standard that applies:
2.4.6 - Headings and Labels (Critical)
3.3.2 - Labels or Instructions (Critical)
Critical Failure if Not Met?: Yes
Prioritization: High/Must Do
Reason: Clearly marking required fields is essential for ensuring an accessible and efficient user experience. Missing required indicators make it challenging for users, especially those with disabilities, to understand form expectations and complete the form accurately.

[AnnaGingle]

Duplicate of #2698. Closing

[AnnaGingle]

Just kidding! I thought I made a new ticket, but I actually updated the existing one 😎

[PaulKuykendall]

Moved from Parking Lot to Ready because it was in advertently closed earlier. This ticket is active and valid.