Accessibility

Keyring is designed to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. It hasn’t been audited against them yet, so this page doesn’t claim that it does. It says what is built in, what is known not to be right, and how to ask for something in a way that works for you.

• Its colours are chosen so that text has a contrast of at least 4.5 to 1 in both the light and the dark theme, and control borders and the focus ring at least 3 to 1.
• Every link, button and field can be reached and used with a keyboard, and shows a clear ring when it has focus.
• A step’s state is never shown by colour alone: waiting and blocked always carry a word and an icon.
• The circle that shows a sale’s progress has a spoken description, such as “14 of 24 milestones done”.
• With reduced motion turned on in your device’s settings, nothing moves on its own.
• Pages are built to work at phone width without scrolling sideways.
• Keyring follows your device’s light or dark setting, and you can choose either.
• Buttons say exactly what they do, and error messages say how to put things right.

• Keyring hasn’t been tested with the full range of screen readers and voice control software.
• Documents on a sale, such as a contract pack, searches or a survey, are made by others and may not be accessible. Ask the person who uploaded one for it in another format.
• On a phone, the bar at the bottom of the screen shows the first four places in Keyring; the others are reached from the pages that link to them.

If something in Keyring doesn’t work for you, or you need information in another format, such as large print or a call instead of an email, tell Keyring with the form on Your data, or email support@usekeyring.co.uk. Say what you were trying to do, and Keyring will answer.

If you’re not happy with the answer, the Equality Advisory and Support Service can help: equalityadvisoryservice.com.

Keyring’s design rules are written down and its pages are tested at phone width in its automated tests. An independent audit against WCAG 2.2 AA is planned, and this page will be updated with what it finds.