From 3823d01d199697e0e87ac79643b6f65185922d35 Mon Sep 17 00:00:00 2001 From: Ryan Smith Date: Mon, 16 Dec 2024 11:26:37 -0500 Subject: [PATCH 1/2] Fix a11y testing link --- src/_about/accessibility/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_about/accessibility/index.md b/src/_about/accessibility/index.md index 03e86d406..2ecd4561f 100644 --- a/src/_about/accessibility/index.md +++ b/src/_about/accessibility/index.md @@ -19,7 +19,7 @@ Therefore, [accessibility is core to all design decisions]({{ site.baseurl }}/ab The VA Design System provides accessible components, the guidance to implement these components, and the tools to customize and extend the design system accessibly. It was built on top of a fork of the U.S. Web Design System (USWDS), which prioritizes accessibility throughout. [Learn more about how USWDS practices accessibility.](https://designsystem.digital.gov/documentation/accessibility/) -Components don’t live in a vacuum. As standalone elements, they can only be tested atomically. [Learn more about how VA Design System components are tested.](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/blob/8b49df2eddc3956daf9cff03728430311c597631/about/accessibility/accessibility-testing) For a product to launch, you need to test holistically; you should review the product as a whole before launch. +Components don’t live in a vacuum. As standalone elements, they can only be tested atomically. [Learn more about how VA Design System components are tested.](/about/accessibility/accessibility-testing-for-design-system-components) For a product to launch, you need to test holistically; you should review the product as a whole before launch. The surest way to make an accessible product is to “shift left,” or prioritize accessibility during an entire project’s lifecycle. From c5b24957439d1447a9b1b2b105b43ef122815f45 Mon Sep 17 00:00:00 2001 From: Matthew Dingee <52176351+humancompanion-usds@users.noreply.github.com> Date: Mon, 16 Dec 2024 12:59:28 -0500 Subject: [PATCH 2/2] Update index.md Adding the site.baseurl which I think we still need when we deploy to different environments because of the way Jekyll is configured. --- src/_about/accessibility/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_about/accessibility/index.md b/src/_about/accessibility/index.md index 2ecd4561f..96511bd18 100644 --- a/src/_about/accessibility/index.md +++ b/src/_about/accessibility/index.md @@ -19,7 +19,7 @@ Therefore, [accessibility is core to all design decisions]({{ site.baseurl }}/ab The VA Design System provides accessible components, the guidance to implement these components, and the tools to customize and extend the design system accessibly. It was built on top of a fork of the U.S. Web Design System (USWDS), which prioritizes accessibility throughout. [Learn more about how USWDS practices accessibility.](https://designsystem.digital.gov/documentation/accessibility/) -Components don’t live in a vacuum. As standalone elements, they can only be tested atomically. [Learn more about how VA Design System components are tested.](/about/accessibility/accessibility-testing-for-design-system-components) For a product to launch, you need to test holistically; you should review the product as a whole before launch. +Components don’t live in a vacuum. As standalone elements, they can only be tested atomically. [Learn more about how VA Design System components are tested.]({{ site.baseurl }}/about/accessibility/accessibility-testing-for-design-system-components) For a product to launch, you need to test holistically; you should review the product as a whole before launch. The surest way to make an accessible product is to “shift left,” or prioritize accessibility during an entire project’s lifecycle.