Accessibility statement

The standard

We aim for full conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, which is the standard the European Accessibility Act enforces through EN 301 549 and the one Brazil's Lei Brasileira de Inclusão points to. That covers the public site, the signed-in product and the emails we send. Where we can meet a level AAA criterion at no cost to anyone, we do.

Where we stand

As of the date above, our automated checks find no WCAG 2.2 A or AA violations on the public pages, at phone and desktop widths and in both color themes; the signed-in product passes the same checks when we run them with a test account. Automated testing cannot judge everything the standard asks — keyboard operation, focus order, and how a screen reader announces each control — and a full manual review of those across the whole product is not part of our routine checks, so we do not claim full conformance. If something does not work for you, the section below is the fastest way to get it fixed.

How we check

Whenever a change touches what the public pages show, our automated build runs two checks on them: an axe-core scan against the WCAG 2.2 A and AA rules, at phone width in light and dark and at desktop width, and an audit of the rendered pages for contrast, overflow and clipping at desktop in both themes and at phone width. The signed-in product gets the same two checks only when we run them by hand with a test account. No automated step tests keyboard operation or screen readers. A failing check is reported on the change; releases are deployed by hand and are not blocked by it automatically, so a failure is something we fix rather than a gate.

Parts of the service provided by others

Three steps use another company's interface. Each maker builds to the same standard and says so in its own words; we test them as they appear on our pages, we cannot alter what is inside them, and for each there is a way around it if it fails you. They are not shortfalls of ours — they are another company's work, held to the same bar.

• The bot check on our sign-in, sign-up and contact forms is Cloudflare Turnstile. Cloudflare states it is built to WCAG 2.2 — AAA for contrast and readability, with every interactive element focusable and announced to screen readers — and redesigned it for keyboard and screen-reader users in February 2026. It is usually invisible. If it ever blocks you, write to us and we will help you directly.
• Payment is Stripe Checkout, a page Stripe hosts. Stripe states its Checkout pages are structured and labeled for screen readers and built to WCAG 2.1; its conformance report is available from Stripe on request. If Checkout does not work for you, write to us and we will complete the purchase another way.
• Signing in with Google is Google's page — part of the Google Account system every Google product uses, including the ones whose conformance reports Google publishes, Gmail among them. You never need it: signing in with email and password is ours, and everything on this page applies to it.

What each of them publishes: Cloudflare · Stripe · Google

Tell us

If any part of CloseRev is hard or impossible for you to use, write to accessibility@closerev.com. Say what you were trying to do, which page, and what happened; if you use assistive technology, say which. We answer within five working days, and fixes go to the front of the queue. You do not need an account to ask.

If we do not answer

In the European Union you may raise an unresolved complaint with the market surveillance authority for accessibility in your member state; in Portugal that is ANACOM. In Brazil, with the Ministério Público or Procon in your state. We would much rather hear from you first.