Skip to accessibility statement

Accessibility Statement

Effective: July 2, 2026

Previous versions of this document are available upon request.

Our Commitment

Blueprint is committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and apply the relevant accessibility standards to ensure we provide equal access to all users.

As an education technology platform used by schools receiving federal funding, we take our obligation under Section 508 of the Rehabilitation Act seriously. Accessibility is a core requirement, not an afterthought.

Conformance Standards

Blueprint aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. These guidelines explain how to make web content more accessible to people with a wide array of disabilities, including:

  • Visual impairments (blindness, low vision, color blindness)
  • Hearing impairments
  • Motor impairments
  • Cognitive and learning disabilities

Conformance with these guidelines helps make content accessible to a wider range of people and also makes web content more usable to users in general.

Accessibility Features

Blueprint includes the following accessibility features across the current platform where implemented:

Perceivable

  • Meaningful images are intended to include descriptive alt text, while decorative images are intended to be hidden from assistive technology; a full alt-text audit is still pending
  • Color-coded statuses are designed to be paired with text or icons; inline links carry persistent underlines so they do not rely on color alone (covered by automated checks in our CI accessibility suite)
  • High-contrast text on dark surfaces: our CI accessibility suite runs automated WCAG AA contrast checks on the core public routes; remaining marketing routes and authenticated app surfaces are still being audited

Operable

  • Standard links, buttons, and form controls are keyboard reachable; the custom Discovery Quiz controls are built to be fully keyboard-operable, including arrow-key navigation and focus management across steps
  • Skip navigation links are provided on key public and legal pages, with full-route coverage still in progress
  • Visible focus indicators are used across interactive elements, including explicit high-visibility focus rings on the quiz controls; authenticated app surfaces still need a complete pass
  • No content flashes more than three times per second

Understandable

  • Key form inputs use visible labels or visible prompts, with a full form-label audit still pending
  • Error messages are written to identify the issue and next step, with programmatic field association still being reviewed
  • Public-page navigation uses consistent patterns, while focused quiz flows intentionally use step-by-step navigation
  • The page language is declared in HTML (lang="en")

Robust

  • Native semantic HTML is used where possible; custom components are being reviewed for complete name, role, and value support

Testing and Evaluation

We evaluate accessibility through a combination of methods:

  • Automated testing: axe-core WCAG 2.1 AA scans cover eight core public routes in our CI accessibility suite (landing, both quiz intros, the quiz email gate, sign-in, get-started, and the two accessibility pages) and are required to pass with zero rule exceptions. The suite runs on labeled pull requests and manual dispatch. Automated trusted-keyboard tests in the same suite cover the Matchmaker quiz steps (focus rings, arrow keys, selection, step-change focus).
  • Manual audits: Keyboard navigation, focus order, and focus visibility have been manually verified on the Discovery Quiz and sign-in flows; authenticated app routes are next.
  • Screen reader testing: VoiceOver testing has covered the Discovery Quiz, sign-in, and College Matchmaker flows (labels, roles, selection states, automatic error and step-change announcements). NVDA (Windows) review is planned against the production site.
  • Keyboard-only testing: The Discovery Quiz and sign-in flows were verified fully operable without a mouse.

Known Limitations

While we strive for full WCAG 2.1 AA compliance, we are aware of the following areas where we are actively working to improve:

  • Authenticated app controls (dashboard, essays, colleges) still need the complete keyboard and screen-reader review that the public and quiz surfaces have received.
  • Automated contrast checks currently cover the public routes; authenticated routes are not yet scanned in CI.
  • Screen-reader verification so far uses VoiceOver on macOS; NVDA and JAWS on Windows have not yet been tested.

We are committed to addressing these limitations and continuously improving accessibility.

Feedback and Assistance

We welcome feedback about the accessibility of Blueprint. If you encounter accessibility barriers or need assistance using any part of our platform, please contact us:

We aim to respond to accessibility feedback within 5 business days and to resolve accessibility issues within 30 days where technically feasible.

VPAT Availability

Blueprint publishes an Accessibility Conformance Report based on the ITI VPAT 2.5Rev WCAG format for school procurement offices. The report documents our current WCAG 2.1 Level AA self-assessment and is updated with major accessibility reviews.

View the current report at /accessibility/vpat. To request a reviewed copy or ask accessibility questions, contact us at accessibility@applywithblueprint.com.