Thanks to visit codestin.com
Credit goes to github.com

Skip to content
Closed
Changes from all commits
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
10 changes: 9 additions & 1 deletion _includes/forms-guidance.html
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,14 @@ <h2 id="general-accessibility-guidance-for-forms">Accessibility guidance</h2>
<li><strong>Use simple vertical layouts.</strong> 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.
</li>
<li><strong>Keep form elements enabled and offer feedback.</strong> 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,
<a href="https://www.w3.org/WAI/WCAG22/Understanding/error-suggestion.html">helpful error messages</a>,
and inline validation. These approaches can show what caused a problem and guide people to a solution.
For more detail, you can read
<a href="https://github.com/uswds/uswds/wiki/Disabled-States-Research-Findings-2023">USWDS’s 2023 literature review on disabled states</a>.
</li>
</ul>
<h2 id="identifying-required-fields">Identifying required fields</h2>
<ul class="usa-content-list">
Expand Down Expand Up @@ -56,4 +64,4 @@ <h2 id="known-issues-with-screen-readers">Known issues with screen readers</h2>
</ul>
<div class="site-note"><strong>Note:</strong> These components have been designed to support a wide range of screen
readers, but they may not work with all versions.</div>
</section>
</section>