Accessibility

Last updated August 26, 2026

Everyone should be able to use this site and the sites built here — including people who navigate by keyboard, use a screen reader, need larger text, or turn off animation.

The standard I build to

Sites are built toward the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, which is the benchmark the U.S. Department of Justice points to in its guidance on web accessibility and the ADA.

What that means in practice here

• Keyboard — every link, button, and form field is reachable with the Tab key and shows a visible gold focus ring. Nothing traps focus. A "skip to main content" link is the first thing you reach.
• Motion — the animated hero has a visible pause button, and the whole site honors your system "reduce motion" setting: turn it on and animation stops, with the finished state shown instead.
• Contrast — body text and captions are tested against their backgrounds and exceed the 4.5:1 minimum.
• Images — meaningful images carry text alternatives; purely decorative images are hidden from screen readers so they don't add noise.
• Video — the background film is silent and decorative, and is marked so screen readers skip it.
• Forms — every field has a real, visible label tied to it, and tap targets are at least 44 pixels.
• Structure — one main heading per page, headings in order, and the page language declared.

Known limitations

• The chat assistant is a custom component and has had less assistive-technology testing than the rest of the site. If it gives you trouble, text or email instead — you'll reach me directly either way, and faster.
• Demo pages are portfolio pieces for fictional businesses. They receive the same keyboard and contrast treatment but are not maintained to the same standard as this site.
• Testing has been done with automated tooling and manual keyboard passes. It has not been formally audited by a third party.

For clients

Websites I build start from these same practices — keyboard access, visible focus, labeled fields, text alternatives, tested contrast. Two things worth knowing:

• Accessibility depends on content too. Photos added later need alt text, videos with speech need captions, and PDFs have their own rules.
• A build includes accessible construction, not a formal conformance audit or certification. If you need a documented audit — some contracts and public work require it — that's quoted separately.

Feedback loop

If you report a barrier and I can't fix it quickly, I'll tell you honestly how long it will take and offer another way to get what you needed in the meantime — a phone call, a text, or the information read to you directly.