Accessibility
Last updated 04-18-2026.
QuoteChecker should work for everyone, including people who use screen readers, keyboard-only navigation, voice control, or other assistive tech. We aim for WCAG 2.1 Level AA. We're not perfect — if something is broken for you, tell us and we'll fix it.
What works today
- Keyboard. Every button, link, form field, and modal can be reached and used with the keyboard alone. Focus is visible.
- Screen readers. Pages use real headings, lists, and landmarks. Icon-only buttons have labels. Form errors are announced.
- Contrast. Body text targets at least 4.5:1 against the background; controls target 3:1.
- Reduced motion. The animated background respects your
prefers-reduced-motionsetting. - Zoom. Pages reflow at 200% browser zoom without forcing a sideways scroll.
- Plain-text exports. The "Copy Report" button on every audit page gives you a clean, screen-reader-friendly text version.
Known gaps
These are real and we're working on them. If one of them blocks you, email us — we usually have a workaround.
- The decorative background canvas hasn't been tested with every screen reader and browser combination. It's marked hidden, but report anything that leaks through.
- The side-by-side compare view on
/pro/historyworks with the keyboard but hasn't been deeply tested with screen readers. - Sign-in, sign-up, and account screens are rendered by Clerk (our auth vendor). Issues there should be reported to us — we'll pass them on.
- Stripe Checkout runs on Stripe's own page. We don't control its accessibility but we can escalate problems on your behalf.
- Downloaded PDFs don't yet include tagged structure for screen readers. Use the "Copy Report" plain-text button as the accessible alternative.
How to tell us about a problem
Email contact@quotechecker.ai with "Accessibility" in the subject, or use the contact form. Useful to include:
- Which page (the URL).
- What you were trying to do.
- What happened, and what you expected.
- Your assistive tech, if relevant (screen reader, browser, OS).
We read every accessibility report and respond within two business days. We treat them as bugs, not feature requests.