Start

Accessibility

Orrerie Pay, the checkout businesses use to take crypto, and Orrerie Merchant, their dashboard, are built to be usable by everyone. This page says what we aim for, how we check it, what we know falls short and how to tell us about a barrier.

What we aim for

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA on every page of pay.orrerie.com and merchant.orrerie.com.

How we check it

Every payer page and every dashboard screen is tested before each release in Chromium, WebKit (the engine of Safari) and Firefox, at widths from 360 to 1440 pixels, using the keyboard alone, with text enlarged to 200%, with reduced motion, and for the contrast of its text and controls. The names a screen reader reads for each control, and what it announces, are checked in the same tests.

These are our own tests. No independent body outside Orrerie has checked the service.

What we know falls short

• A QR code cannot be read aloud. Every QR code has the same address or link beside it as text, with a Copy button.
• The passkey, Face ID and fingerprint prompts are drawn by your browser or your device, not by us, and follow their accessibility settings.
• A payment window has a time limit, usually 15 minutes, because the price and the address are fixed for that time. It cannot be extended; when it ends, a new one can be started at once.
• Receipt and invoice PDFs may not read well with every screen reader. The same details are on the receipt and invoice pages as text.

Tell us about a barrier

If something on a payment page stops you, tell the business you are paying: its contact is on the page and on your receipt, and it can pass it to Orrerie from its dashboard.

If you run a business on Orrerie Merchant, use Help, then Contact support, in the dashboard, and choose the topic Something else. We answer at the email address you sign in with.

This statement was written on 20 October 2026. It is checked again with each release.