Skip to content

Accessibility

QuotWay works toward WCAG 2.1 Level AA across our marketing site, our documentation, and the buyer-facing experience. We treat accessibility as part of building the product, not a finishing step. This statement explains what that means in practice, where we know we have more to do, and how to tell us when something doesn't work for you.

Our commitment

We want anyone to be able to find out what QuotWay does, set it up, and request or negotiate a quote, regardless of how they use the web. Our target is WCAG 2.1 AA for the public marketing site, the documentation site, and the buyer-facing experience (the quote drawer, the buyer portal, and quote emails).

We aim for AA, and we test against it, but we do not claim full or certified conformance. Accessibility is ongoing work: pages change, content gets added, and assistive technology evolves. When we find a gap, we fix it and update this page.

What we do

These are the practices we build to:

  • Semantic HTML. One <h1> per page, a logical heading order, landmark regions (header, nav, main, footer), real lists for lists, <button> for actions, and <a> for navigation.
  • Keyboard operability. Every interactive element - including the navigation menu and the interactive demos - can be reached and used with a keyboard alone, in a logical tab order, with a skip-to-content link near the top of each page.
  • Visible focus. A clear, high-contrast focus ring follows the keyboard so you always know where you are.
  • Sufficient contrast. Text and interactive elements meet the AA contrast minimums (4.5:1 for normal text, 3:1 for large text and UI). We never use color as the only way to convey meaning.
  • Reduced-motion support. We respect prefers-reduced-motion. When you ask your system to reduce motion, animated demos offer a static or step-through view instead, and motion is never required to understand a page.
  • Captions and a transcript for the demo video. The product demo video has captions, and a text transcript is available.
  • Alt text. Meaningful images carry descriptive alt text; decorative images are marked so screen readers skip them.
  • Accessible forms. Form fields have programmatic labels, errors are described in text rather than by color alone, and error messages are linked to the field they describe.

Known limitations

We would rather tell you where we fall short than pretend we're perfect. As of the date above, we are not tracking any specific unresolved barriers against WCAG 2.1 AA. Accessibility is ongoing work, so this can change between reviews - and reports are how we find what we've missed.

If you hit an accessibility barrier that isn't listed here, please tell us - see below. We treat reports as the fastest way to find what we've missed.

How to report an accessibility problem

Email accessibility@quotway.com and tell us:

  • the page or URL where you ran into the problem,
  • what you were trying to do, and
  • the browser, device, and any assistive technology you were using, if you can.

You don't need technical detail - a plain description of what didn't work is enough. We aim to acknowledge your message and to work with you on a fix or a workaround.

Standards and approach

We measure ourselves against WCAG 2.1 Level AA. Our testing approach combines automated and manual checks before each release:

  • Automated: axe-core runs in our continuous-integration pipeline, so common issues are caught before changes ship.
  • Manual keyboard pass: we navigate key pages and flows using only the keyboard.
  • Screen-reader smoke test: we check key pages with a screen reader (VoiceOver and/or NVDA).

Automated tools catch only part of what matters, which is why the manual passes and your feedback are essential. We welcome it - accessibility reports make the product better for everyone.

This statement was last reviewed on June 20, 2026.