Accessibility is a product requirement.
SpecSprout targets WCAG 2.2 Level AA for its public site and authenticated workspace. Accessibility is tested as an ongoing engineering constraint rather than treated as a final cosmetic pass.
What the current build supports
- Keyboard navigation with visible focus states and skip-to-content links.
- Focus-managed modal dialogs that trap focus, close with Escape and return focus to the invoking control.
- Screen-reader labels and live announcements for status, validation errors and progress.
- Accessible readiness/progress indicators that expose numeric values without relying on color.
- Reduced-motion behavior that respects the operating-system preference.
- High-contrast/forced-colors support and contrast-checked core color pairs.
- Semantic headings, landmarks, labels and table headers on primary public and application surfaces.
Keyboard basics
Use Tab and Shift+Tab to move through interactive controls. Enter or Space activates buttons and interactive project rows. Escape closes SpecSprout dialogs. The first focusable control on every page is a skip link that moves directly to the main content.
Readiness is not color-only
Confirmed, Partial, Deferred, Inferred and Missing states are shown with text labels as well as visual styling. Readiness bars expose their numeric percentage to assistive technology, and hard-gate explanations are provided in text.
Known testing boundary
Automated checks catch structural regressions, but they cannot replace testing with real browsers and assistive technology. Before broad public launch, the release checklist requires keyboard-only testing, browser zoom testing and screen-reader smoke tests on representative desktop and mobile combinations.
Report an accessibility problem
You can contact support without signing in, or use Support in your account. Include the page or workflow, what you expected to happen, and your browser or assistive technology if relevant. Please avoid sending confidential product content.