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.10.0 released on Aug 3, 2026 | Guidance: Sprint 4 released on Aug 4, 2026 | Figma: Changelog

About

What's new?

The latest news and updates on the VA Design System.
Sprint 4
August 4, 2026

What’s Changed

New Contributors

Full Changelog: https://va.ghe.com/software/vets-design-system-documentation/compare/Sprint-3…Sprint-4

 Sprint 3
July 13, 2026

What’s Changed

Full Changelog: https://va.ghe.com/software/vets-design-system-documentation/compare/Sprint-2…Sprint-3

 Sprint 2
June 29, 2026

What’s Changed

Full Changelog: https://va.ghe.com/software/vets-design-system-documentation/compare/Sprint-1…Sprint-2

 v56.10.0
August 3, 2026

What’s Changed

Tokens

  • Updated hard-coded values in web components to use recently added CSS-Library tokens by @Kerry-Powell in #2206

va-alert

  • Added non-breaking space so sr-text doesn’t run into alert headings by @Jeana-Clark in #2197

va-telephone

va-file-input

Font resize component

  • Fixed font resizing issues for va-additional-info, va-date, va-memorable-date, va-search-input, va-telephone-input, and va-text-input by @Amy-Leadem in #1800

va-file-input-multiple

va-tag-status

CSS-Library

dependency updates

 v56.9.0
July 20, 2026

What’s Changed

New Features & Components 🎉

Fixes

  • [Tokens] va-select, va-service-list, va-sidenav, va-sort, va-statement-of-truth, va-summary-box, va-table, va-tabs, va-tag-status, va-telephone, va-telephone-input, va-text-input, va-textarea : replace hard-coded values by @Kerry-Powell in #2191
  • [Tokens] globals and mixins: replace hard-coded css-values by @Kerry-Powell in #2193
  • Fix error state visual regression by @JAMI-GIBBS in #2200

Full Changelog: https://va.ghe.com/software/component-library/compare/v56.8.0…v56.9.0

 v56.8.0
July 14, 2026

What’s Changed

New Features & Components 🎉

  • va-header-minimal, va-icon, va-language-toggle, va-link, va-link-action, va-loading-indicator, va-maintenance-banner, va-memorable-date, va-minimal-footer, va-modal, va-need-help, va-notification
  • va-official-gov-banner, va-omb-info, va-on-this-page, va-pagination, va-privacy-agreement, va-process-list, va-progress-bar, va-promo-banner, va-radio, va-radio-option, va-search-filter, va-segmented-progress-bar

Fixes

Full Changelog: https://va.ghe.com/software/component-library/compare/v56.7.0…v56.8.0

August 2026

Content style guide

  • Revised consideration about putting links on their own line to add “generally”:

    We generally put links on their own line to help make the page easier to scan and the intention of the link as clear as possible. Too many embedded links can be distracting or overwhelming to people with traumatic brain injuries or other cognitive impairments.

  • Added information on how to structure link text for links that go to a site outside of VA.gov:

    If the link takes the reader outside of VA.gov, name the external website in the link text. Put the action first (“Learn more about vaccines”) then the destination (“on the CDC website”) to lead with the value to the Veteran. We prefer to include the location in the main link text instead of in parentheses, like “Learn more about vaccines on the CDC website” and not “Learn more about vaccines (CDC website).”

    Use a link label that tells the reader where the link takes them. We prefer including the location in the main link text instead of in parentheses since it’s clearer for screen readers and translated text. For example, “Play the YouTube video on creating an account” and not “Play the video on creating an account (YouTube).” But it’s okay to use parentheses if needed because of space constraints or to make the link text clearer.

  • Replaced “abilities” with “ways of interacting with the information”:

    Avoid using words that assume certain ways of interacting with the information, like “See,” “Hear,” and “Watch.”

  • Updated guidance on links opening in a new tab to align with previous guidance. Links should only open in a new tab if the person will lose progress or unsaved data, regardless of the link’s destination:

    Note: Links should open in the same tab, unless they meet the specific criteria for opening in a new tab. If a link needs to open in a new tab, add “(opens in a new tab)” to notify the person. Don’t use the new window icon unless there are space constraints.

    Review guidance on when to open links in a new tab in the Components section

  • Added information on anchor and jump links:

    We sometimes use an anchor or jump link when we need to link to a section within a VA.gov page. Anchor or jump links can be helpful in certain cases, like when we want to direct someone to a specific section on a long page. But if the heading of the section we’re linking to ever changes, the anchor or jump link won’t work and will redirect to the top of the page. Use anchor and jump links with caution.

  • Added information on how to structure link text for online forms:

    Link text for forms

    • Links to the form Detail page follow this format: Get VA Form XX-XXXX to download.
    • Links to the online tool should include a verb and the purpose of the form. For example: Apply for healthcare benefits.
      Note: If it will make the purpose of the link clearer, include “online” in the link text (“Apply for healthcare benefits online”). But if including “online” will be too repetitive or if a form only has an online version (no PDF option), you don’t need to include “online.”
  • Updated all mentions of “form’s About page” to “form Detail page”
  • Made edits throughout to align with the style guide

Components

  • Updated guidance on links opening in a new tab to align with previous guidance:

    • Open all links in the same tab, with one exception. Only open links in a new tab if selecting the link would cause the person to lose progress or unsaved data. In all other cases, links should open in the same tab.
    • Always notify the person when opening in a new tab. Add “(opens in a new tab)” text to the link and use the external link variation. Don’t use the new tab icon unless there are space constraints.
      Note: The external link variation applies to links that open in a new tab, not links that take people to a site outside of VA.gov.
    • Links to a non-VA.gov site must indicate where they go. Follow the methods detailed in linking to external sites.
    • Links that open in a new tab must indicate that. By default, the link component’s external link variation will add “(opens in a new tab)” to the link text instead of using an icon. This follows Techniques for WCAG 2.0 advice on providing people with both a spoken and visual warning that this link opens in a new tab.

  • Made edits throughout to align with the style guide
Edit this page in GitHub (Permissions required)
Last updated: Sep 03, 2026