Everyone should be able to use this.

Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. Where WCAG 2.2 adds something that applies to a site this simple — bigger click targets, focus that never ends up hidden behind the header — I've followed that too.

I'm one person, not an audit firm, so I'll say it plainly: I've built and checked this against those guidelines, and I haven't paid for a third-party certification.

• Real headings in a real order, so a screen reader can jump around the page instead of reading it end to end.
• A skip link as the first thing you reach with the keyboard, so you can get past the header in one press.
• Everything works with a keyboard alone. Nothing needs a mouse or a drag.
• A visible focus outline on every control you can reach, in a colour that stands out against the surface it's on.
• Colour contrast at or above AA everywhere, including the small print. Orange is never used for text on a light background — it doesn't have the contrast, so on light sections it's decoration only.
• Motion respects your system setting. Turn on reduce motion and the animations don't run.
• Every form field has a real label, marks whether it's required, and announces its error message when something's wrong.
• The questions section uses the browser's own expand-and-collapse control, so it behaves the way your software expects — and still works with JavaScript off.
• No audio or video that starts on its own. No carousels, no pop-ups, no interstitials.
• No cookie banner, because the site sets no cookies — one less thing between you and the page.

Nothing, right now — I don't have a known failure on the list.

The one thing in flight: real photographs of finished jobs are being added over time, and each one gets written alt text as it goes in. If a photo ever turns up here without a useful description, that's a bug and I'd like to hear about it.

Email me at [email protected]. Tell me what page you were on, what you were trying to do, and what you were using — a screen reader, a phone, a keyboard, whatever it was. A rough description is plenty; you don't need the technical name for it.

I reply within two business days, usually sooner. If it's something I can fix, I'll fix it. If it's going to take a while, I'll tell you that instead of going quiet, and I'll find another way to get you what you needed in the meantime.