2914: Change screenreaderoutput of domain request purpose form [ES]

[erinysong]

Ticket

Resolves #2914

Changes

• Change screenreader text on Domain request's Purpose of your domain page. Text field's screenreader output now updated to requested content (question, subquestion, and character limit)

Context for reviewers

Part of #2913

Setup

1. Go to any domain request and navigate to the Purpose of your domain page.
2. Run ANDI and focus on the the text input field. The screenreader output should match the requested AC content.

Code Review Verification Steps

As the original developer, I have

Satisfied acceptance criteria and met development standards

• Met the acceptance criteria, or will meet them in a subsequent PR
• Created/modified automated tests - NA
• Update documentation in READMEs and/or onboarding guide - NA

Ensured code standards are met (Original Developer)

• If any updated dependencies on Pipfile, also update dependencies in requirements.txt. - NA
• Interactions with external systems are wrapped in try/except - NA
• Error handling exists for unusual or missing values - NA

Validated user-facing changes (if applicable)

• Tag @dotgov-designers in this PR's Reviewers for design review. If code is not user-facing, delete design reviewer checklist
• Verify new pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing - NA
• Checked keyboard navigability
• Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)

As a code reviewer, I have

Reviewed, tested, and left feedback about the changes

• Pulled this branch locally and tested it
• Verified code meets all checks above. Address any checks that are not satisfied
• Reviewed this code and left comments. Indicate if comments must be addressed before code is merged
• Checked that all code is adequately covered by tests
• Verify migrations are valid and do not conflict with existing migrations

Validated user-facing changes as a developer

Note: Multiple code reviewers can share the checklists above, a second reviewer should not make a duplicate checklist. All checks should be checked before approving, even those labeled N/A.

• New pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing
• Checked keyboard navigability
• Meets all designs and user flows provided by design/product
• Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)
• (Rarely needed) Tested as both an analyst and applicant user

As a designer reviewer, I have

Verified that the changes match the design intention

• Checked that the design translated visually
• Checked behavior. Comment any found issues or broken flows.
• Checked different states (empty, one, some, error)
• Checked for landmarks, page heading structure, and links

Validated user-facing changes as a designer

• Checked keyboard navigability
• Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)
• Tested with multiple browsers (check off which ones were used)
  • Chrome
  • Microsoft Edge
  • FireFox
  • Safari
• (Rarely needed) Tested as both an analyst and applicant user

References

• Code review best practices

Screenshots

[github-actions]

🥳 Successfully deployed to developer sandbox es.

[github-actions]

🥳 Successfully deployed to developer sandbox es.

[github-actions]

🥳 Successfully deployed to developer sandbox es.

[github-actions]

🥳 Successfully deployed to developer sandbox es.

[github-actions]

🥳 Successfully deployed to developer sandbox es.

[github-actions]

🥳 Successfully deployed to developer sandbox es.

[github-actions]

🥳 Successfully deployed to developer sandbox es.