Accessibility
Not a checkbox. Not a post-launch initiative. One of 28 firm-level standards enforced at the architecture level — the same level as security, privacy, and engineering. Every product, every page, every interaction.
Our Standard
Every LEAPWare product and web surface meets WCAG 2.2 Level AA. Not "mostly compliant." Not "AA except for this component." Full compliance, verified before launch.
Every interactive element reachable by tab. Every action completable without a mouse. Focus indicators visible on all focusable elements. No keyboard traps. Skip-to-content links on every page. Tab order follows logical reading order, not DOM order where they diverge.
Semantic HTML throughout. ARIA labels on all interactive components. Live regions for dynamic content updates. Tested with VoiceOver (macOS/iOS) on all primary user journeys. Heading hierarchy (h1→h2→h3) maintained without skips on every page.
Color contrast minimum 4.5:1 for normal text, 3:1 for large text — verified against our Graphite design system tokens. Color is never the sole indicator of state — every status communicates through text, icons, or patterns alongside color. Support for high contrast mode and system color preferences.
All animations disabled when prefers-reduced-motion is set — non-negotiable. No content flashes more than 3 times per second. Touch targets minimum 44×44px. No time-limited interactions without user control over timing.
Accessibility is tested at four levels before any LEAPWare surface goes live:
Automated testing — axe DevTools integrated into CI/CD. Zero critical or serious violations required for deployment. Automated scans run on every build, not just before launch.
Manual keyboard testing — every interactive element on every page tested for keyboard reachability. Every multi-step flow (onboarding, knowledge creation, agent configuration) tested for keyboard-only completion.
Screen reader testing — VoiceOver (macOS/iOS) spot-check on all primary user journeys. We verify that the screen reader experience conveys the same information and enables the same actions as the visual experience.
Design system enforcement — our Graphite design system (three-panel Outlook layout, Plus Jakarta Sans / Inter / JetBrains Mono typography, 4px grid) has accessibility baked into every token and component. Contrast ratios are verified at the token level — if a developer uses the design system correctly, accessibility is automatic.
LEAPWare products are designed to work with screen readers (VoiceOver, NVDA, JAWS), voice control (Voice Control on macOS/iOS), switch access devices, screen magnifiers, and high-contrast display modes. If you encounter an issue with your assistive technology, we want to know.
If you encounter an accessibility barrier on any LEAPWare surface — website, product, documentation, or any other property — please tell us:
Every report is reviewed by the team. We acknowledge receipt within 24 hours and provide a remediation timeline within 5 business days. Accessibility barriers are classified as P1 (blocking) or P2 (degraded experience) and remediated on the same priority track as security vulnerabilities.
Accessibility is not a launch milestone — it is a continuous obligation. Our accessibility standard is a living governance document with version control, audit history, and mandatory enforcement. When WCAG standards evolve, our standard evolves with them. When assistive technology capabilities expand, our testing expands to cover them.