The app needs some error pages

[jadudm]

At a glance

In order to know that I've done something wrong
as a person using the app
I want an amazing error page.

Acceptance Criteria

We use DRY behavior-driven development wherever possible.

Scenario:

Given that we get an error from the server
when it has a number
...

then...

Preview Give feedback

1. A page showing the number should be presented
2. It should encourage the user to visit the ticketing system and report it

Shepherd

• Design shepherd:
• Engineering shepherd:

Background

We envisioned customized error pages for different kinds of errors (e.g. 401, 403, 404, 444.4, etc.).

For now, we will just have one. We'll ticket out improved pages after go-live.

Security Considerations

Required per CM-4.

There are no security concerns in presenting an error page. This will not present a dump of app state, but instead just say "This is a 404! Submit a ticket!" or thereabouts.

Sketch

We're thinking we'll try implementing A and then changing B.

Tasks

Preview Give feedback

1. [something we'll definitely have to do]

---

Process checklist

Sketch

• Design designs all the things
• Engineering engineers all the things

Definition of Done

Triage

If not likely to be important in the next quarter...

• Archived from the board

Otherwise...

• Has a clear story statement
• Design or Engineering accepts that it belongs in their respective backlog

Design Backlog

• Has clearly stated/testable acceptance criteria
• Meets the design Definition of Ready [citation needed]
• A design shepherd has been identified

Design In Progress

• Meets the design Definition of Done [citation needed]

Design Review Needed

• Necessary outside review/sign-off was provided

Design Done

• Presented in a sprint review
• Includes screenshots or references to artifacts

If no engineering is necessary

• Tagged with the sprint where it was finished
• Archived

Engineering Backlog

• Has clearly stated/testable acceptance criteria
• Has a sketch or list of tasks
• Can reasonably be done in a few days (otherwise, split this up!)

Engineering Available

• There's capacity in the In Progress column
• An engineering shepherd has been identified

Engineering In Progress

• Meets acceptance criteria
• Meets QASP conditions

If there's UI...

• Screen reader - Listen to the experience with a screen reader extension, ensure the information presented in order
• Keyboard navigation - Run through acceptance criteria with keyboard tabs, ensure it works.
• Text scaling - Adjust viewport to 1280 pixels wide and zoom to 200%, ensure everything renders as expected. Document 400% zoom issues with USWDS if appropriate.

Engineering Blocked

• Blocker removed/resolved

Engineering Review Needed

• Outside review/sign-off was provided

Engineering Done

• Presented in a sprint review
• Includes screenshots or references to artifacts
• Tagged with the sprint where it was finished
• Archived