Skip to main content
U.S. flag

An official website of the United States government

Dot gov

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.

Https

The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.

Latest release: Component Library: v56.3.0 released on Mar 30, 2026 | Guidance: Sprint 26 released on Apr 13, 2026 | Figma: Changelog

About

What's new?

The latest news and updates on the VA Design System.
Sprint 26
April 13, 2026

What’s Changed

Full Changelog: https://github.com/department-of-veterans-affairs/vets-design-system-documentation/compare/Sprint-25…Sprint-26

Sprint 25
March 30, 2026

What’s Changed

Full Changelog: https://github.com/department-of-veterans-affairs/vets-design-system-documentation/compare/Sprint-24…Sprint-25

Sprint 24
March 16, 2026

What’s Changed

New Contributors

Full Changelog: https://github.com/department-of-veterans-affairs/vets-design-system-documentation/compare/Sprint-23…Sprint-24

v56.3.0
March 30, 2026

What’s Changed

Component Summary API Change Rendered markup change
va-file-input, va-file-input-multiple Updates va-file-input and va-file-input-multiple to support the existing behavior for encrypted file passwords (event emission on change of nested va-text-input for password) and the new pattern that includes a submit button for the inputted password. By @RyanMunsch #2027 Yes Yes
Dependency update Bumps flatted from 3.3.3 to 3.4.1 in the npm_and_yarn group. By @dependabot #2033 No No
Component guidance tags Backfills guidanceHref on top-level web components and adds lint enforcement to prevent future omissions. By @humancompanion-usds #2036 No No
va-file-input-multiple Storybook Removes stringified passwordSubmissionSuccessList state value in the EncryptedTemplate from rendered output. I was using this value to debug template validation logic. By @RyanMunsch #2042 No Yes
va-telephone-input Updates the va-telephone-input component to be compatible with the form-system such that errors are properly set on the component. By @it-harrison #2028 No Yes
CSS-Library: mega-menu Changes mega-menu overflow from scroll to auto to remove unnecessary scrollbar behavior. By @powellkerry #2048 No Yes
va-date, va-file-input-multiple, va-file-input, va-memorable-date, va-telephone-input, va-text-input Makes changes to various interactive input components to normalize label bold styles based on the components’ error states. Labels should be bold when there is an error present. By @RyanMunsch #2041 No Yes
Revert - Stencil/puppeteer upgrade Reverts stencil and puppeteer upgrade due to runtime/modal issues, with follow-up tracked separately. By @powellkerry #2049 No No
va-on-this-page Update va-on-this-page to add a prop to exclude h2s that match heading selectors. Update utils to add a function to normalize string arrays so that the react binding is not necessary to use the prop. By @powellkerry #2043 Yes Yes

Full Changelog: https://github.com/department-of-veterans-affairs/component-library/compare/v56.2.1…v56.3.0

v56.2.1
March 19, 2026

What’s Changed

Component Summary API Change Rendered markup change
dashboard App columns are now sorted alphabetically so the CSV schema is identical every run, regardless of filesystem traversal order. Added a dedicated pattern for single-letter-suffix forms. By @humancompanion-usds #2035 No No
es-lint ESLint 9 config converted. For compatibility with ESLint 9, the config files were converted to ES module flat config format. By @jamigibbs #2039 No No
va-modal Patch for allowing string versions of “false” for the visible prop. By @powellkerry #2037 No No

Full Changelog: https://github.com/department-of-veterans-affairs/component-library/compare/v56.2.0…v56.2.1

v56.2.0
March 16, 2026

What’s Changed

New Features & Components 🎉

Component Summary API Change Rendered markup change
va-details Add new component. By @RyanMunsch #2015 Yes Yes
Architecture Upgrade Upgrades puppeteer@24.37.2 and stencil/core@4.43.2 By @powellkerry #2008 No No
Dependabot Upgrades Security upgrades. By @amyleadem & @powellkerry #2026, #2032 No No
va-file-upload The original content select was a va-select with an inert attribute. Updated to a dl. A screen reader should be able to read the content now. By @ediiotero #2020 No No
va-button Fixed the va-button when using it to submit a form. The onClick will now fire first before the onSubmit. By @ediiotero #2023 No No
CSS-Library - Mega Menu Updated mega-menu css-library styles to allow large font size users to be able to see all links and content in the va.gov navigation menus. By @powellkerry #2022 No No
va-on-this-page Filters out sr-only content and invisible elements from the generated link text. By @powellkerry #2022 No No

Full Changelog: https://github.com/department-of-veterans-affairs/component-library/compare/v56.1.0…v56.2.0

March 2026

Content style guide

Bulleted and numbered lists

Added guidance on what to consider when ordering bulleted lists:

Bulleted lists generally don’t need to be in a specific order. But in some cases, you may want to consider ordering the list based on the type of list items.

Grouping like items

Some lists may include sets of similar items. For example, a list of documents may include some documents related to education, some for personal information, and some for financial information. In this case, group each set of similar items together in the list.

Order of importance or level of urgency

In some lists, certain items may be more important or urgent than others. In this case, order the list with the most important or urgent item first. Consider a numbered list if appropriate for the content.

Numerical

In lists of dates, dollar values, percentages, or other numerical values, it may make sense to order the list from either high to low or low to high.

Alphabetical

Use alphabetical order for lists of certain items, like medications or specific locations, that don’t have another natural order. But don’t default to alphabetical order for all lists.

Punctuation and formatting

Added guidance on parentheses:

When to use parentheses

  • For short examples within a sentence
  • To set off brief additional information (an aside) that helps readers understand the sentence, the context, or a specific word or phrase
  • To introduce an acronym or abbreviation
  • To add a VA form number after the form title

When not to use parentheses

Consider making the parenthetical a separate sentence in these cases:

  • If the parenthetical is a full sentence on its own
  • If the parenthetical is long or makes the sentence harder to understand

Plurals

Don’t use “(s),” “(es),” or “(ies)” at the end of a word to show a possible plural. Screen readers don’t announce the parenthetical in a way that people can easily understand. Instead, use the plural version of the word. You can also reword the sentence to use “any” before the plural to mean 1 or multiple.

Payments and debts

Updated the definition for balance:

balance

Use “balance” when you refer to the total amount owed for copay bills or overpayment debt.

Like this: Pay your full balance or request help by the due date on your collection letter or billing statement.

Readability and usability of VA digital content

Added this new page to the style guide. This page explains our approach to ensuring digital content is easy to find, understand, and use. And it explains our approach to readability scores.

Sign in and identity verification

  • Added information on ID.me to the first Considerations bullet:

    ID.me provides more flexibility for identity verification for Veterans in certain situations, such as living outside the U.S.

  • Updated the identity verification and verify your identity definition to specify that ID.me and Login.gov are accounts. And added information to the note about using “confirm” or “confirmation” when asking someone to check information they provided on a form (like a mailing or email address).

Word list

Updated these entries:

  • verify and verification: Specified that ID.me and Login.gov are accounts
  • Veterans Service Organization (VSO): Fixed typo

Added these new entries:

balance

Use “balance” when you refer to the total amount owed for copay bills or overpayment debt.

Like this: Pay your full balance or request help by the due date on your collection letter or billing statement.

community care

Lowercase.

confirm or confirmation

Use “confirm” or “confirmation” when asking a person to check the information they provided on a form or application, like an email address or mailing address. Avoid using the terms “verify” or “verification” in this context. We only use the terms “verify” and “verification” to describe the initial, one-time process of verifying your identity with an ID.me or Login.gov account.

discharge status (character of discharge)

The discharge statuses are honorable, general, medical, other than honorable, bad conduct, dishonorable, officer, and entry-level separation. If you’re grouping multiple statuses together, list each status.

  • Like this: You may qualify for these benefits if you have an honorable, general, or medical discharge.
  • Like this: You may qualify for these benefits if you have an honorable, general, or medical discharge. If you have a different discharge type, you may still qualify for some benefits.
  • Like this: If you have an other than honorable or bad conduct discharge, you may still qualify for some benefits.

MOVE! Weight Management Program for Veterans

MOVE! is all capital letters, with an exclamation point at the end. There’s no space between the “E” and the exclamation point. MOVE! isn’t an acronym. After the first mention of the full formal program name, we can use “MOVE!” for all other mentions.

Components

Alert

  • Added guidance on slim alert length:

    Keep slim alerts to 100 characters (with spaces) when possible. If you have a slim alert that’s longer than 100 characters, contact the VA.gov content and IA team. The team will work with you to edit the alert or determine if we need to make an exception (up to 150 characters).

  • Made edits to the Content considerations to align with the style guide.

IA

VA website organization

This new section explains how and why we organize content on the main VA.gov website and key subdomains.

Edit this page in GitHub (Permissions required)
Last updated: Apr 21, 2026