OKR 1.6: Error messaging and pages

[srtalbot]

OKR 1.6: Exceed WCAG criteria 3.3.3 “Error Suggestion” by providing more specific information to end-users on how to fix their mistake for common short answer questions.

Types of elements:

1. We know how to set an effective error message (E.x.: email, we have a specific component and can set a valid format easily)
2. We have some information on how to set an effective error message (e.g.: date - we have some specific options in the data component that can tell us more information on what is an expected valid input)
3. We have no information about how to set an effective error message

Context:

• Which error messages are server-side vs client-side validated?
• For type 1 & 2 we can do the work for them
• For type 3: HMW help clients set custom validation

Goals:

1. Review types 1 and 2 to see what work we can do to improve the error messaging for clients now
2. Ideation on how we support clients in creating more custom validation, where and when it will/won't apply.
3. Identify an interative approach to improving error messaging
4. Designs that are ready for dev implementation to be prioritized.

[anikbrazeau]

Past context:

• AODA Audit
• Client support ticket - Heritage
• Required fields left empty #449 #3950
• Site not operational #402
• Address validation #313
• Deleted form #4129
• Form no longer available #2169
• Bilingual errors #1723
• 500 Error #2159
• File upload error #4362
• Conditional logic #3888
• Sharing a form errors #3916
• Address complete #4314
• Error message to match GCDS #4390
• Error summary to match GCDS #4310
• Client's form submission not received through email #2279
• Phone number component #439
• Error language #3881

Current context

Follow Design System specifications and advice

• GCDS Error summary
  • Create usable error summaries
  • Use error summary with your own component instances
• GCDS Error message
  • Identify and define the error
  • Get the person back on track with a call to action
  • Write a message that's scannable
  • Use a human tone
  • Use error messages to support accessible task success
  • Follow a predictable format for error messages

[anikbrazeau]

Outlining error content here: https://docs.google.com/spreadsheets/d/1qx6K-PkburkQ2anDbRAhLpgWIfbYF8aWV6N34NrFUp8/edit?gid=0#gid=0

[anikbrazeau]

Note: some issues for multiple errors repeating can be mitigated by using pagination and one question per page to avoid summaries with many non-specific error messages.