Accessibility

The standard we aim for

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — the benchmark widely used for accessible websites and apps in the UK. Peamo is a young product in active development and in a private beta, so it is a work in progress: large parts of the app are built to this standard, and we are actively bringing the remaining areas into line. We have not yet completed a formal, independently verified conformance review, so we describe our progress honestly rather than publishing a conformance level we have not confirmed.

What’s in place today

Accessibility is something we design for as we build, not a bolt-on. Across Peamo you should find:

• Keyboard access.You can move through the app with a keyboard. A “Skip to main content” link appears when you start tabbing on any page, and focused controls show a clear, consistent focus outline.
• Screen-reader structure. Pages use proper landmarks (header, navigation, main, footer), a single main heading with a logical heading order, and real lists and definition lists — so assistive technology can announce and jump around the page sensibly.
• Labelled forms with clear errors. Form fields have associated labels, and validation messages are announced to assistive technology rather than relying on colour or position alone.
• Reduced motion. If your device is set to reduce motion, Peamo honours that — animated backgrounds, count-ups, and loading effects are calmed or removed.
• Light and dark themes. Peamo offers both, with an in-app toggle, and text colours are chosen for readable contrast in each.
• Colour is never the only signal. Where colour conveys meaning — such as how soon a renewal is due — the same information is always spelled out in text as well.
• Text, images, and zoom. Decorative images are hidden from assistive technology and meaningful ones are described; the layout is mobile-first and reflows when you zoom, and form controls avoid the unwanted zoom-on-focus some phones apply to small text.
• Language. Pages declare their language so screen readers pronounce content correctly.

Known limitations we’re working on

We’d rather be upfront than overclaim. From our own review, these are the main areas not yet fully at WCAG 2.1 AA, and they’re on our list to fix:

• Pop-up menus and keyboard navigation. Some menus can be opened, used, and closed with Tab and Escape, but don’t yet support full arrow-key movement between items.
• A few contrast and labelling details. A small number of elements — including one green action button and a couple of section labels — are being brought fully up to the AA contrast and labelling bar.
• Touch-target size.A few buttons and toggles are a little smaller than the comfortable 44 pixel target size we’re moving towards, though they remain usable.

This list reflects what we currently know; it isn’t necessarily complete. If you hit a barrier that isn’t mentioned here, please tell us — see below.

Reporting an accessibility problem

If any part of Peamo is hard to use with the tools or settings you rely on, we want to hear about it. Email support@peamo.co.uk and, if you can, include:

• the page or part of the app where it happened (a link or screenshot helps);
• what you were trying to do, and what got in the way;
• the device, browser, and any assistive technology you were using (for example, a particular screen reader or browser zoom level).

We read every message that comes in and will aim to get back to you, and where we can, offer the information or function you needed in another way while we put a fix in place.

About this statement

Peamo is operated by Arcshore Limited. We’ll keep this statement up to date as the app evolves and as we close the gaps above. For anything about accessibility, or about your data and privacy, email support@peamo.co.uk. You can also read our Privacy Policy and data & security pages.