Visitar URL original
Form component: Updated Disabled States guidance by finekatie · Pull Request #2776 · uswds/uswds-site · GitHub
Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update _includes/forms-guidance.html
Co-authored-by: Charlie Mahoney <charlie.mahoney@bixal.com>
  • Loading branch information
finekatie and Charlie Mahoney authored Aug 23, 2024
commit 92240e7a022447f3d81d0f9dfea155a96e4c9a93
2 changes: 1 addition & 1 deletion _includes/forms-guidance.html
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ <h2 id="disabled-states-for-components-in-forms">Disabled states for components
<li><strong>Don’t use disabled states, especially for text inputs.</strong> Disabled states have low color contrast,
Comment thread
amyleadem marked this conversation as resolved.
Resolved
do not offer meaningful feedback to screen reader users, and keyboard navigators can’t focus on them.
These states can also be generally confusing to users. Instead, keep form elements enabled.
Offer <a href="https://www.w3.org/WAI/WCAG22/Understanding/error-suggestion.html">helpful error messages</a>
Offer contextual helper text, tooltips, <a href="https://www.w3.org/WAI/WCAG22/Understanding/error-suggestion.html">helpful error messages</a>
and inline validation to help people correct mistakes and move through the form.</li>
<li><p><strong>If you <i>must</i> use disabled states, follow best practices.</strong> Some disabled states can prevent errors
by telling users that a system is loading or processing (for example, to prevent multiple form
Expand Down