Accessibility statement

We want everyone to be able to use CarPairly. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. This is our target, not a certified result. No outside body has audited the site. This page is based on our own code, on checks built into that code and on manual checks we made in October 2026.

What we build in

Keyboard use. The first thing you reach with the Tab key on every page is a "Skip to main content" link. We build with standard links, buttons and form controls, so the site works with a keyboard. The focus ring is a 3 pixel outline.
Labels. Every form field has a label, including the car filters, the compare pickers and the search box. Errors appear as text with an icon, not only as a color.
Not by color alone. Electric and gas cars are named in text as well as colored. Tax treatment, the lowest price and the better value in a comparison each have words or an icon, not only a color.
Contrast. Text and controls use a fixed set of colors. We check the color pairs against the WCAG contrast ratios in both themes: 4.5 to 1 for text and 3 to 1 for controls.
Light and dark themes. The site follows your system setting. A "Dark mode" button in the header switches themes, and your choice stays in your browser only.
Reduced motion. Animation is switched on only if your system does not ask for reduced motion. Animations run once, are brief and never loop.
Forced colors. In high contrast modes, buttons and fields keep a border and the focus ring stays visible.
Small screens. Pages reflow without sideways scrolling. Wide tables scroll inside their own box, which you can reach with the keyboard and scroll with the arrow keys.
Touch targets. Most buttons and fields are at least 44 pixels tall. The small buttons are 36 pixels tall and the navigation links 40 pixels, which is above the WCAG 2.2 minimum of 24 pixels.
Price conversions. Where a price is converted, the "≈" sign is hidden from screen readers and the word "approximately" is read out instead.
Without JavaScript. The car filters and the compare picker are ordinary forms and work without JavaScript. The market picker, the currency button and the theme button need it. Without JavaScript the site shows United States prices and follows your system theme.

What we check

Checks built into the code. Our tests read the shipped style sheet and compute the WCAG contrast ratio of the main color pairs in the light and the dark theme. Other tests check the order of the page landmarks, which starts with the skip link, that each page has one main heading and that headings do not skip a level, and that the style sheet handles reduced motion. These tests run on every change. They cover the markup and the CSS, not how the page looks or feels in a browser.

Manual checks in October 2026. On 23 October 2026 we ran the axe-core accessibility scanner by hand over 46 pages at 390, 820 and 1440 pixels wide, in the light and the dark theme, and tried the keyboard on the main pages. The skip link came first, the focus ring showed on every stop and we found no keyboard trap. There was no sideways scrolling at 320 and 390 pixels. That review also found a price chart that the keyboard could not reach, and we fixed it. On 24 October 2026 we checked again by hand the keyboard use of the currency button and its menu, the pages with reduced motion on, and the header at 360, 390 and 768 pixels in both themes, and found no overflow. An axe scan of a brand page, the electric and gas lists and the search results then reported no problems, after we changed a card animation that started with too little contrast. These checks are not part of the automatic build, so a later change can break something they found fine. We plan to repeat them before a release.

What we have not tested

Automated tools find only part of the problems. They cannot judge whether a label makes sense or whether the reading order helps. We have not tested the site with a screen reader, and no outside audit has been done.
We have not tested every page by hand. The manual checks above covered the main pages, not each guide, glossary entry or report.
When ads are live, they and the consent screen come from outside companies, and we cannot fully control their accessibility. We reserve their space, label them and keep them away from buttons. See our advertising page.

Report a barrier

If you cannot use part of CarPairly, or something is hard to read or operate, tell us by e-mail at admin@carpairly.tech or on the contact page. Say which page it was, what went wrong and, if you can, which device and assistive technology you used. We reply within 5 working days, and we will work on a fix.