Bug Report
Problematic behavior
Across multiple forms:
- Required fields are not indicated to users
- Error messages are not programmatically linked to their respective fields
- Some error messages lack actionable information (e.g. the email field on the import page does not show expected format on error)
Expected behavior/code
Required fields must be clearly indicated. Error messages must be linked to fields via aria-describedby and provide actionable guidance including examples.
Steps to Reproduce
- Submit the label name form with an empty required field — no indication that the field is required
- Trigger a validation error — error message is not announced by screen reader
- On the import page, enter an invalid email — error does not indicate expected format
Environment
- RGAA Criterion: 11.10
- Severity: 🟠 Major
Possible Solution
- Indicate required fields in
<label> text or via introductory text (e.g. "* Required fields")
- Link error messages to fields via
aria-describedby pointing to the error's id
- Import page email error → "Invalid email address. Example: j.doe@gmail.com"
Additional context/Screenshots
RGAA reference: Criterion 11.10
Bug Report
Problematic behavior
Across multiple forms:
Expected behavior/code
Required fields must be clearly indicated. Error messages must be linked to fields via
aria-describedbyand provide actionable guidance including examples.Steps to Reproduce
Environment
Possible Solution
<label>text or via introductory text (e.g. "* Required fields")aria-describedbypointing to the error'sidAdditional context/Screenshots
RGAA reference: Criterion 11.10