Accessibility Statement

1. Our accessibility target

We aim to make Perkstar-hosted web surfaces conform to WCAG 2.2 level AA where reasonably achievable. This includes the Operator dashboard, scanner surfaces, customer sign-up pages, wallet-pass preference pages, customer privacy pages and public legal pages.

Accessibility is treated as part of product quality, not as a separate afterthought. New product work should preserve keyboard access, visible focus, readable contrast, meaningful labels, responsive layouts and understandable error messages.

2. What should work well

We design Perkstar so users should be able to:

• navigate core pages with a keyboard;
• see visible focus states on interactive controls;
• use pages on mobile, tablet and desktop without horizontal overflow in normal use;
• read page titles, headings and labels that describe the page or control;
• use form validation that explains what needs fixing;
• zoom text and use browser zoom without losing core functionality;
• use customer-facing sign-up and preference pages without relying on colour alone; and
• access public legal pages in a simple, readable document layout.

3. Known limitations

Perkstar is a fast-moving product, and some areas may still need improvement. Known or likely limitations include:

• complex data tables may be easier to use on desktop than mobile;
• some rich card-design controls, image crop tools, QR/scan tools and visual previews may have limited screen-reader usefulness because they are inherently visual;
• third-party embedded or redirected services, including Stripe, Apple Wallet, Google Wallet and external POS/booking partners, are controlled by those providers;
• uploaded operator content, images, logos and marketing copy may not always be accessible unless the Operator creates them accessibly; and
• older internal admin pages may not yet meet the same standard as newer production operator/customer surfaces.

We prioritise fixes that block account access, customer enrolment, payment, wallet installation, scanner use, privacy controls or legal information.

4. Feedback and support

If you find an accessibility problem, need information in another format, or cannot complete a task, email accessibility@perkstar.co.uk or hello@perkstar.co.uk.

Please include:

• the page or URL;
• what you were trying to do;
• the device, browser and assistive technology you used, if relevant; and
• the format or support you need.

We aim to acknowledge accessibility requests within 5 business days and provide a practical response or workaround as quickly as reasonably possible.

5. Operator responsibilities

Operators control some content shown to their own customers, including business names, logos, card images, reward names, form questions, marketing copy and imported customer data. Operators should make that content accessible and should not use Perkstar to publish content that they could not lawfully or accessibly provide to their own customers.

Perkstar provides the platform controls, but an Operator remains responsible for the accessibility and legality of its own programme content.

6. How we test and improve

Our accessibility work combines product design review, responsive checks, keyboard checks, semantic HTML patterns, component reuse and issue-led remediation. We also treat user feedback and support reports as accessibility signals.

Before launch-critical changes, we prioritise checking the first-time onboarding flow, card creation, customer sign-up, wallet installation, scanner use, billing, privacy controls and public legal pages.

7. Review cycle

We review this statement when major product surfaces change and at least annually. The current statement was last updated on 24 June 2026.

Questions or accessibility requests: accessibility@perkstar.co.uk.