Accessibility
Accessibility statement
This site should be usable whether you browse with a mouse, a keyboard, a screen reader, magnification, or with motion reduced. Here is what has been done, how it was checked, what is not finished, and how to tell me if something is broken for you.
Last reviewed 16 August 2026
The standard I am working to
The target is WCAG 2.2 Level AA. I am not claiming full conformance, and I would be careful with any site that does so casually. Automated tools can only verify a minority of the success criteria, and no independent audit of this site has been carried out. What follows is what has actually been tested.
What has been done
Structure and navigation
- One
<h1>per page and no skipped heading levels - A skip link to the main content on every page
- Real landmarks — one
<main>,<nav>and<footer>per page - Every interactive control is a real link or button, reachable and operable by keyboard
- Visible focus outlines that are never removed
- Accordions and the mobile menu use native
<details>, so keyboard and screen-reader behavior comes from the browser rather than from script
Content and presentation
- Body text at 17px, never below 16px, and no text baked into images
- Text and interface colours checked against AA contrast, including the dark bands
- Descriptive link text — no bare “click here”
- Decorative graphics hidden from assistive technology; meaningful ones described
- Touch targets of at least 44×44px on the mobile action bar
- Layout reflows without horizontal scrolling down to 320px
prefers-reduced-motionis respected: the animated chain and every hover lift stop entirely
How it is tested
Every release runs an automated accessibility audit with axe-core against the WCAG 2.0, 2.1 and 2.2 A and AA rule sets, across the main page types at both desktop and mobile widths. The most recent run reported zero violations, and Lighthouse accessibility scores 100 on mobile. Criteria that cannot be automated — heading order, link purpose in context, focus order and reduced-motion behavior — are checked by hand.
A release also fails outright if a page loses its <h1>, its<main> or its skip link, or introduces a heading skip. Those are the regressions most likely to slip past review, so they are enforced mechanically rather than remembered.
Being straight with you
Known limitations
- No independent third-party accessibility audit has been carried out.
- Testing has used axe-core, Lighthouse and keyboard navigation. It has not been tested end to end with every screen reader and browser combination.
- Booking opens Cal.com, a third-party service whose accessibility I do not control. Every booking button is also a normal link to that page, so you are never dependent on the pop-up.
- Articles are drafted with AI assistance and reviewed before publication. If one lacks structure that makes sense read aloud, tell me and I will fix that article.
- Client sites linked from the homepage client section are separate sites with their own accessibility positions.
If something does not work for you
Tell me and I will fix it. This is a one-person business, so the message reaches the person who can change the code — there is no queue and no ticket to escalate.
Email [email protected] or call+1 (512) 336-9618. Please say what page you were on, what you were trying to do, and what you browse with. I aim to reply within two business days, and to fix or offer a workaround for anything that blocks you.
If you need information from this site in another format, ask and I will send it.