Accessibility statement

1. Scope

This statement applies to this website (tuppence.ai), operated by [Company legal name] Ltd. The Tuppence dashboard, hosted checkout and pay pages, and the iPhone app (beta) are covered where stated. It does not cover third-party websites we link to, or Stripe’s own card and identity verification fields.

2. Our commitment

We aim to meet the Web Content Accessibility Guidelines (WCAG) version 2.2 at level AA. We have not yet had an independent audit, so we do not claim full conformance. We currently assess our status as [partially conformant — to be confirmed by audit].

3. What you can expect

On this website you should be able to:

• navigate using only a keyboard, with a visible focus indicator;
• use the “Skip to content” link at the top of every page to jump past the navigation;
• find your way using proper headings, landmarks and breadcrumbs, which work with screen readers;
• read text in our brand colours, which have been chosen for sufficient contrast against their backgrounds [contrast ratios to be verified by audit];
• understand images: informative images have text alternatives, and decorative illustrations and product mock-ups are hidden from screen readers, with their meaning described in the surrounding text;
• turn off animations — the site respects the “reduce motion” setting on your device;
• zoom in, and use the site on a small screen, without content being lost;
• fill in forms, such as the waitlist, that have visible labels.

The site is a lightweight static website. It uses no cookies, analytics or third-party scripts.

4. Known limitations

We know some parts may not yet be fully accessible:

• Code examples on product pages are presented in tabbed panels. [Confirm screen reader behaviour through testing.]
• The dashboard, pay pages and iPhone app (beta) have not yet been audited against WCAG 2.2 AA. [Audit results and target dates to be added.]
• Card details are entered into Stripe’s own fields, and identity verification uses Stripe Identity. We rely on Stripe for the accessibility of those components.
• [Further issues identified by audit.]

5. Alternative formats

If you need information on this website in a different format — such as accessible PDF, large print, easy read or audio — email [accessibility email address] or use our contact page. Tell us:

• the page address or document name;
• the format you need;
• the assistive technology you use, if relevant.

We will reply within [five working days] and let you know how long it will take to provide the information.

6. Reporting problems

If you find a problem not listed above, or think we are not meeting accessibility requirements, email [accessibility email address], use “Get help” in the dashboard or iPhone app, or use our contact page. Where possible, please include the page, what you were trying to do, and the device, browser and assistive technology you were using.

7. If you are not satisfied

If you are unhappy with our response, you can make a formal complaint using our complaints procedure. You can also contact the Equality Advisory and Support Service for independent advice about your rights.

8. How we test

[Describe how we test — for example, manual checks with a keyboard, zoom and reduce motion, automated checks and screen reader testing.] No full audit has been carried out yet; [the first audit is planned for [date] by [internal team / external auditor]] against WCAG 2.2 AA. We will review this statement at least every [12 months] and after significant changes.

9. Technical information

This website is built with HTML and CSS, with a small amount of JavaScript for things like tabs and menus. It is designed to work with current versions of major browsers and assistive technologies. [List tested combinations, e.g. VoiceOver with Safari, NVDA with Firefox.]