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

USWDS-Site - Indent left navigation subfields #2730

Open
jaclinec opened this issue Jun 26, 2024 · 0 comments
Open

USWDS-Site - Indent left navigation subfields #2730

jaclinec opened this issue Jun 26, 2024 · 0 comments
Assignees
Labels
Good First Issue A good issue for those new to USWDS Role: Dev Development/engineering skills needed Severity: 4 Minor functionality, workaround available Usability Testing

Comments

@jaclinec
Copy link
Contributor

jaclinec commented Jun 26, 2024

During top tasks usability testing 🔒, a user commented that it is sometimes difficult to distinguish the hierarchy of items in the left navigation on our site since all the items seem to be at the 'same level' and suggested we indent the subfields.

For instance, our left navigation items are all in alignment, making it touch to know the 'level' of information:
image

We should consider indenting subfields. I believe this recommendation is also supported by the recent content audit. 🔒

Additional context

To give more context on how to prioritize the new issues and feature requests that came out of top task testing, here's the full list of issues divided into 3 buckets and in order of priority (though it is somewhat flexible):

Low lift recommendations:

  • Implement better synonym searching in the component search function. #2724
  • Make design kits stand out more on the page and consider offering access to the kits in more visible places on the site (such as the homepage). #2723
  • Provide a “Show all” link near the showcase list on the homepage that takes users to the entire list of sites that use USWDS. #2725
  • Change the names of the step indicator and in-page navigation components to better match user expectations. #2728
  • Link to form-related components (like step indicator) from the form component page (better cross-linking in general) #2729
  • Indent subgroups in the left navigation. #2730
  • Consider putting “References” at the very bottom of the component page (see data visualizations page). #2732
  • Make the language selector preview have dark text with white background. (need to discuss before creating issue)
  • Make the icons above the components, patterns, templates, etc. on the homepage clickable. #2734

Medium lift recommendations:

  • Offer component previews on the components page. #2736
  • Provide a glossary of definitions of heading labels (patterns, components etc.). (First we need to create a glossary component (see proposal discussion). Then we can address adding it to USWDS site.)
  • Provide more context around showcase sites that use USWDS. #2737

High lift recommendations:

  • Consider how we might reorganize the information architecture to better match users’ mental models of how information should be grouped and found. #2738
@jaclinec jaclinec added Needs: Discussion We need to discuss an approach to this issue Status: Triage We're triaging this issue and grooming if necessary Role: Content Content/writing skills needed Role: Dev Development/engineering skills needed Role: Visual Visual design skills needed Severity: 4 Minor functionality, workaround available labels Jun 26, 2024
@amyleadem amyleadem added Good First Issue A good issue for those new to USWDS and removed Status: Triage We're triaging this issue and grooming if necessary labels Jun 27, 2024
@amyleadem amyleadem removed Needs: Discussion We need to discuss an approach to this issue Role: Content Content/writing skills needed Role: Visual Visual design skills needed labels Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Good First Issue A good issue for those new to USWDS Role: Dev Development/engineering skills needed Severity: 4 Minor functionality, workaround available Usability Testing
Projects
Status: Ready to Schedule
Development

No branches or pull requests

4 participants