Statement prepared: 7 November 2026. Next review: within 12 months, or sooner after a major redesign.
The short version
- We want everyone to be able to use The Prompt Index, including people who use screen readers, keyboard-only navigation, magnification or voice control.
- Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, level AA.
- We have not yet completed a full accessibility audit, so we cannot yet say the site meets that standard. Some parts probably do not.
- If something gets in your way, tell us and we will help. Contact: steve@thepromptindex.com.
1. Our commitment
The Prompt Index is a small, one-person business. Under the Equality Act 2010 we have a duty to make reasonable adjustments so that disabled people are not put at a disadvantage when using our service, and we take that duty seriously. We use WCAG 2.2 level AA as our benchmark for new and rebuilt pages.
2. How accessible the site is today
We have not yet carried out a full audit against WCAG 2.2, either ourselves or with an independent tester. This is an honest description based on what we know, not a certification.
Things we have tried to do:
- use real text rather than images of text for content, with text alternatives on the main logos and icons;
- let pages zoom and reflow on mobile screens;
- use labelled buttons and form fields on our newer tools and pages.
Problems we know about or expect:
- Some older pages and blog posts use colour combinations that may not have enough contrast, and decorative animated backgrounds.
- Some menus, pop-ups and modal windows (for example dropdown navigation and some tool dialogs) may not be fully usable with a keyboard or announced correctly by screen readers.
- Some AI tools show results that change on screen without telling screen-reader users.
- Some images in the image prompt database, and some AI-generated images, have no useful text description.
- Some PDFs, slides and documents our tools produce may not be fully accessible, depending on the content you create.
- Third-party parts we don't fully control (for example Stripe's checkout, Google sign-in and embedded forms) have their own accessibility levels.
3. What we are doing about it
- We are checking the most important journeys first: signing up and logging in, the cookie banner, choosing and paying for a plan, cancelling, reporting content, making a complaint and the most used tools.
- New and rebuilt pages are designed with WCAG 2.2 AA in mind.
- We will update this statement with the results, including any problems we cannot fix straight away and why.
- Signing in or signing up with Google takes two clicks: our own "Sign in with Google" button loads Google's sign-in script, then you press Google's button. This avoids loading anything from Google before you choose it. Signing in with email and password is always available as an alternative.
4. Getting help and asking for adjustments
If you have trouble using any part of the site, or need information in a different format, contact us:
Tell us the page address (URL), what you were trying to do, and what got in the way. If it would help, also tell us the assistive technology you use. We will reply within 2 working days. Where we can, we will offer a reasonable alternative while we fix the problem: for example, we can help you with a task by email, send information in another format, or manage your subscription or cancellation for you.
5. If you are not happy with our response
Please use our complaints process. If you are still not satisfied, you can contact the Equality Advisory and Support Service (EASS) in Great Britain, or the Equality Commission for Northern Ireland.
Last reviewed 7 November 2026