hey prescott.
Accessibility

Accessibility statement

Last updated May 21, 2026

Plain-English summary
  • Target: WCAG 2.2 AA across web, iOS, and Android.
  • External audit pre-launch. Annual re-audits; quarterly internal axe + manual screen-reader checks.
  • 5 business-day acknowledgment SLA on reports. P0 issues fixed before deploy.
  • VPAT 2.4 available at /accessibility/vpat for institutional buyers.

1. Our commitment

Hey Prescott is for everyone navigating a down-payment-assistance search — including people who use screen readers, keyboards instead of pointers, magnified or high-contrast displays, or voice control. We treat accessibility as a baseline product quality, not a checkbox, and we test against the real assistive-tech stacks our users rely on.

2. Conformance level

We target conformance with the Web Content Accessibility Guidelines 2.2 at the AA level on the web, and Apple's and Google's respective accessibility guidelines on iOS and Android. Areas where we know we fall short are listed under Known issues.

3. Built-in features

  • Keyboard navigation for every interactive surface; visible focus indicators.
  • Semantic HTML and ARIA labels — Prescott chat, the wizard, and the program directory are all screen-reader navigable.
  • prefers-reduced-motion respected for transitions and celebrations.
  • Color contrast verified against the design-system palette (4.5:1 for body text, 3:1 for large text).
  • Touch targets at least 44×44 pt on iOS / 48×48 dp on Android per platform guidelines.
  • Dynamic Type (iOS) and Font Scale (Android) supported up to 200% without breaking layout.

4. Known issues

We update this list as issues are reported, found in our internal audits, or remediated. ETAs are best-effort, not contractual.

Currently tracking

  • Range sliders in the wizard — keyboard users get sliders today; we are adding a number-input alternative for income, credit, and savings inputs in v1.1. Severity P1.
  • Prescott chat live-region throttling — streaming responses can over-announce to screen readers on slow connections. Working on debounced announcements. Severity P2.
  • Mobile high-contrast iconography — a few decorative icons drop below 3:1 in iOS Smart Invert. Tracking. Severity P3.

5. Audit cadence

  • Pre-launch external audit by a financial-services accessibility specialist (WCAG 2.2 AA across web + mobile native).
  • Quarterly internal audits using axe DevTools and mobile accessibility scanners; manual VoiceOver / TalkBack / NVDA walkthroughs.
  • Annual external re-audit, or sooner after any major redesign.
  • Continuous monitoring via eslint-plugin-jsx-a11y on every PR and Lighthouse accessibility checks in CI.

6. Report an issue

If you encounter a barrier using Hey Prescott — anything from a missing label to a flow that won't complete with your assistive tech — please tell us.

Report an accessibility issue →

We acknowledge every report within 5 business days. Resolution targets by severity: P0 fixed before next deploy, P1 within 30 days, P2 within 90 days, P3 backlog with public ETA.

7. Contact

Accessibility lead: accessibility@heyprescott.com. We prefer the report form so we can triage with full context, but plain email works too.

Looking for our VPAT? It's at /accessibility/vpat.