Pular para o conteúdo principal
7Anospor MADITECH7 Anos · por MADITECH

Accessibility Statement

Last updated:

Honest status, not a marketing claim. JOEY targets WCAG 2.2 Level AA. We are partially conformant: most of the site meets that standard, and the specific gaps we know about today are listed below in plain language, not buried. This page is updated as each one is fixed.

1. Our commitment

JOEY is used by salespeople and dealership staff of every ability, so the product has to work with a keyboard alone, with a screen reader, with reduced motion turned on, and with reading and vision needs of every kind. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the W3C. We test toward that standard on an ongoing basis rather than treating it as a one-time project.

2. Conformance status

Partially conformant. This means some parts of getjoey.app do not yet fully meet WCAG 2.2 Level AA. It does not mean the site is unusable with assistive technology; it means we know of specific gaps, we have written them down, and we are working through them in order of impact.

3. Known issues

From our most recent internal review (July 31, 2026). Listed worst impact first.

  • No “skip to main content” link. A keyboard user landing on any page has to tab through the full header before reaching the page content. This affects every page on the site.
  • Some brand-orange text does not meet the 4.5:1 contrast minimum. Our brand orange, used as a text color in a few places (small eyebrow labels and some inline links on the pay-as-you-go and API pricing pages, among others), measures at roughly 3:1 against its background rather than the required 4.5:1 for normal-size text. Larger, bolder text using the same color is closer to compliant. Where we have already found this, we now use a darker shade of the same color for text, and we are extending that fix to the remaining spots.
  • One landing page design can be hard to read in dark mode. One of our rotating homepage designs uses a deliberately pale background and was built assuming a light color scheme. If a visitor has our site set to dark mode, that specific design can render pale text on a pale background, making the main heading difficult to read. Our other homepage designs do not have this problem.
  • A homepage product video autoplays with no visible pause control and no captions. The product walkthrough clip on the homepage plays and loops automatically. It has no visible controls, so a visitor cannot pause, stop, or hide it, and it has no caption track. The clip is muted by default and shows product screens rather than spoken narration, but we have not confirmed every recorded take is free of audio, and the lack of a pause control is a gap on its own.
  • Two newer pages render a duplicate main landmark. The pay-as-you-go and API pricing pages each render their own main element inside the page's shared one, which can confuse screen-reader landmark navigation on those two pages.

4. How we tested (and what we have not tested yet)

What we have done: a manual review of the homepage hero and its animated variants, the cookie consent banner, the site header and footer, and the pay-as-you-go and API pricing pages against the WCAG 2.2 Level AA success criteria, including color contrast, heading structure, keyboard focus, reduced-motion behavior, and form labeling.

What we have not done yet: we have not run a dedicated testing session with a screen reader (VoiceOver, NVDA, or JAWS), a switch device, or voice control software, and we have not yet done usability testing with people who use assistive technology day to day. Until that testing happens, treat this statement as accurate for what a code-level review can find, not as proof that every real assistive-technology workflow has been verified.

5. Technical specifications

Accessibility on getjoey.app relies on HTML5, WAI-ARIA, and CSS, and on the accessibility support already built into your browser and assistive technology. These technologies are relied upon for conformance with the accessibility standards used.

6. Reporting a problem

If you run into an accessibility barrier anywhere on getjoey.app, tell us. Use the form on our Contact page, or email support@getjoey.app. Please include the page URL and, if you can, the assistive technology and browser you were using. We aim to acknowledge accessibility reports within 5 business days.

7. Scope of this statement

This statement covers the public getjoey.app marketing site and the pages linked from it. It does not separately cover third-party services we embed or link to, which publish their own accessibility statements.

Accessibility Statement | JOEY