Accessibility

We want this site to work for everyone who lands on it, including people using a keyboard only, a screen reader, magnification, or a browser with animation turned off. We are aiming at WCAG 2.2 level AA.

What we have done

• Every control works from the keyboard alone, in a sensible order, with a focus indicator designed to stay visible on both the light and the dark parts of the page. A “skip to main content” link comes first.
• The page is built from real landmarks and headings, so a screen reader can navigate it by structure. The nine cookbooks in the hero are ordinary buttons with descriptive names, and the panel they open is a native dialog that traps focus, closes on Escape and returns focus where it started.
• Text contrast has been measured against the surfaces behind it and meets at least 4.5:1 for body text; the focus indicator and interface borders meet 3:1.
• A Display & accessibility panel, opened from the top of the page or the footer, lets you make the text larger, switch to higher contrast, widen line and letter spacing, underline every link, and stop all motion. Settings are saved on your device only. If your system already asks for reduced motion or more contrast, the page starts that way.
• A back-to-top button appears once you have scrolled, the email address can be copied with one click for devices with no mail app, and the sample spreads can be paged with the arrow keys. Printing the page hides the animation and opens every FAQ answer.
• The layout reflows to a single column at phone widths and at 200% zoom without horizontal scrolling, and it keeps working in Windows High Contrast mode.
• There are no time limits, no auto-playing sound or video, nothing that flashes, and no third-party accessibility overlay — every control above is built into the page itself.

Known limitations

• The hero scene is decorative. Everything it communicates — what each sample cookbook is, what is inside it and how it is designed — is also available as text in the panel each cover opens, and in the Samples section further down the page.
• Typefaces are requested from a third party. If that request is blocked, the page uses the fonts already on your device; nothing becomes unreadable.
• We have tested with keyboard navigation, zoom, reduced-motion and forced-colours settings. We have not yet completed testing with every screen reader and browser combination.

Tell us if something is broken

If any part of this site is hard or impossible to use, email lucasszkliarski@genesis-8.com and say what happened and what you were using. We aim to reply within five working days, and we will tell you what we are going to do about it. If you need something on this page in another format, ask and we will send it.

Last updated 12 September 2026 · questions to lucasszkliarski@genesis-8.com