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: v55.0.0 released on Feb 17, 2026 | Guidance: Sprint 22 released on Feb 18, 2026 | Figma: Changelog

About

What's new?

The latest news and updates on the VA Design System.

Guidance Updates

Sprint 22
February 18, 2026

What’s Changed

New Contributors

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

 Sprint 21
February 2, 2026

What’s Changed

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

 Sprint 20
January 20, 2026

What’s Changed

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

VADS Component Library Releases

v55.0.0
February 17, 2026

What’s Changed

Breaking Changes

| Summary | API change | Rendered markup change | | :—- | :—- | :—- | | Updated css-library and web-components to use Sass modules.** This update replaces the deprecated @import statements  with @use, and uses Sass’ built in modules for math and functions. | No | No |

Full Changelog: https://github.com/department-of-veterans-affairs/component-library/compare/v54.7.0…v55.0.0

 v54.7.0
February 16, 2026

What’s Changed

⚠️ Potential impact to downstream applications and tests

This release includes updates to rendered component markup that may affect existing applications or test suites. Review the notes below for guidance on resolving test failures for affected components.

New Features & Components 🎉

| Component | Summary | API change | Rendered markup change | | :—- | :—- | :—- | :—- | | va-accordion | Changed the expand/collapse toggles to use va-button-icon. Replaced native button elements with the va-button-icon web component for the expand/collapse actions. If your code or tests rely on this element, update your selectors or assertions to match the updated component structure. By @powellkerry https://github.com/department-of-veterans-affairs/component-library/pull/1975 | No | Yes | | va-sidenav | Added props for customizing header and aria-label. Additional props added for experimenting with the va-sidenav web component as a stepper component. By @Dr-Pongo https://github.com/department-of-veterans-affairs/component-library/pull/1955 | Yes | No | | va-card-status| Made header props required. The web component requires the headerText, linkHref, and linkText before it will display. By @RyanMunsch https://github.com/department-of-veterans-affairs/component-library/pull/1990 | Yes | No | | va-sort | Added new web component. A new web component is available for triggering search result sorting. By @jamigibbs https://github.com/department-of-veterans-affairs/component-library/pull/1963 | N/A | N/A |

Fixes

| Component | Summary | API change | Rendered markup change | | :—- | :—- | :—- | :—- | | va-language-toggle | Updated aria-current to a valid value. Previously the aria-current value was using an invalid value of “language” but it will now use “true” instead. By @jamigibbs https://github.com/department-of-veterans-affairs/component-library/pull/1968 | No | No | | va-language-toggle | Added language context to aria-label. The aria-label will now provide the name of the language that was selected. By @jamigibbs https://github.com/department-of-veterans-affairs/component-library/pull/1967 | No | No | | va-radio-option| Override global styles affecting display. The web component was receiving unwanted global styles from the CSS-Library because the shadow DOM of this component is open. By @jamigibbs https://github.com/department-of-veterans-affairs/component-library/pull/1987 | No | No |

CSS-Library

| Summary | | :—- | | Updated non-breaking space unicode value to full 4-digits. This update hopes to remediate a seemingly random issue where Sass compiles content: \a0 to actual UTF-8 bytes 0xC2 0xA0 in the CSS output. By @jamigibbs https://github.com/department-of-veterans-affairs/component-library/pull/1989 |

Dependency updates

Affected package Dependency name Before After
core webpack 5.94.0 5.104.1

By @powellkerry #1979

Full Changelog: https://github.com/department-of-veterans-affairs/component-library/compare/v54.6.2…v54.7.0

 v54.6.2
February 9, 2026

What’s Changed

Fixes

| Component | Summary | API change | Rendered markup change | | :—- | :—- | :—- | :—- | | va-file-input-multiple, va-modal | Fixed a bug in iOS VoiceOver that prevented some modal implementations from being accessible via touch gestures. Now, the component traverses both the light and shadow DOM to appropriately apply aria-hidden. By @amyleadem #1977 | No | No |

Full Changelog: https://github.com/department-of-veterans-affairs/component-library/compare/v54.6.1…v54.6.2

Figma Component Library Changelog

Content Style Guide Updates

January 2026

Content style guide

We, us, you

Removed this section. The guidance is available in the Use conversational language section.

They, their

Removed this section. The guidance is available in the Neutral language section.

Sign in and identity verification

  • Changed the order of accounts in the text so ID.me comes before Login.gov.
  • Removed the guidance to emphasize using Login.gov.
  • Revised the guidance explaining that ID.me and Login.gov are accounts and not separate tools:

    Research has shown that some people confuse Login.gov with being a separate tool, and some people think they need to go to the ID.me or Login.gov websites to sign in rather than VA.gov. So, we reinforce that ID.me and Login.gov are types of sign-in accounts—not separate tools or websites—by using the phrase “ID.me account” or “Login.gov account.”

  • Added guidance on the term “DS Logon”:

    VA no longer offers the ability to sign in with a DS Logon username and password. Use this term only in reference to this option going away or the ability to use this option for Defense Department (DOD) websites.

  • Added guidance on using the “MFA” acronym: Introduce “MFA” on the first mention and use “MFA” on any subsequent mentions on the same page.
  • Updated the “My HealtheVet” guidance:

    With rare temporary exceptions, VA no longer offers the My HealtheVet user ID and password option for sign in. Today, My HealtheVet on VA.gov refers instead only to the health portal on VA.gov. When using this term to refer to the portal, “My HealtheVet” is 2 words. Don’t italicize the “e” between “Health” and “Vet” in digital content body copy, headlines, or user interface elements such as links, buttons, and navigation. The “e” is italicized only in the logo and in print materials.<p> Note: We no longer tell Veterans to create new My HealtheVet accounts or upgrade existing accounts. We don’t use the terms “My HealtheVet basic,” “My HealtheVet advanced,” or “My HealtheVet Premium.” Don’t refer to the sign-in account Veterans use to access their health portal as a My HealtheVet account. Instead, refer to the type of sign-in account (ID.me or Login.gov) or simply “your sign-in account.”

  • Added “My HealtheVet account” to the retired terms and updated the guidance:

    With rare temporary exceptions, VA no longer offers this sign-in option. Don’t refer to the sign-in account Veterans use to access their health portal as a My HealtheVet account. Instead, refer to the type of sign-in account (ID.me or Login.gov) or simply “your sign-in account.”

  • Updated the Considerations section to make guidance clearer:

    • We use links to connect Veterans and other visitors with related information that may be helpful to them.
    • We 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.
    • We tell people where links are taking them and why. External links can be disorienting for all people, but especially people who use screen readers.

  • Updated guidance in the Link text section to make guidance clearer:

    • Describe the purpose of the linked page
    • If the link takes the reader outside of VA.gov, name the external website in the link text
    • Balance link text length to provide the needed descriptions without having the relevant words get lost in the length
    • Use “Select” instead of “Click here,” since not all people are physically clicking links

  • Added a new section on linking to forms: linking to the form’s About page instead of the PDF (applies to all content other than the form’s About page), linking directly to the form’s PDF on the About page, and added exceptions for links to the direct download to the PDF version:

    • For forms that aren’t part of the VA forms database, you may need to use a direct download link to the PDF version of the form. This is a rare situation. Contact the centralized content and information architecture (IA) team for guidance.
    • You may also need a direct download link if the person filling out the form is downloading and generating their own completed copy. Contact the centralized content and IA team for guidance.

  • Added new guidance in the Linking to documents and other file sources section:

    • If a link opens a calendar, YouTube video, XLS, or other file format, add the relevant icon from the Components section in the Design System. This does not apply to pages housed within Drupal.
    • Include the file format (ex. PDF, HTML, or XML) in the link label. Place the file format at the end of the link label in parentheses. For example, “Download the Continuity of Care document (PDF).”
    • If you have a list of links to the same document with different file formats, consider rewording the link text to include the file format earlier. Contact the centralized content and IA team for help with your link text.

  • Added guidance on not linking to the Code of Federal Regulations on VA.gov pages.
  • Added a new section on Links in lists that includes general guidance and 3 options for adding links to lists.

Bulleted and numbered lists

Updated the Links in lists section to include 3 options for adding links to lists

Word list

  • Updated entries:

    apply: updated the examples
    delete: clarified this is specifically for file uploads
    educational and career counseling: removed note on style differences on Education and Career Counseling pages
    educational counseling: removed note on style differences on Education and Career Counseling pages
    Montgomery GI Bill Active Duty (MGIB-AD): added information on using the acronym and “Chapter 30”
    Montgomery GI Bill Selected Reserve (MGIB-SR): added information on using the acronym and “Chapter 1606”
    My HealtheVet: added that this is 2 words
    upload: clarified this is specifically for file uploads
    Veteran Readiness and Employment (VR&E): added information on using the acronym and “Chapter 31”; added information about the previous names for the program

  • Added new entries:

    approved program
    copay (or copayment, or health care copay)
    copay bill (or patient statement, or billing statement)
    cover the costs/cover expenses
    debt
    dependent child
    education benefit
    eligible
    entitlement
    get paid back
    Montgomery GI Bill
    national tests
    non-qualifying period of service
    overpayment or overpayment debt
    Personalized Career Planning and Guidance (PCPG)
    Post-9/11 GI Bill (PGIB)
    preparatory courses or prep courses
    Primary Family Caregiver
    qualify
    relinquish your benefits
    Secondary Family Caregiver
    spouse
    Statement of Service
    verify and verification
    VET TEC 2.0
    waiver (debt forgiveness)

Edit this page in GitHub (Permissions required)
Last updated: Feb 03, 2026