Accessibility statement

Last updated 3 November 2026

I want everyone to be able to use this site, whether you navigate with a mouse, a keyboard, a screen reader, voice control or a phone. The target is the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA.

Where it stands today

The site has not been audited by an independent accessibility specialist, so I do not claim full conformance with WCAG 2.2 AA. What I can say is what has been tested and what has not, below. Treat this as a work in progress that I keep checking.

What has been done

• A “Skip to main content” link is the first thing keyboard users reach on every page.
• Every page can be used with a keyboard alone, with a visible focus outline. The mobile menu closes with Escape and returns focus to its button.
• The calculator opens as a modal dialog: focus moves into it, stays inside it, and returns to where you were when you close it with Escape or the close button.
• The project questionnaire at /start has labelled fields, errors that are announced and linked to their field, focus that moves to the first problem, and step changes announced to screen readers.
• The work and blog filters report which filter is selected and how many results are showing.
• Text and interface colours were checked against the AA contrast ratios, and buttons and links outside running text are at least 24 by 24 pixels.
• Animations respect the “reduce motion” setting, and all content is visible if JavaScript is switched off.
• Pages have a single main heading, landmarks, a descriptive title, and the page language is set to Australian English.

How it was tested

• Automated checks with axe-core and Lighthouse on every type of page (home, about, services, work and a case study, blog and a post, calculator, questionnaire, contact, privacy and the not-found page), at phone, tablet and desktop widths. As at the date above, they report no accessibility issues.
• Manual keyboard testing in Chromium of the questionnaire, calculator, menu, filters and skip link.

Automated tools find only some problems, so the points under “Not yet tested” matter.

Not yet tested

• Screen readers such as VoiceOver, NVDA and JAWS. The page structure and labels are built for them, but I have not yet listened to the site with one.
• Browsers other than Chromium, including Safari and Firefox.
• Zooming to 200% and 400%, and high-contrast or forced-colours modes.
• Use on physical touch devices and with voice-control software.

I will update this page when those checks are done and if they turn up problems.

Content you may find elsewhere

Some pages link to sites and documents run by other people, such as Shopify help pages and client stores. I do not control their accessibility.

Tell me about a problem

If something on this site is hard to use, or you need information in another format, use the contact form. Include the page address, what you were trying to do, and the browser or assistive technology you use if you know it. I will reply within 48 business hours and tell you what I can do about it.