From 43e7885b91e22f96bfbce68a898a430c711cbe41 Mon Sep 17 00:00:00 2001
From: Katie Fine <145465509+finekatie@users.noreply.github.com>
Date: Sun, 11 Aug 2024 17:22:18 -0400
Subject: [PATCH] Adding new disabled states guidance
adding new disabled states guidance per #2246
---
_includes/forms-guidance.html | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/_includes/forms-guidance.html b/_includes/forms-guidance.html
index 7b76086671..ec5215664d 100644
--- a/_includes/forms-guidance.html
+++ b/_includes/forms-guidance.html
@@ -16,6 +16,14 @@
Use simple vertical layouts. Keep your form blocks in a vertical pattern. This approach is
ideal, from an accessibility standpoint, because of limited vision that makes it hard to scan from right to left.
+ Keep form elements enabled and offer feedback. Don’t use disabled or unavailable states.
+ These states often don’t interact well with assistive technology, and they can confuse users. Instead, keep
+ elements enabled and use contextual helper text, tooltips,
+ helpful error messages,
+ and inline validation. These approaches can show what caused a problem and guide people to a solution.
+ For more detail, you can read
+ USWDS’s 2023 literature review on disabled states.
+
Identifying required fields
@@ -56,4 +64,4 @@ Known issues with screen readers
Note: These components have been designed to support a wide range of screen
readers, but they may not work with all versions.
-
\ No newline at end of file
+