You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
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.
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:
AC:
Tasks:
Supporting Documentation:
The text was updated successfully, but these errors were encountered: