Accessibility

What I'm aiming for

My goal is for this site to meet WCAG 2.1 Level AA — the standard most commonly used to judge whether a website is usable by people with disabilities. I don't claim to be fully there, but I check it and I fix what I find.

What's been done

• Every page has a "skip to main content" link and a marked main content area.
• All images have text descriptions for screen readers.
• Text and interface colours are checked against the required contrast levels.
• The site honours your system's "reduce motion" setting — animations stop if you've asked your device to reduce them.
• Keyboard navigation shows a clear focus outline, and the chat assistant can be opened, used, and closed entirely by keyboard (Escape closes it).
• Form fields have proper labels rather than relying on placeholder hint text.
• Pinch-to-zoom is enabled everywhere.

Known limitations — the honest part

Some things on this site genuinely can't be made fully accessible, and I'd rather say so plainly than pretend otherwise.

🕹️ The Arcade

The games on the Arcade page are real, decades-old console games running in an emulator. They render to a single graphics canvas with no text a screen reader can read, and they need fast two-handed input. There is no available way to make them playable without sight. They're offered as a bonus, not as core content.

📺 Pickle TV

Pickle TV streams public-domain films from the Internet Archive using their player. Captions depend on the copy the Archive holds, and I can't add captions to video I don't host.

🖥️ PickleOS 93

PickleOS is a joke desktop operating system with draggable windows and clickable icons. It's a novelty, and it's difficult to use with a screen reader. Everything meaningful inside it is also reachable as an ordinary page elsewhere on this site.

🃏 Card and board games

Solitaire and Chinese Checkers have keyboard-usable controls, but the gameplay itself is drag-and-drop on a visual board.

Run into a problem?

If any part of this site blocks you, please tell me — I'd genuinely rather hear about it and fix it. Describe what you were trying to do and what got in the way, and I'll do my best to sort it out or get you the information another way.

📧 Email me about accessibility

I read these myself, so expect a reply from an actual pickle rather than a support queue.