As a user who relies on screen readers for navigation,
I want to interact with forms that clearly communicate input fields, required information, and error messages,
so that I can complete the form independently and accurately without confusion or frustration.
NOTE: It is expected that one dev will pick up and finish all the below tasks, listed in the AC. Those tickets will NOT be shown in the sprint. Ensure that you use the "Resolves" keyword in the PR with all the ticket numbers below, so that each of the tickets get closed when your PR merges.
Acceptance Criteria
Complete the following tickets and their A/C
[ ] Form fields, hint text, and error messages are remediated using accessibility best practices outlined in the W3 form tutorial.
[x] #2569
[x] #2752
[x] #2570
[x] #2568
[x] #2556
Additional Context
Note: Screen reader output does not need unit tests
Story
As a user who relies on screen readers for navigation, I want to interact with forms that clearly communicate input fields, required information, and error messages, so that I can complete the form independently and accurately without confusion or frustration.
NOTE: It is expected that one dev will pick up and finish all the below tasks, listed in the AC. Those tickets will NOT be shown in the sprint. Ensure that you use the "Resolves" keyword in the PR with all the ticket numbers below, so that each of the tickets get closed when your PR merges.
Acceptance Criteria
Complete the following tickets and their A/C
Additional Context
Note: Screen reader output does not need unit tests
Issue Links
No response