Accessibility

Accessibility statement

We aim at WCAG 2.2 level AA. This page says what we have actually checked, what we have not, and how to tell us when something gets in your way.

Last reviewed 2026-11-03.

What we have checked

Colour contrast: Every text colour pair in the design system is checked against the WCAG AA ratio for its size by an automated test that runs with the rest of the suite. Two colours are marked as unusable for small text and are only used for focus rings, lines and large icons.
Charts and figures: Every chart carries a text alternative naming its numbers and a table with the same values, so a chart is never the only way to read a figure.
Navigation without a pointer or JavaScript: The site menus open on keyboard focus as well as hover, and their links are present in the HTML with JavaScript switched off. The phone menu shows the same groups.
Meaning beyond colour: Statuses carry a word as well as a colour; a coloured dot is never the only signal.
Forms: Every field has a visible label, and validation errors are written in text next to the field rather than by colour alone.

What we have not checked

Listed because a statement that only says what works is not a statement.

No external audit: No independent accessibility audit has been carried out, and we publish no conformance claim or VPAT.
Screen readers: We have not tested with JAWS, NVDA or VoiceOver. Structure and text alternatives are written with them in mind, but that is not the same as testing.
Zoom and reflow at extremes: Pages are built to work down to a phone width, but we have not checked 400% zoom or 320 CSS pixels systematically.
Exported documents: The DOCX and PDF documents the product produces have not been checked for tagged-PDF accessibility.
Third-party screens: The payment form is Stripe's own component, and its accessibility is theirs.

Telling us about a barrier

Write to hello@clausebench.com with the page and what happened. We answer within five working days, say whether we can fix it and when, and update this page when we do.

REALTY.TM GROUP sp. z o.o. · Company details · Trust centre

What we have checked

Colour contrast

Every text colour pair in the design system is checked against the WCAG AA ratio for its size by an automated test that runs with the rest of the suite. Two colours are marked as unusable for small text and are only used for focus rings, lines and large icons.

Charts and figures

Every chart carries a text alternative naming its numbers and a table with the same values, so a chart is never the only way to read a figure.

Navigation without a pointer or JavaScript

The site menus open on keyboard focus as well as hover, and their links are present in the HTML with JavaScript switched off. The phone menu shows the same groups.

Meaning beyond colour

Statuses carry a word as well as a colour; a coloured dot is never the only signal.

Forms

Every field has a visible label, and validation errors are written in text next to the field rather than by colour alone.

What we have not checked

Listed because a statement that only says what works is not a statement.

No external audit

No independent accessibility audit has been carried out, and we publish no conformance claim or VPAT.

Screen readers

We have not tested with JAWS, NVDA or VoiceOver. Structure and text alternatives are written with them in mind, but that is not the same as testing.

Zoom and reflow at extremes

Pages are built to work down to a phone width, but we have not checked 400% zoom or 320 CSS pixels systematically.

Exported documents

The DOCX and PDF documents the product produces have not been checked for tagged-PDF accessibility.

Third-party screens

The payment form is Stripe's own component, and its accessibility is theirs.