Accessibility Is
Not Optional
WCAG 2.1 AA is now legally required for healthcare. We exceed it.
The HHS final rule mandates WCAG 2.1 Level AA compliance for all healthcare organizations receiving federal funding. WC-2026 does not just meet the bar -- every component is built to exceed it, targeting WCAG 2.2 AAA for critical interactions. Compliance is the floor, not the ceiling.
The Regulatory Timeline
Accessibility in healthcare is not aspirational -- it is a legal requirement with an immovable deadline. Here is where the industry stands.
Four Levels of Assurance
Automated tools catch roughly 30% of accessibility issues. That is why WC-2026 uses a four-level testing strategy -- from CI pipelines to real users with disabilities.
axe-core runs in every unit test and every Storybook story. Catches color contrast failures, missing ARIA labels, invalid roles, and structural issues automatically on every commit.
Storybook accessibility addon provides real-time a11y feedback during development. Tab-order visualization, keyboard interaction testing, and ARIA inspector integrated into the component playground.
Expert manual testing with JAWS, NVDA, and VoiceOver. Cognitive load assessment ensures components do not overwhelm users. Reading order, announcement quality, and interaction patterns verified by accessibility specialists.
The ultimate validation. Real users with visual, motor, cognitive, and auditory disabilities test critical workflows. Their feedback shapes component design decisions. Nothing replaces lived experience.
What Every Component Delivers
Every WC-2026 component ships with these seven accessibility guarantees. No exceptions. No opt-in flags. Accessible by default.
Every interactive element is reachable and operable via keyboard alone. Tab order follows logical reading order. Enter and Space activate controls. Escape closes overlays.
Semantic ARIA attributes, live regions for dynamic content, and proper role announcements. Tested with JAWS, NVDA, and VoiceOver on every release.
Information is never conveyed by color alone. Icons, text labels, and patterns supplement all color-coded indicators. Works for all types of color vision deficiency.
All animations respect prefers-reduced-motion. Users with vestibular
disorders never see unexpected motion. Critical for healthcare patients.
Full Windows High Contrast Mode support. Components adapt to forced-colors media query. Text meets 7:1 AAA contrast ratios in high-contrast themes.
All interactive elements meet the minimum 44x44 CSS pixel touch target. Users with motor impairments, tremors, or limited dexterity can activate every control.
Clear, high-contrast focus indicators on every interactive element. 3px solid ring with 3:1 contrast against adjacent colors. Never hidden, never suppressed.
Typical vs. WC-2026
Most component libraries treat accessibility as an afterthought. WC-2026 builds it into the architecture from the first line of code.
<!-- Typical component library --> <div class="btn" onclick="handleClick()"> Submit </div> <!-- No focus indicator --> <!-- No keyboard support --> <!-- No ARIA role --> <!-- No loading state --> <!-- Color-only disabled state -->
.btn { background: #6c757d; color: #999; /* Contrast ratio: 1.9:1 */ /* FAILS WCAG AA (4.5:1) */ } .btn:focus { outline: none; /* Focus indicator removed */ }
<!-- WC-2026 component --> <wc-button variant="primary" type="submit" aria-describedby="help-text"> Submit Form </wc-button> <!-- Focus ring: 3px solid, 3:1 contrast --> <!-- Enter + Space keyboard activation --> <!-- role="button" + aria-pressed --> <!-- aria-busy loading state --> <!-- Icon + text disabled indicator -->
:host { --btn-bg: var(--hds-interactive-primary); --btn-text: var(--hds-text-on-primary); /* Contrast ratio: 8.2:1 */ /* EXCEEDS WCAG AAA (7:1) */ } :host(:focus-visible) { outline: 3px solid var(--hds-focus-ring); outline-offset: 3px; }
POUR Principles Coverage
WCAG is organized around four principles: Perceivable, Operable, Understandable, and Robust. Here is how WC-2026 addresses each.
- 1.1 Text Alternatives -- Alt text for all non-text content
- 1.2 Time-based Media -- Captions and audio descriptions
- 1.3 Adaptable -- Meaningful structure and relationships
- 1.4 Distinguishable -- 7:1 AAA contrast ratios targeted
- 2.1 Keyboard Accessible -- All functionality via keyboard
- 2.2 Enough Time -- Adjustable time limits
- 2.3 Seizures -- No flashing content, motion-safe default
- 2.4 Navigable -- Focus order, skip links, breadcrumbs
- 2.5 Input Modalities -- 44x44px targets, no complex gestures
- 3.1 Readable -- Language identification, clear labels
- 3.2 Predictable -- Consistent navigation and behavior
- 3.3 Input Assistance -- Error prevention, suggestions, review
- 4.1.1 Parsing -- Valid HTML, no duplicate IDs
- 4.1.2 Name, Role, Value -- Full ARIA + ElementInternals
- 4.1.3 Status Messages -- Live regions for all updates
The Cost of Doing Nothing
Accessibility is not just the right thing to do -- it is a financial imperative. The numbers make the case undeniable.