Accessibility

1. Our commitment

People back tabletop projects using screen readers, keyboard-only navigation, magnification, and voice control. Confirming a pledge you've already paid for should not require a mouse, a steady hand, or good eyesight.

We're aiming for WCAG 2.1 Level AA across the pages that matter most: finding your pledge, confirming your address, choosing add-ons, paying, and reaching your downloads.

2. Where we actually are

Being straight with you: this site is partially conformant with WCAG 2.1 Level AA. That means we've built to the standard deliberately but have not yet completed a full independent audit, so we can't claim the certificate.

What we have done:

• Every form field has a real, programmatically associated label.
• The whole pledge flow can be completed by keyboard, with visible focus indicators.
• Text and interface contrast is checked against the AA thresholds.
• Images that carry meaning have alternative text; decorative ones are hidden from screen readers.
• Headings are properly ordered so a screen reader can navigate by structure.
• Nothing depends on colour alone to make sense.
• No CAPTCHA anywhere in the buy path.
• No time limits on completing your pledge — take as long as you need.
• No auto-playing audio or video, and motion respects your reduced-motion setting.

3. Known gaps we're working on

We'd rather list these than pretend they don't exist. If one of them is what's blocking you, email us and it moves to the top of the queue.

• No independent audit yet. Scheduled. Until it's done, treat our conformance claim as our own assessment rather than a verified one.
• Creator admin tools. Our effort has gone into the backer-facing pages first. The campaign management side, used by creators rather than backers, has had less accessibility attention. If you're a creator who needs it, tell us and we'll prioritise it.
• Creator-supplied content. Reward images and descriptions come from creators. We require alternative text but can't guarantee every creator writes a good one. Tell us about a bad one and we'll fix it.
• Third-party payment pages. Card payment happens on Stripe's checkout, which we don't control. Stripe publishes its own accessibility commitments. If you can't complete a payment there, we can take it another way — just ask.

4. Why there's no accessibility widget

You won't find a floating accessibility button offering high-contrast mode and bigger text. Those overlays are widely criticised by disabled users and by the screen reader community for interfering with the assistive technology people already have set up properly.

We'd rather fix the underlying pages so your own tools work, than bolt a widget on top and call it solved.

5. How we test

• Keyboard-only walkthroughs of the full pledge flow before release.
• Screen reader checks on the confirm and payment steps.
• Automated contrast and markup checks.
• Real reports from people using the site, which are the most useful of the four.

6. Telling us about a problem

Email james@storyforgerpg.com with the subject line Accessibility. Useful detail if you have it: the page, what you were trying to do, and what browser or assistive technology you use. None of it is required — a one-line "I can't get past the address screen with a screen reader" is enough to act on.

We aim to acknowledge within 2 working days and give you a fix or a workaround within 10. Anything blocking access to something you've paid for, we handle immediately by hand.

7. Standards and scope

This statement covers storyforgerpg.com and the pledge pages hosted on it. It was prepared on 26 July 2026 using our own evaluation against WCAG 2.1 Level AA, and we review it whenever we make a significant change to the pledge flow.