Accessibility statement

We aim for WCAG 2.2 AA across this site: semantic markup, visible focus states, keyboard-operable interactive elements, sufficient contrast, and forms that work without JavaScript.

Known limitations. We're a small team; if something isn't usable — a contrast issue, a screen-reader snag, a keyboard trap — we want to know.

Report a problem: contact form or reply to any email from us. We fix accessibility issues as bugs, not backlog.