Legal

Accessibility

Last updated 22 September 2026

What we build to, what is already true, and what is not yet.

The standard we aim at

We build Ratably to meet WCAG 2.1 Level AA. We have not commissioned a third-party audit, so this is a statement of what we build to and test for, not a certification.

What is in place

• Every form control has a visible label tied to it, and error messages sit next to the field they describe rather than only at the top of a form.
• Focus is always visible, and the whole site can be operated from the keyboard.
• Body text meets AA contrast against its background in both the light and dark renderings of the page.
• Animation respects prefers-reduced-motion; nothing moves if your system asks it not to.
• The page reflows to a single column at phone width without horizontal scrolling.
• Results that update without a page load are announced to screen readers.

What is not there yet

• No independent accessibility audit has been done.
• The report PDF has not been tested with a screen reader, and is not yet tagged for accessibility.
• A scanned lease is read by sending the page images to our AI processor rather than extracted text, so quality depends on the scan: a blurry or skewed scan may read less reliably than a clean one.

If something gets in your way

Write to support@ratably.io and say what you were trying to do. We treat accessibility problems as defects, not feature requests, and we will tell you when it is fixed.

If you need a report in a different format, ask and we will produce one.