Accessibility

This site aims for WCAG 2.2 level AA. It is built so the tools you already have — screen readers, browser zoom, OS display settings, switch devices — work with it directly. There is no separate "accessible mode" to lag behind the main site.

What this site does

• Semantic structure throughout: landmarks, one <h1> per page, ordered headings, labeled form fields.
• Full keyboard access, with a visible focus indicator and a "Skip to content" link at the top of every page.
• Text size and contrast controls in the header (the Aa button): text up to 125% and a high-contrast palette. Your choice is remembered on this device. The layout is built from relative units, so large text reflows instead of breaking — including on a phone.
• Respects your system settings: reduced motion disables animations; the site also works with your browser’s own zoom and font settings.
• Text is real text (not images of text), links in paragraphs are underlined, and nothing meaningful is conveyed by color alone.

Known limits

• The games themselves run on an HTML <canvas>, which is inherently visual. Each one documents its keyboard controls and offers remappable keys and pause, but they are not screen-reader playable.
• The FortKnight and ForkKnife planners render most of their pages in the browser from your saved profile, so their interactive views need JavaScript; the prerendered fallback is limited.

How it stays this way

Every change to the site is checked before it can go live: an automated axe-core audit of every page (WCAG 2.0/2.2 A and AA), static HTML checks in the build, and a manual keyboard / zoom review for layout changes. A regression blocks the deploy.

Report a barrier

If something on this site doesn’t work for you, that’s a bug — please report it via the issue tracker and it will be treated as a defect, not a feature request.