Legal

Accessibility Statement

Last updated 7 September 2026

This statement applies to the ClubKeeper web platform at www.clubkeeperapp.com, including the club pages your club uses day to day. It does not cover the ClubKeeper Android app, which has not yet been assessed.

What we’re aiming for

Running a grassroots club is volunteer work, and the people doing it are every kind of person. A treasurer with low vision, a parent using a phone one-handed on a touchline in the rain, a coach who navigates by keyboard — none of them should be shut out of the club they give their time to. Where ClubKeeper is the only way to register a child, pay subs or reply to a fixture, anything we get wrong stops being an inconvenience and starts being an exclusion.

We aim to meet WCAG 2.2 level AA. We are not claiming to have got there yet.

How accessible this platform is

ClubKeeper is partially conformant with WCAG 2.2 level AA. Partially conformant means most of the standard is met, and the parts we know are not met are listed below.

What currently works:

• Every page can be operated by keyboard alone, and every page marks out its main content region. On pages with the club menu, a “skip to main content” link is the first thing you reach; the signed-out pages (sign in, sign up, joining links) have no menu to skip past, so they don’t carry one.
• Focus is always visible — a clear outline follows the keyboard, and never disappears behind a hover style.
• Text and background colours meet the AA contrast minimum in both light and dark themes. This is checked automatically before every release, not by eye.
• Every button, link, form field and dropdown has a name a screen reader can announce.
• The interface respects your system settings for dark mode and for reduced motion — if you have animation turned down, we turn it down too.
• Nothing depends on colour alone: a status is always written out as well as tinted, and a link inside a sentence is underlined rather than only recoloured.
• Whoever posts a photo to the club noticeboard can describe it, and that description is what a screen reader reads out.

What we know isn’t accessible yet

These are the gaps we are aware of. Where a gap affects you, please tell us — knowing which of these actually gets in someone’s way is what decides the order we fix them in.

• We have not tested with a screen reader. Our checks so far are automated scans, calculated colour contrast, and keyboard testing. Those catch a great deal, but they are not the same as somebody listening to the app. This is the biggest known gap and the next thing on our list.
• Older noticeboard photos have no description. Descriptions can be added from today, but every photo posted before that has none, and nobody can write one for a photo they didn’t take. Those announce as “photo posted by [name], no description added”, so you at least know a photo is there and who to ask. Descriptions are also optional, so a newer photo may not have one either. Photos sent in club chat are announced as a photo and who sent it, but cannot be described.
• The Android app has not been assessed at all. Everything on this page refers to the website. If you use the app with TalkBack and hit a problem, we would especially like to hear about it.
• Some data tables have not been tested with assistive technology. Financial and register tables use proper heading markup, but we have not confirmed how they are read out in practice.

Content that isn’t ours

Some of what you see in ClubKeeper is put there by your club rather than by us, and we can’t guarantee it. That includes documents a club uploads to its own library — constitutions, minutes, risk assessments and similar, often scanned PDFs that were never made accessible. If you need something from a club document and can’t get at it, ask your club directly: they hold the original and can give it to you another way.

Card payments are handled on Stripe’s own pages, and the GIF picker in club chat uses Giphy’s search. Both are outside our control and have their own accessibility statements.

Getting the same thing another way

If part of ClubKeeper doesn’t work for you, you should not have to go without what it does. Two things are always available:

• Ask us. Tell us what you were trying to do and we will get you the information or complete the action for you while we fix the underlying problem.
• Ask your club. Club officials can enter and retrieve almost everything on a member’s behalf — register a player, record a payment, pass on a fixture. You are not required to use the app to be part of your club.

Telling us about a problem

We want to hear about anything that doesn’t work for you, whether or not it is on the list above. You do not need to know the technical cause or use any particular words — “I can’t get the subs page to work with my magnifier” is a perfect report.

• Email jason@clubkeeperapp.com. This works for everyone, signed in or not, and you don’t need an account.
• If you are one of your club’s administrators, you can also use Contact support on your Settings page. That form is only available to club administrators — for everyone else, email is the route, and it reaches the same place.

We aim to reply within 5 working days, and will tell you honestly whether we can fix it quickly, whether it will take longer, or whether we can’t — rather than leaving you waiting to find out.

That is longer than the one working day we commit to for support and for anything affecting money, and the difference is deliberate. An accessibility problem usually has to be reproduced on the device it happened on before there is anything useful to say, and we would rather take five days and tell you what we are actually going to do than reply in one to say we have received it.

If you’re not happy with our response

Service providers in the UK have a duty under the Equality Act 2010 to make reasonable adjustments for disabled people. If you contact us about an accessibility problem and are not satisfied with how we respond, the Equality Advisory and Support Service (EASS) gives free, independent advice: equalityadvisoryservice.com. In Northern Ireland, contact the Equality Commission for Northern Ireland instead.

How we tested this platform

Last tested on 21 August 2026, by ClubKeeper. The testing covered:

• Automated scanning with axe-core against the WCAG 2.0, 2.1 and 2.2 A and AA rule sets, run over the journeys that matter most: signing in with two-factor authentication, replying to a fixture, viewing and paying subs, raising a safeguarding concern, and safeguarding casework.
• Colour contrast calculated for every text and background combination across all four theme states — light, dark, and each explicitly chosen. This now runs automatically before every release, so a colour that fails cannot ship.
• Keyboard testing of the same journeys: tab order, whether every control can be reached and named, and whether anything traps focus.
• Accessibility rules added to the code checks that run on every change, so specific mistakes cannot come back unnoticed.

Testing did not include a screen reader, voice control, or the Android app. We would rather say that plainly than let a scan stand in for it.

What we’re doing next

• Testing the main journeys with a screen reader, and fixing what that finds.
• Assessing the Android app.
• Re-testing whenever a significant part of the platform changes, and updating this page when it does.

This statement was prepared on 21 August 2026 and reflects testing carried out on that date.