Accessibility.

The goal

The target is WCAG 2.2 level AA, the standard checklist that accessible websites are tested against. I do not claim the site is perfect. I claim it is checked, and that problems you report get fixed.

What is in place

• Keyboard. Everything works with Tab, Enter, and Space, a "Skip to content" link comes first, and focus is always visible and never hidden under the top bar.
• Screen readers. Pages declare English, have one main heading, headings in order, named regions, and described images.
• Reading. Text meets 4.5 to 1 contrast, and pages reflow on a phone or at 200% zoom without sideways scrolling.
• Motion. If your device asks for reduced motion, the animations stop. A Reduce motion switch in every page footer, and in the homepage hero, stops them too, on any device, and the site remembers your choice.
• Tap targets. Buttons and links are at least 24 pixels, so they are easy to hit on a phone.
• No overlay widget. The fixes are in the code itself, not in a plugin pasted on top.

How it was checked

On October 14, 2026, every page was scanned with axe-core 4.10 (the engine behind most accessibility scanners) at desktop and phone widths, then checked by hand with a keyboard. Result: no automated issues on any page.

Known limits

• The two forms run on Tally, a form service embedded in the page. Its accessibility is Tally's. Each form page has a link to open the form directly on Tally, which can work better with some screen readers.
• Videos live on YouTube, TikTok, and Instagram. They carry burned-in captions; the platform players are outside my control.

Report a problem

If anything on this site blocks you, tell me through any Clashworks profile linked in the footer, or reply to any message from me. Say which page and what happened. I answer within seven days, and if a form will not work for you, I will take your answers another way.