uat_docs_part_2.md

UAT Documentation (Part 2) : : Accessibility and Usability Acceptance Criteria

Companion to : : UAT Documentation (Part 1) : : Accessibility and Usability Requirements

---

📚 References

• Section 508 Standards
• WCAG 2.2 Level AA
• US Web Design System (USWDS)
• ISO 9241-210
• Nielsen Norman Group Heuristics
• Direct Access vs. Sequential Access: Definition (NNG)
• Corporate Reference: ICT Accessibility Standards Scoresheet v2.2-1

---

✨ Context

This document provides a comprehensive set of Acceptance Criteria (AC) for accessibility and User Experience (UX) guidelines for usability that can be integrated into story requirements, Jira tickets, and QA processes. It is intended to help development teams meet legal obligations, organizational policy, and industry best practices for inclusive design and development.

These criteria are:

• Data-agnostic (independent of backend or schema)
• Framework-agnostic (works with or without React, Angular, etc.)
• Platform-agnostic (usable on web, mobile, intranet, kiosk, etc.)
• Browser-agnostic (compatible with all modern standards-compliant browsers)

---

🔍 Definitions

Term	Definition
Accessibility	The degree to which a system is usable by people with a wide range of physical, sensory, and cognitive abilities. Governed by WCAG 2.2 and Section 508.
Usability	The effectiveness, efficiency, and satisfaction with which users achieve their goals. Not governed by law but critical for reducing user friction and cognitive load.

💡 Example: Usability ≠ Accessibility

Direct access to actions (e.g. contextual menus) vs. sequential navigation (e.g. multiple screens or steps) is a usability guideline—not an accessibility requirement (NNG)

---

📄 Accessibility Requirements (Testable)

NOTE: AC numbering is unique to this UAT document.

AC-01 : : All interactive elements are operable via keyboard navigation alone. (WCAG 2.2: 2.1.1, USWDS)

AC-02 : : Focus is clearly visible on all interactive elements. (WCAG 2.2: 2.4.7)

AC-03 : : Page content is navigable in a logical order using semantic HTML. (WCAG 2.2: 1.3.1, 2.4.3)

AC-04 : : Non-text content has equivalent text alternatives. (WCAG 2.2: 1.1.1)

AC-05 : : Text contrast ratio meets 4.5:1 minimum. (WCAG 2.2: 1.4.3)

AC-06 : : Color is not the only method of conveying information. (WCAG 2.2: 1.4.1)

AC-07 : : ARIA roles and properties reflect current state. (WCAG 2.2: 4.1.2)

AC-08 : : Form fields include accessible labels or names. (WCAG 2.2: 3.3.2)

AC-09 : : No interaction requires gestures without a fallback. (WCAG 2.2: 2.5.1)

AC-10 : : Content changes are announced to assistive tech. (WCAG 2.2: 4.1.3)

AC-11 : : Layout supports 400% zoom at 1280px without two scrollbars. (ICT Scoresheet v2.2-1)

AC-12 : : Motion and animation respect user preferences (WCAG 2.2: 2.3.1)

Code Example:

@media (prefers-reduced-motion: reduce) {
  * {
    animation: none !important;
    transition: none !important;
  }
}

/* Optional toggle: */

[data-motion="off"] * {
  animation: none !important;
  transition: none !important;
}

AC-13 : : Headings follow a meaningful, nested order (no skipped levels). (WCAG 2.2: 1.3.1)

AC-14 : : Every page includes a mechanism to skip to main content. (WCAG 2.2: 2.4.1)

Code Example:

<!-- HTML -->
<a href="#main-content" class="skip-link">Skip to main content</a>

/* CSS */
.skip-link {
  position: absolute;
  top: -40px;
  left: 0;
  background: #000;
  color: #fff;
  padding: 8px;
  z-index: 100;
  text-decoration: none;
}

.skip-link:focus {
  top: 0;
}

<!-- HTML -->
<main id="main-content">
  <!-- Main content starts here -->
</main>

AC-15 : : Forms provide error identification and suggestions for correction. (WCAG 2.2: 3.3.1, 3.3.3)

AC-16 : : All functionality is available from the keyboard. (WCAG 2.2: 2.1.1)

AC-17 : : Pages have unique and meaningful titles. (WCAG 2.2: 2.4.2)

---

🌎 User Experience Guidelines (Benefits All Users)

NOTE: UX numbering is unique to this UAT document.

UX-01 : : Interfaces support efficient task flow. (ISO 9241-210)

UX-02 : : Errors include clear instructions. (NNGroup)

UX-03 : : Interaction patterns are consistent. (NNGroup)

UX-04 : : All actions give visible feedback. (NNGroup)

UX-05 : : Labels and UI language follow plain language. (USWDS)

UX-06 : : Related options are visually grouped. (NNGroup)

UX-07 : : Navigation is clear and intuitive. (NNGroup)

UX-08 : : Users can undo actions where possible. (NNGroup)

UX-09 : : Layouts adapt to viewport without truncation. (USWDS)

UX-10 : : Logical properties are used for internationalization. (MDN)

Code Example:

/* Instead of margin-left, use: */
margin-inline-start: 1rem;

UX-11 : : Interactive controls are large enough to avoid input errors. (ISO 9241-210, USWDS)

UX-12 : : Essential tasks can be completed in no more than three steps. (NNGroup: Efficiency of Use)

UX-13 : : Users can identify their current location in the app/site structure. (NNGroup: Visibility of System Status)

UX-14 : : Help and documentation is available when needed. (NNGroup)

UX-15 : : Long processes provide checkpoints or progress indicators. (NNGroup: User Control and Freedom)

---

This list may be adapted per feature scope. These are functional and testable, not enhancements.

---

Next up : : UAT Documentation (Part 3) : : Developer Experience (DX) Principles and Criteria