Skip to content

Defining and documenting the web product palette #134

@nicolebrennan

Description

@nicolebrennan

At a glance

As part of the design system, we are establishing a structured and accessible color palette to ensure consistency, usability, and compliance with WCAG accessibility standards across the web products. This color palette will be integrated into the design tokens and front end framework to maintain uniformity and UI components, typography, and interactive elements.

In order to ensure a consistent visual identity and enhance accessibility across our web product, we are standardizing our color palette with clearly defined design tokens and compliance to WCAG contrast guidelines.

Scenario:

Given that our web product must provide a uniform and accessible user interface
when a new UI component is developed or updated
then it should reference the standardized color tokens to ensure consistency and meet established accessibility standards,
...

### then...
- [ ] [a thing happens]
- [ ] https://github.com/GSA-TTS/jemison/issues/141
- [ ] https://github.com/GSA-TTS/jemison/issues/142
- [ ] Verify color contrast
- [ ] Document color usage guidelines, including use cases for each color
- [ ] Create a centralized reference (style guide/design system)

Shepherd

  • UX shepherd: Nicole Brennan
  • Design shepherd: Nicole Brennan
  • Engineering shepherd:

Background

Security Considerations

Required per CM-4.


Process checklist
  • Has a clear story statement
  • Can reasonably be done in a few days (otherwise, split this up!)
  • Shepherds have been identified
  • UX youexes all the things
  • Design designs all the things
  • Engineering engineers all the things
  • Meets acceptance criteria
  • Meets QASP conditions
  • Presented in a review
  • Includes screenshots or references to artifacts
  • Tagged with the sprint where it was finished
  • Archived

If there's UI...

  • Screen reader - Listen to the experience with a screen reader extension, ensure the information presented in order
  • Keyboard navigation - Run through acceptance criteria with keyboard tabs, ensure it works.
  • Text scaling - Adjust viewport to 1280 pixels wide and zoom to 200%, ensure everything renders as expected. Document 400% zoom issues with USWDS if appropriate.

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

Status

blocked

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions