eAPD
eAPD copied to clipboard
Accessibility Research: How should the app behave when a new form is added
Research the accessibility of tabs and auto-focus in forms. Verify that inline validation errors are accessible to non-sighted users.
In many parts of our app, there is the option to add new form elements.
Example:
When clicking on add outcome, a new text area appears:
What should the app do from a:
- Screen reader perspective (should the app announce the new form?)
- Focus perspective (should the focus on the app move to the new text field (1) or stay on the outcomes section (2)?)
This task is done when...
- [ ] we understand the most accessible way to handle tabbing and auto-focus in our forms
- [ ] inline validation errors are accessible to non-sighted users
- From a screen reader perspective the app should announce when a new form is generated
- The focus on SHOULD move to the newly generated field as it was created by the user input.
Thanks @itsonlydio - we are going to reassign this to a dev for confirmation / review.