Accessibility

Accessibility is a
governance standard

Not a checkbox. Not a post-launch initiative. One of 28 firm-level standards enforced at the architecture level — the same priority as security, privacy, and engineering quality. Every product, every page, every interaction.

Compliance Framework

Three standards. Full conformance.

LEAPWare products and web properties conform to three internationally recognized accessibility standards. Not "mostly compliant" — full conformance, verified before every release.

WCAG 2.2 Level AA

The Web Content Accessibility Guidelines published by the W3C. All four principles — Perceivable, Operable, Understandable, Robust — satisfied across every LEAPWare surface. Level AA is the conformance target; we pursue AAA where technically feasible without degrading the experience for other users.

Section 508

The United States federal accessibility standard (29 U.S.C. § 794d) requiring electronic and information technology to be accessible to people with disabilities. LEAPWare products meet Section 508 requirements, enabling procurement by federal agencies and organizations with Section 508 obligations.

EN 301 549

The European harmonized standard for ICT accessibility, aligned with WCAG 2.1 Level AA and extending to non-web ICT including documentation and support services. LEAPWare products conform to EN 301 549 V3.2.1 (2021-03), supporting procurement under European Accessibility Act obligations.

VPAT & Procurement Documentation

Enterprise procurement-ready

Voluntary Product Accessibility Template (VPAT). LEAPWare maintains a current VPAT 2.5 (International Edition) documenting conformance to WCAG 2.2 AA, Section 508, and EN 301 549. The VPAT is available on request for enterprise procurement evaluation. Contact accessibility@leapware.ai to request a copy.

Accessibility Conformance Report (ACR). The VPAT includes a detailed Accessibility Conformance Report mapping each success criterion to conformance level (Supports, Partially Supports, Does Not Support, Not Applicable) with specific remarks for any partial conformance. Updated with each major product release.

Government and Education Procurement. LEAPWare provides documentation packages for Section 508 procurement (US federal), EN 301 549 procurement (EU public sector), and state-level accessibility mandates. If your procurement process requires additional documentation, we will provide it.

Implementation

How we build accessible products

Accessibility is enforced at four layers of our development process — design system, code, testing, and release gating.

Keyboard Navigation

Every interactive element reachable by Tab. Every action completable without a mouse. Visible focus indicators on all focusable elements using our :focus-visible system. No keyboard traps. Skip-to-content links on every page. Tab order follows logical reading order. Custom keyboard shortcuts documented and non-conflicting with assistive technology defaults.

Screen Reader Compatibility

Semantic HTML throughout — no div soup. ARIA labels on all interactive components. ARIA live regions for dynamic content updates (agent status changes, knowledge mutations, notification toasts). Heading hierarchy (h1→h6) maintained without skips. Landmark roles on every page. Tested against NVDA, JAWS, and VoiceOver on all primary user journeys.

Visual Accessibility

Color contrast minimum 4.5:1 for normal text, 3:1 for large text and UI components — verified against our Graphite design system tokens at the token level. Color is never the sole indicator of state — every status uses text, icons, or patterns alongside color. Tested with Sim Daltonism for protanopia, deuteranopia, and tritanopia. Support for forced-colors mode and system contrast preferences.

Motion and Interaction

All non-essential animations disabled when prefers-reduced-motion: reduce is set — non-negotiable, enforced at the design system level. No content flashes exceed three times per second (WCAG 2.3.1). Touch targets minimum 44×44px (WCAG 2.5.8). No time-limited interactions without user control. Scroll-triggered animations respect motion preferences.

Verification

Five-level testing before every release

Level 1: Automated CI/CD scanning. axe-core integrated into our continuous integration pipeline. Zero critical or serious violations required for deployment — builds fail automatically on accessibility regression. Automated scans execute on every commit, not just before release.

Level 2: Manual keyboard testing. Every interactive element on every page tested for keyboard reachability. Every multi-step flow (onboarding, knowledge creation, agent configuration, synthesis review) tested for keyboard-only completion. Documented in our QA checklist with pass/fail per flow.

Level 3: Screen reader testing. Primary user journeys tested with NVDA (Windows), JAWS (Windows), and VoiceOver (macOS/iOS). We verify that the screen reader experience conveys equivalent information and enables equivalent actions to the visual experience. Testing covers navigation, data input, status updates, and error recovery.

Level 4: Color and contrast verification. Every new component verified against WCAG contrast requirements using automated tools and manual inspection. Color blindness simulation testing using Sim Daltonism across protanopia, deuteranopia, and tritanopia profiles. High-contrast mode verification on Windows and macOS.

Level 5: Independent third-party audit. Annual accessibility audit conducted by a certified third-party assessor (IAAP CPWA or equivalent credential). Audit scope covers all production web surfaces and primary product flows. Findings are remediated on the same priority track as security vulnerabilities. Audit summary available on request.

Assistive Technology

Tested with real assistive technology

Screen Readers

NVDA (Windows) — primary testing target for Windows users. JAWS (Windows) — tested for enterprise environments where JAWS is standard. VoiceOver (macOS and iOS) — primary testing target for Apple platform users. TalkBack (Android) — tested for mobile web access.

Voice Control

Voice Control (macOS/iOS) and Windows Speech Recognition tested for primary navigation and data entry flows. All interactive elements have accessible names that can be spoken as voice commands.

Switch Access and Alternative Input

Switch Control (iOS), Switch Access (Android), and keyboard-based switch emulation tested. All interactive sequences completable with single-switch scanning. No interaction requires simultaneous multi-key input beyond standard modifier combinations.

Screen Magnification

ZoomText (Windows), macOS Zoom, and browser-level zoom tested up to 400%. Layout remains functional and content remains readable at all supported zoom levels. No horizontal scrolling required at 400% zoom on standard viewport widths (WCAG 1.4.10).

Media Accessibility

All video content includes synchronized captions (WCAG 1.2.2) and audio descriptions where visual content conveys information not available in the audio track (WCAG 1.2.5). Transcripts provided for all audio and video content. Caption files use WebVTT format. Documentation PDFs are tagged for screen reader accessibility with proper reading order, alt text, and table structure.

Mobile Accessibility

Fully accessible on every device

LEAPWare web surfaces and products are tested for accessibility on mobile devices across iOS and Android platforms:

  • iOS: VoiceOver, Voice Control, Switch Control, Dynamic Type (up to Accessibility XXL), Reduce Motion, Increase Contrast, Smart Invert
  • Android: TalkBack, Voice Access, Switch Access, font scaling (up to 200%), high contrast text, Remove Animations

Touch targets meet the 44×44px minimum. Gesture-based interactions always have single-pointer alternatives. Orientation is not locked — content works in both portrait and landscape (WCAG 1.3.4).

Reporting & Remediation

Report a barrier. We will fix it.

If you encounter an accessibility barrier on any LEAPWare surface — website, product, documentation, or any other property — report it to:

accessibility@leapware.ai

Please include: the URL or product area, your assistive technology (if applicable), a description of the barrier, and your expected behavior. Screenshots or recordings are helpful but not required.

Response Commitments

  • Acknowledgment: within 24 hours of receipt
  • Triage and severity classification: within 3 business days
  • P1 (Blocking barrier): remediation within 5 business days — treated at the same priority as a security vulnerability
  • P2 (Degraded experience): remediation within 15 business days
  • P3 (Minor inconvenience): remediation in the next scheduled release

All reports receive a resolution notification explaining what was fixed and when the fix is available.

Roadmap

Accessibility roadmap — 2026

  • Q2 2026: Complete independent third-party WCAG 2.2 AA audit across all production surfaces. Publish audit summary.
  • Q2 2026: Publish VPAT 2.5 (International Edition) for LEAPCortex and LEAPControl.
  • Q3 2026: Expand screen reader testing to include JAWS on all primary flows (currently spot-check coverage).
  • Q3 2026: Implement real-time accessibility monitoring in production (continuous axe-core scanning on live pages).
  • Q4 2026: Evaluate WCAG 2.2 Level AAA conformance for documentation and marketing surfaces.
  • Q4 2026: Publish accessibility testing methodology as an open governance document.

Ongoing Commitment

Accessibility is not a launch milestone — it is a continuous obligation governed by the LEAPWare Accessibility Standard (one of 28 firm-level governance standards). The standard is a living document with version control, audit history, and mandatory enforcement. When WCAG evolves, our standard evolves. When assistive technology capabilities expand, our testing expands. Accessibility regressions are treated as defects with the same severity classification as functional bugs.

This accessibility statement was last reviewed on March 27, 2026. It is reviewed and updated with each major product release and at minimum quarterly.