Discovery: Adding a monospace font to VADS

[babsdenney]

Description

The USWDS table requires numerical data use a monospace font. We currently don't have a monospace font in the Design System and will need to do research to figure out how we want to add a monospace font to the DS.

USWDS Table guidance

Use a monospace font for numerical data. For even better readability of dense, numerical data, consider formatting numbers that convey amounts, such as percentages, currency, or tallies, in a monospace font. (There’s no need to apply monospace formatting or alignment to phone numbers, zip codes, dates, or other number content that can’t be totaled.)

There are also other factors in play. There are discussions to reducing fonts from the VADS. We need to answer all the different questions about adding the font to the VADS.

Some questions to address

• [ ] Do we need to add a monospace font?
• [ ] What font should we add?
• [ ] What components can use the monospace font (aside from the table)?
• [ ] What documentation would need to be updated on VADS?
• [ ] What would we need to change in the component library/Example library to update all the monospace options?
• [ ] Any other issues you discover while researching this topic

Details

Slack thread for more context Design ticket - #2847

Tasks

• [ ] Research what monospace font to add to the DS
• [ ] Address all questions above and any other discoveries during the process
• [ ] Update this ticket (#2847) with the new findings and work that should be done

Acceptance Criteria

• [ ] Review your findings with Designers, PO, Accessibility, and Development

[caw310]

Hey team! Please add your planning poker estimate with Zenhub @babsdenney @danbrady @LWWright7