Skip to content

Design: Fix Accessibility for Number of Days Deleted for Highlighted and Unhighlighted Rows #3388

Description

@Rabia2219

Overview

We need to update the text spacing and text color for deleted TDM Plans "(X days)" so that the highlighting of rows doesn't cause it to fail accessibility standards.

Details

Image Image

Text should have a space between Draft and the '('
Draft (70 days)

Text for number of days deleted probably does not pass contrast ratio when the row is highlighted.
Text might be #808080. It's currently in the code as "color: gray".

Image

The highlighting color comes from theme.js: colorRowHighlight #B2C0D3.

Accessibility Assesment

  • Contrast Ratio: 2.6:1
  • WCAG AA Minimum (Regular Text): 4.5:1 (Fails)
  • WCAG AA Minimum (Large Text): 3:1 (Fails)

In the Calculator, see page 4, the dropdowns use a different highlighting color (from theme.js colors.secondary.lightGray: #EEF1F4), which may or may not be influenced by which browser you use.
Image

Action Items

  • Assign yourself to this issue.
  • Move the issue from Prioritized Backlog to In Progress.
  • In Figma, move a blank page to the Design section.
  • Change the Figma page's title to have the format "#Issue Number | Title | Assignee Name".
  • Copy contents from the Figma Template page to this issue's Figma page.
  • Include a link to this issue's Figma page in the Figma section below.
  • Use the Figma page to design solutions for this issue.
  • Once this issue is ready to be reviewed:
    • Add a comment tagging the team design lead that explains the design.
    • Move it to the Visual Review column.
    • Add the "ready for Design lead-[team]" label specific to your team.
    • Once you have received feedback from the team lead, implement feedback as necessary.
  • Use presentation structure to review proposed designs with the design director. Implement feedback as necessary.
  • Use presentation structure to review proposed designs with the product, development, and research teams. Implement feedback as necessary.
  • Create a new slide (or edit one if it already exists) in staging and add images and appropriate text
  • Receive design approval from stakeholders. Implement feedback as necessary.
  • Add any annotations to the Figma design that would help the developer with implementation.
  • Create a Ready for Dev section around the final designs on the Figma page.
  • Update the Figma Design System with changes resulting from the issue's final design, if applicable.
  • Update the Style Guide Presentation, if applicable.
  • Add a comment to the issue that references the final design and adds any annotations that would help the developer with implementation.
  • Create a development handoff issue that references the comment.
  • Move the Figma page to the Development section of the Figma file.
  • Add the development issue's number in parentheses at the beginning of the title of the Figma page.
  • Include the development handoff issue number in the GitHub section below.
  • Reassign any previous assignees to this issue.
  • Close this issue.

Resources

GitHub

Figma

Dev Site

Staging and Release decks

  • Staging Deck
    • [Staging slide, ISSUE NUMBER]
  • Release Deck
    • [2025-MM-DD Release deck, slide ISSUE NUMBER]

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    New Issue Approval

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions