This site should work for everyone

A site full of hand-drawn sketches still has to work when you can't see the sketches, can't use a mouse, or get motion-sick from things that wiggle. Here's what this site does about that, what it doesn't do yet, and how to reach the one person who can fix a problem, usually quickly.

The standard I aim for

tl;dr · wcag 2.1 aa, as a floor

builtwiththeo.com targets WCAG 2.1 Level AA ↗ as a minimum, treated as a floor rather than a finish line. Accessibility is part of the build, not a retrofit: the same design system that draws the sketches enforces the rules below.

What's built in

tl;dr · contrast-checked · reduced motion respected · keyboard friendly · labelled sketches

Contrast. Body text is checked against a 4.5:1 minimum contrast ratio on both the teal canvas and the cream cards. Color is never the only carrier of meaning.
Motion. Every animation (the drawing squiggles, marching dashes, springy cards) has a prefers-reduced-motion alternative. Turn on “reduce motion” in your system settings and the page holds still.
Keyboard. Everything you can do with a mouse (open FAQs, submit forms, follow links) works from a keyboard, with visible focus.
Screen readers. Purely decorative sketches are hidden from assistive tech; meaningful diagrams carry written descriptions of what they show. Headings, landmarks, and form labels are real, not visual.

Known limitations

tl;dr · the honest list · shrinks over time

Some project demos link out to third-party sites (YouTube, client websites) whose accessibility I don't control.
The site hasn't yet had a formal third-party accessibility audit; testing so far is automated checks plus my own keyboard and screen-reader passes. If you hit something those missed, I want to know.

Found a barrier?

tl;dr · email me · i'm the developer · expect a reply within one business day

Email hello@builtwiththeo.com and describe what got in your way: the page, what you were trying to do, and the assistive tech or settings you use, if any. There's no support queue here: the person reading that email is the person who wrote the code, and real barriers go to the top of the list.