Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Dev-ready Design] Explainer for "Closed Cases" for grantees familiar with "Negative Cases" #2131

Closed
10 tasks
reitermb opened this issue Sep 14, 2022 · 6 comments
Closed
10 tasks
Labels
Old Refined Ticket has been refined at the backlog refinement Research & Design

Comments

@reitermb
Copy link

Description:

Pilot research revisited the fact that many grantees use different/older terms for various elements of TANF data, in this case using "Negative" rather than "Closed" to refer to Section 2 data. This ticket delivers in-app and knowledge center enhancements to de-mystify the terminology difference for grantees. In-app changes should be achievable with minimal scope (i.e. around the level of adding text / knowledge center links to the data files page).

Related User Stories:

  • As a grantee user I want to understand what Closed Case data refers to

AC:

  • App explains terminology difference / directs users to the knowledge center
  • Knowledge center explains the terminology difference
  • Documentation work for the following has occurred:
    • Relevant User stories.
    • Recommended pa11y checks.
    • Updating living UX documents, e.g. User Flows or Personas(if relevant).
  • Dev/Design sync has occurred; resulting tickets created
  • The design is usable and accessible, meaning it adheres to definition of done standards for design work.
Expand Definition of Done Standards
  • It uses USWDS components and follows it’s UX guidance, or a deviation is clearly documented

  • Language is intentional and plain; placeholders are clearly documented

  • It follows accessibility guidelines and accessibility implementation notes are documented (e.g. clear information hierarchy, color is not the only way meaning is communicated, etc.)

  • If feedback identifies bigger questions or unknowns, create additional issues to investigate

Tasks:

  • Draft design in Figma
  • Draft hack.md with knowledge center changes

Supporting Documentation:

@stevenino stevenino added the Refined Ticket has been refined at the backlog refinement label Oct 25, 2022
@stevenino
Copy link

@reitermb to add additional details that were discussed as part of the ticket sync with Alex.

@lilybl1
Copy link

lilybl1 commented Oct 27, 2022

Note: Based on discussions with Alex's meeting with the Tribal team members, it was identified that due to the long tail of fTANF replacement may be 1 year or more, there needs to be some content about Closed = Negative. TBD on the design, but needs to be considered.

@ADPennington
Copy link
Collaborator

did we also discuss implementing for other terms like "stratum"? @reitermb @lilybl1

@ADPennington
Copy link
Collaborator

Collaborator

please disregard. i see this is captured in #2217

@robgendron
Copy link

@reitermb Is this related to Parity?

@robgendron robgendron added the Old label Apr 15, 2024
@reitermb
Copy link
Author

This may have been duped by knowledge center work that delivered these FAQ additions
Walking onto UX sync agenda to confirm
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Old Refined Ticket has been refined at the backlog refinement Research & Design
Projects
None yet
Development

No branches or pull requests

5 participants