Bug Extravaganza

[kenieh]

An internal place for the design team to track bugs and areas of improvement as pre-emptive preparation for the upcoming Bug Hunt.

Action items

• [ ] Review this ticket and decide what needs to be turned into tickets.

• [ ] Heuristic evaluation of the product as a team

• [ ] Build a visual way to track, communicate, and socialize design debt (e.g. slide deck or Figma page)

  ---

  Bugs

  USWDS classes not properly applied in core app.

Design POC: @vz3

• [ ] Some USWDS classes not properly applied in the core app. For instance, on the (properly implemented landing pages), the <main> container has the usa-prose class applied, ensuring all content therein receives USWDS styling. In the core app, usa-prose seems to be applied inconsistently on various divs. This

  results in class bloat, code bloat, and inconsistent typography throughout the experience.

---

Areas of improvement

Application-wide

• [x] Extend the application's max viewpoint beyond 1024 px
• [x] Expose "search" outside of the "filter" button as a commonly used interaction that should not be hidden.
• [x] Make everything sentence case
• [x] Overall redesign/refactoring of filters

Static site [To be considered with future refactoring work]

• [ ] Add "On this page" section and anchor bullets when page has more than 2 H2s [Save for next round of Resources redesign work]
• [ ] Static sites uses Inter font, core app uses Public Sans. And the line between the two is being further blurred with log-in and sign-up. Should we use the same typeface throughout?
• [x] Make everything sentence case

Form - visual design [To be considered as part of future refactoring work.]

• [ ] Define spacing parameter
• [ ] Improve typography hierarchy, especially for headers
• [ ] Improve differentiation between different form sections

Error messaging - content design [Rebecca to continue meeting with Engineer. We're proposing to add content review and documentation in QA process / checklists.]

• [ ] Improve error messaging across the application, particularly the placeholder body text currently used "Please check for errors and try again".
• [ ] The error messaging could use an overall audit and be made more actionable and insightful for users. - According to Adam, the body text in error messages cannot be easily changed.

Emails

• [x] Make everything sentence case

Use case: Many facilities Use case of >~12 facilities [Leslie and Tim N to handle strategizing for this.]

• [ ] All facility selector interactions start to break down when user has many facilities.
• [ ] Facility page should be alphabetized.
• [ ] Front page facility selector should be a combo box or similar.
• [ ] Consider allowing user to set default facility to skip the selector on log-in. For users with many facilities, navigating through the list may be burdensome.

Facility selector on log-in Facility selector in core app

Use case: One facility, many people [Reconsider this use case in future refactoring work. See LFG for specific constraints around this.]

• [ ] LGF uncovered an org (Lamar County) with 500+ pages of people
• [x] Expose search field by default
• [x] Address first/last name search issue
• [ ] Identify ways to encourage users to make use of facility functionality (potentially related to dashboard concepts)

Use case: Need design work for a test-admin experience of setting up patient self-registration

• [ ] Need to put in thought on what this flow looks like for test admins—how are links shared (i.e. email or text)? what is all user-facing content in this process? how much customization do we enable users when creating and sharing the link?
• [x] How might we address new feature discovery in SR in general?

---

Open questions

• [ ] Content stuff to test

---

Future state product ideas

• [x] Super admin user dashboard—to view centralized source of SR data (e.g. test results, patient data, etc.) across multiple facilities rather than one facility at a time. User research: Lamar County Schools use case and need; [interview notes]

(https://docs.google.com/document/d/1K24kkc1AtMIaIdx784zxwiqGPtzHfCyxtRe83XAj7Go/edit?usp=sharing). Previous design work by Heather.

[kenieh]

FYI @Rebecca-LM I added a piece about improving error messages across the app under "Areas of Improvement"

[kenieh]

Design team has gone through these and added to our list of design debt/potential tickets to draft.