About
What's new?
What’s Changed
- 📊 Update pattern adherence data - 2026-10-19 by @Amy-Leadem in #7237
- chore: update releases for 2026-10-19 by @Amy-Leadem in #7238
- Upgrade component-library to 56.19.0 by @Kerry-Powell in #7244
- Adds styling guidance for headings in screenshot-to-html skill to be not programmatic by @Derek-Wang in #7040
- Tag - Status: Adds draft as a neutral status use by @Barbara-Denney in #7248
- Add va-action-list accessibility test list by @Amy-Leadem in #6880
- Metrics tests: Fixes silent pass on empty chart check by @Matthew-Dingee in #7253
- Update css-library and web-components packages for component-library v56.20.0 release by @Ryan-Munsch in #7260
- Authenticated home page: Clarifies zero counts in Updates by @Matthew-Dingee in #7295
- 📊 Update metrics dashboard data - 2026-10-23 by @Amy-Leadem in #7269
- 📊 Update pattern adherence data - 2026-10-26 by @Amy-Leadem in #7284
- Update component-library packages for latest release by @JAMI-GIBBS in #7296
- Skills: Adds design-staging-review skill for Collaboration Cycle Staging Reviews by @Matthew-Dingee in #7262
- Bump nanoid from 3.3.17 to 3.3.20 by @dependabot[bot] in #7298
- Staging review skill: Adds shareable HTML findings export by @Matthew-Dingee in #7304
- Doc-queue and guidance-grooming skills: Updates for va.ghe.com and the current epic by @Matthew-Dingee in #7311
- Action required window: Adds missing profile information exception by @Matthew-Dingee in #7326
- [DONT MERGE TILL AFTER MIGRATION] Figma: Updates links to Figma for Government (figma-gov.com) by @Barbara-Denney in #7251
- Doc skills: Treats the groomed label as already groomed by @Matthew-Dingee in #7329
- Category pages: Adds partial-load, empty-state, and heading icon guidance by @Matthew-Dingee in #7331
- Action List: Updates Figma link to figma-gov.com by @Derek-Wang in #7342
- va-action-list: Document “Show more” toggle by @Jeana-Clark in #7339
- Metrics: Adds focused hardcoded typography report by @Matthew-Dingee in #7132
- Guidance skills: Adds content style guide review step by @Matthew-Dingee in #7359
- Docs: Fixes broken internal links by @Matthew-Dingee in #7358
- Process List: Adds design decision and guidance for error and action-needed states by @Matthew-Dingee in #7328
- Update site for Public Sans by @JAMI-GIBBS in #7309
Full Changelog: https://va.ghe.com/software/vets-design-system-documentation/compare/2026-10-19…2026-10-30
What’s Changed
- chore: update releases for 2026-10-06 by @Amy-Leadem in #7167
- Updates form step screenshots by @Jeana-Clark in #7169
- Update component-library to latest - v56.16.2 by @JAMI-GIBBS in #7174
- Bump component-library package for component-library v56.17.0 release by @Ryan-Munsch in #7198
- Metrics tests: Removes hardcoded counts and runs suites in CI by @Matthew-Dingee in #7188
- 📊 Update metrics dashboard data - 2026-10-09 by @Amy-Leadem in #7190
- 📊 Update pattern adherence data - 2026-10-12 by @Amy-Leadem in #7193
- Update component-library packages for latest release: v56.18.0 by @JAMI-GIBBS in #7200
- Create september-2026.md: Added Sept 2026 changes by @Lauren-Vocke in #7204
- Metrics: Runs the imposter component scan in the weekly workflow by @Matthew-Dingee in #7118
- Dates: Add timestamp display guidance as reusable partial by @Barbara-Denney in #6559
- HTML examples: Standardizes screenshot-to-HTML mockups by @Barbara-Denney in #7186
- 📊 Update metrics dashboard data - 2026-10-16 by @Amy-Leadem in #7233
Full Changelog: https://va.ghe.com/software/vets-design-system-documentation/compare/2026-10-06…2026-10-19
What’s Changed
- chore: update releases for 2026-09-17 by @Amy-Leadem in #7061
- Tag & Tag - Status: Adds BIG variant guidance by @Barbara-Denney in #7028
- Naming conventions: Adds component naming rubric by @Matthew-Dingee in #7039
- form-watch: stop crashing on bare numeric watchlist ids by @Dominic-Padula in #6938
- Addresses: Clarifies review-page mismatch guidance by @Barbara-Denney in #7055
- 📊 Update metrics dashboard data - 2026-09-18 by @Amy-Leadem in #7069
- Upgrade component-library@56.15.0, css-library@0.36.0 by @Kerry-Powell in #7080
- 📊 Update pattern adherence data - 2026-09-21 by @Amy-Leadem in #7074
- Second signer pattern: Adds Figma link by @Barbara-Denney in #7077
- va-tag-status: Revise dynamic content accessibility guidance by @Jeana-Clark in #7071
- va-action-list: Initial draft of guidance based on SDD Requirement doc by @Jeana-Clark in #7062
- Templates: Adds authenticated home page and category page templates by @Matthew-Dingee in #6973
- Updates Tabs Examples to be HTML instead of screenshots by @Derek-Wang in #6978
- Know when information is prefilled: Converts screenshots to HTML by @Barbara-Denney in #7043
- Mobile Storybook: Fixes broken links after org migration by @Barbara-Denney in #7089
- Navigate a long list: Converts provider screenshot to HTML by @Barbara-Denney in #7046
- Adds a11y tests for va-tag-status by @Jeana-Clark in #7101
- Navigate multiple related forms: Converts screenshots to HTML by @Barbara-Denney in #7047
- 📊 Update metrics dashboard data - 2026-09-25 by @Amy-Leadem in #7103
- Category pages: Revises guidance from designer review and adopts the Action List heading API by @Matthew-Dingee in #7109
- 📊 Update pattern adherence data - 2026-09-28 by @Amy-Leadem in #7110
- Adds ADR addressing color contrast in va-button-segmented by @Jeana-Clark in #7099
- Multiple responses: Replaces screenshots with HTML examples by @Barbara-Denney in #7049
- Action list documentation v2 by @Jeana-Clark in #7106
- Metrics: Replaces imposter component count with reachable, team-attributed scan by @Matthew-Dingee in #7115
- Upgrade component-library@56.16.0, css-library@0.36.1 by @Kerry-Powell in #7124
- Card: Adds guidance for Link - Action versus Link - Active by @Barbara-Denney in #7121
- Category pages: Resolves Auth Exp review of the authenticated experience docs by @Matthew-Dingee in #7122
- Bump brace-expansion from 1.1.18 to 1.1.21 by @dependabot[bot] in #7130
- 📊 Update metrics dashboard data - 2026-10-02 by @Amy-Leadem in #7153
- Category pages: Requires a status on rows that have one by @Matthew-Dingee in #7148
- Payments: Updates Treasury overpayments, Quick access, and travel pay titles by @Matthew-Dingee in #7154
- Update css-library and web-components packages for component-library v56.16.1 release by @Ryan-Munsch in #7162
- Bump source-map-js from 1.2.1 to 1.2.2 by @dependabot[bot] in #7166
- 📊 Update pattern adherence data - 2026-10-05 by @Amy-Leadem in #7155
Full Changelog: https://va.ghe.com/software/vets-design-system-documentation/compare/2026-09-17…2026-10-06
What’s Changed
New Features & Components 🎉
- Update web-components and CSS-Library to use Public Sans by @JAMI-GIBBS in #2429
Full Changelog: https://va.ghe.com/software/component-library/compare/v56.23.0…v56.24.0
What’s Changed
New Features & Components 🎉
- Revert “Main: Update web-components and CSS-Library to use Public San… by @JAMI-GIBBS in #2427
- va-header-navigation: add menuItemFilter to hide Profile and My VA links by @Dominic-Padula in #2409
Fixes
- va-header-navigation: render the hub rail as an unordered list by @JAMI-GIBBS in #2414
- va-header-navigation: Align caret color and header sizes across dropdowns by @Amy-Leadem in #2428
Full Changelog: https://va.ghe.com/software/component-library/compare/v56.22.0…v56.23.0
What’s Changed
New Features & Components 🎉
- Update web-components and CSS-Library to use Public Sans by @JAMI-GIBBS in #2273
Fixes
- va-memorable-date: refactor to share code by @Robert-Hasselle in #2416
Full Changelog: https://va.ghe.com/software/component-library/compare/v56.21.0…v56.22.0
September 2026
Content style guide
Page titles and section titles
-
Added guidance on using unique section titles:
Make each section title unique. Each title should be different enough so people can quickly and easily tell the difference between the sections. This is particularly important for pages that include an On This Page component (table of contents).
- Moved section title bullet items on length and punctuation to a separate subsection, Length and punctuation (no changes to guidance)
- Made edits throughout to align with the style guide
Plain language - Don’t use idioms
-
Updated introduction to include euphemisms and colloquialisms and added a second sentence about using clear and direct language:
Idioms, euphemisms, and colloquialisms can be confusing, especially for someone whose first language isn’t English. Instead, use clear and direct language.
-
Added 2 new examples:
Like this
If you’re the surviving spouse, child, or parent of a Veteran whodiedfrom a service-related injury or illness, you may be eligible for VA Dependency and Indemnity Compensation (D.I.C.).Not this
If you’re the surviving spouse, child, or parent of a Veteran whopassed awayfrom a service-related injury or illness, you may be eligible for VA Dependency and Indemnity Compensation (D.I.C.).Like this
Am I eligible for a Survivors Pension as the child of adeceasedwartime Veteran?Not this
Am I eligible for a Survivors Pension as the child of alatewartime Veteran?
Readability and usability of VA digital content
Added new guidance on content in PDFs on VA.gov, including information on official VA forms, outreach materials, tool user guides, and benefit guides. The guidance explains our approach to PDFs for each type of content and alternate solutions when we don’t recommend posting or linking to PDFs. The guidance also explains the accessibility concerns and requirements we need to consider with PDFs.
Word list
-
Added 4 new entries:
active and inactive (for account status)
When referring to someone’s account status, use “active,” “inactive,” and “to make your account active again.”
e.g., i.e., and ex.
Avoid using “e.g.,” “i.e.,” or “ex.” to introduce examples. Instead, use words like “for example” or “like.”
etc.
Don’t include “etc.” in a list of examples. Use “like” or “for example” to introduce the examples. This indicates that it may not be a full list.
recipient
In general, avoid using “recipient.” Instead, reword the sentence to use “the person who received the benefit,” “the person who will receive the benefit,” or similar. There are some exceptions where “recipient” is part of an understood or official term, like “Medal of Honor recipient.” In those cases, it’s OK to use “recipient.”
-
Revised 1 entry:
healthcare
1 word, never hyphenated as a compound adjective (for example, “healthcare system”). Lowercase unless it’s part of the official name of a VA medical center.
Note: This change aligns with new AP guidance. We’re working on updating this from 2 words to 1 across our content. But you may still find instances of “health care” while we’re working on these updates.
Exception: Defer to the VA medical center’s official name, which may have “health care” as 2 words.