Table of Contents:
We're continuing to learn about the content needs of the new TDRS. Future teams should plan to write in plain language and continually test site navigation and comprehension. Documentation in code docs should ensure that usage of TANF-related terms remains consistent with the definitions found in the Project Glossary.
Resources:
Everyone who works on government websites has a role to play in making federal resources accessible and inclusive. The new TDRS should meet 508 accessibility standards and use accessible design and development best practices.
Resources:
Information on existing ACF styles can be found in the ACF Digital Toolbox
We'll be using USWDS, a design system for the federal government, for the new TANF Data Portal (TDP). USWDS provides us with UX guidance and code for common UI components as well as guidance on how to comply with the 21st Century Integrated Digital Experiences Act (IDEA).
To improve our workflow in ideating and supporting development, we created a user flows page in Figma to map and explore user actions and outcomes in a modular environment that can be easily changed and extended.
This living document covers actions a user would take, system actions that happen on the backend, and destinations that are reached after actions are executed. To communicate how these actions and outcomes intertwine, we included primary and secondary paths that a user can take within the flow. These flows have also proven useful for certain security/compliance workflow documentation needs.
Full Site - A visual site map page encompassing all reviewed dev-ready mockups that responsible parties deliver.
Reviewed
- Upload and Download Data Reports associated with issues #427 and #415
- User Management (Admin tools) associated with issues #404, #327, and #164
- Reset Password associated with issue #318
- Concept Prototype (For round 3 research) associated with issues #275 and #115
- Responsive Mobile Designs (Admin pages) associated with issue #178
- Request Access (New user) associated with issue #166
In Backlog
- Ideas on Validation associated with issue #295