Accessibility

Effective August 27, 2026.

Pairly is built to be usable by as many people as possible. This page says what is in place, what is not finished, and how to tell us when something is in your way.

What we aim at

The Web Content Accessibility Guidelines, version 2.2, at level AA. That is the standard courts and regulators in the United States point at, and it is the one we build against.

What is in place today

• Everything works with a keyboard alone, and focus is always visible rather than styled away.
• Semantic headings, labelled form fields, and error messages tied to the field they belong to, so a screen reader announces them.
• Text contrast checked against AA, including the quieter greys used for secondary text.
• Touch targets sized for a thumb rather than a mouse pointer, because this product is mostly used on a phone.
• Animation that respects the reduced motion setting in your operating system. Turn it on and the movement stops.
• Layouts that reflow rather than break when text is enlarged or the window is narrow, with no horizontal scrolling of the page.
• Information never carried by colour alone. Where a colour marks whose money something is, a name or a label says the same thing.
• Meaningful images described, and decorative ones hidden from screen readers rather than read out as filenames.

What is not finished

• Pairly has not been through a formal third-party accessibility audit. The checks above are our own.
• Charts show trends visually with the same figures available as text nearby, but they are not individually navigable by keyboard.
• We have not tested with every combination of screen reader and browser, and the gaps we do not know about are the ones we most want to hear about.

Telling us something is wrong

If any part of Pairly is difficult or impossible for you to use, write to us through the contact form and say what you were trying to do, what got in the way, and what you use to browse if you are happy to say. It reaches the people who build the product and every message gets a reply within one business day.

An accessibility problem is treated as a bug rather than a request. If we cannot fix it quickly we will tell you what we are doing instead and how you can get the same thing done in the meantime.