Accessibility

Our commitment

We want as many people as possible to be able to use Fortune Cookie Generator — including people who browse with a screen reader, navigate by keyboard, need larger text or more contrast, or prefer less motion on screen.

This page explains what we have built to support that, how we check it, what we know is not perfect yet, and how to tell us when something gets in your way.

The standard we aim for

Our goal is to align with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA wherever practical.

We are not claiming full conformance, and we have not been certified by anyone. Some parts of the site may not yet fully meet that standard, and automated testing only catches part of what matters. We would rather say that plainly than publish a promise we cannot stand behind.

What we do to support accessibility

• The site is built from standard HTML landmarks and headings, so assistive technology can move through it in a predictable order. Every page has one main heading and a “skip to content” link.
• Everything works with a keyboard alone. The category and mode selectors are native radio groups, so arrow keys behave the way you already expect them to.
• Focus indicators are visible and high contrast, so you can always tell where you are on the page.
• New fortunes, copied text, and saved favourites are announced politely to screen readers instead of changing silently.
• The FAQ uses native expand and collapse elements, so it still works if JavaScript does not load.
• Text and background colour pairs are chosen to meet or exceed a 4.5:1 contrast ratio, and most exceed 6:1.
• Animation runs only when your system is not set to reduce motion. The fortune is always real text on the page, never something you have to wait for an animation to reveal.
• The fortune is in the page HTML itself, so it is readable before — and without — JavaScript.
• We do not use an accessibility overlay or widget. Those tools frequently interfere with the assistive technology you already use and trust, and they tend to paper over problems rather than fix them. We would rather correct the underlying markup.

How we check

• Automated checks using axe-core, covering the WCAG 2.0, 2.1, and 2.2 rules at Levels A and AA. These run against the home page, contact page, privacy policy, and terms, and also against the generator after it has been used. As of the date at the top of this page, they report no violations.
• These checks are part of our automated test suite, so a change that breaks something machine-detectable shows up during development rather than after it ships.
• Hands-on review of keyboard navigation, heading structure, and focus order.

An honest caveat about all of that: automated tools catch only a portion of real accessibility problems — commonly estimated at around a third. The rest needs human judgement, and some of it needs people who actually use assistive technology day to day. We have not commissioned an independent third-party audit.

Known limitations, and what to do instead

These are the gaps we know about today. If you hit something that is not listed here, we would genuinely like to know.

• “Save image” produces a picture of your fortune, and the words inside it are part of the image, so a screen reader cannot read them. The same fortune is always available as selectable text on the page, and “Copy Fortune” puts that text straight on your clipboard.
• The contact form includes a Cloudflare Turnstile check to keep automated spam out. It is built to be accessible, but it is a third-party component we do not control. If it gets in your way, email us directly instead — it reaches exactly the same place.
• We have not yet completed formal testing across every combination of screen reader and browser. If something behaves strangely in yours, telling us which ones you use makes it much easier to fix.

What it should work with

The site is built on standard HTML rather than anything exotic, so it should work with current versions of the major browsers — Chrome, Edge, Firefox, and Safari — and with the assistive technology that works alongside them. It needs no plugin or extension, and the core of it works with JavaScript switched off.

Our automated testing runs in a Chromium-based browser. That is a real limit on what we have verified, which is part of why reports from people using other setups are useful to us.

Tell us when something is wrong

The most direct route is email: hello@fortunecookiegenerator.app. You can also use the contact form and choose “Accessibility issue” as the topic.

You do not need an account to report a problem. There are no accounts on this site at all, and there is nothing to sign up for.

If you can include the page you were on, what you were trying to do, and which browser or assistive technology you use, that helps us reproduce the problem quickly. If you do not have those details to hand, send the message anyway — a rough description is far better than nothing.

What happens after you write to us

We read every message and aim to reply within about a week. If a fix is going to take longer than that, we will tell you what we are doing about it and roughly when to expect it, rather than going quiet.

If something is stopping you from doing what you came here to do, say so in the message and we will treat it as urgent.

This is ongoing

Accessibility is not a job that gets finished once. Our automated checks run as part of the test suite so detectable regressions surface early, and we revisit this page whenever the site changes in a way that affects it. The date at the top tells you when it was last reviewed.