Accessibility

Last updated: 16 September 2026

We want TAPPI to work for everyone who uses it, including the customer standing at a counter tapping a chip. This page says what we do, what we know falls short, and how to tell us when we get it wrong.

What we are aiming for

We build towards the Web Content Accessibility Guidelines 2.2, Level AA. We have not had an independent accessibility audit, so we do not claim to conform to it. Saying "WCAG 2.2 AA compliant" without a test behind it is a claim we are not willing to make.

What is in place

semantic HTML, so headings, lists, tables and landmarks read correctly in a screen reader;
keyboard operation for menus, forms, dialogs and the cookie banner, with visible focus;
text alternatives on meaningful images, and decorative images marked as decorative;
a layout that reflows to a phone at 390px wide without a horizontal scroll, and text that survives being zoomed;
a light and a dark theme that both follow your system setting, with colour contrast chosen deliberately rather than inherited;
colour never used as the only way to convey a status — labels and icons carry it too;
form fields with real labels, errors described in text, and a summary at the top of a failed form.

Known issues

No independent audit. Everything above is our own testing. There will be problems we have not found.
Maps. The map views in the dashboard are visual. The same information is available as a list, but the map itself is not usable without sight.
Charts. Analytics charts convey trends visually. The underlying numbers are shown alongside, but the charts do not expose a full text alternative.
Wallet passes. Once a card is in Apple Wallet or Google Wallet, its accessibility is controlled by those apps, not by us. We choose contrast carefully when a card is designed, but we cannot change how the wallet renders it.
Tapping a chip needs a phone. NFC requires holding a device to a physical spot. Every TAPPI chip is also reachable by QR code and by a plain link, which can be typed or shared.
Third-party embeds. The payment step is rendered by Stripe and the anti-bot check by Cloudflare; their accessibility is theirs.

Tell us about a barrier

Email hello@thetappi.com with the page or screen, what you were trying to do, and what got in the way. We aim to reply within 5 business days. If you need anything from this site in another format, ask and we will find a way to give it to you.

If we have not fixed something and you think we should have, say so in the same thread — we would rather hear it from you than not hear it.

What is in place

semantic HTML, so headings, lists, tables and landmarks read correctly in a screen reader;
keyboard operation for menus, forms, dialogs and the cookie banner, with visible focus;
text alternatives on meaningful images, and decorative images marked as decorative;
a layout that reflows to a phone at 390px wide without a horizontal scroll, and text that survives being zoomed;
a light and a dark theme that both follow your system setting, with colour contrast chosen deliberately rather than inherited;
colour never used as the only way to convey a status — labels and icons carry it too;
form fields with real labels, errors described in text, and a summary at the top of a failed form.

Known issues

No independent audit. Everything above is our own testing. There will be problems we have not found.
Maps. The map views in the dashboard are visual. The same information is available as a list, but the map itself is not usable without sight.
Charts. Analytics charts convey trends visually. The underlying numbers are shown alongside, but the charts do not expose a full text alternative.
Wallet passes. Once a card is in Apple Wallet or Google Wallet, its accessibility is controlled by those apps, not by us. We choose contrast carefully when a card is designed, but we cannot change how the wallet renders it.
Tapping a chip needs a phone. NFC requires holding a device to a physical spot. Every TAPPI chip is also reachable by QR code and by a plain link, which can be typed or shared.
Third-party embeds. The payment step is rendered by Stripe and the anti-bot check by Cloudflare; their accessibility is theirs.

Tell us about a barrier

If we have not fixed something and you think we should have, say so in the same thread — we would rather hear it from you than not hear it.