Accessibility statement
Built to be used by everyone.
I want this site to work for the widest possible range of people – those using assistive technology, those reading on small screens or in difficult lighting, and those with visual, motor or cognitive differences.
This page sets out the standard I aim for, what that means in practice, and how to flag anything that isn’t working for you.
The standard
This site targets WCAG 2.2 Level AA, with Level AAA on text contrast wherever the design palette allows.
The European Accessibility Act came into force in Ireland in June 2025. Its specific legal obligations don’t apply to a service practice of this scale – but the standard it sets is one I aim to meet anyway. Accessibility is part of the craft, and a site that’s easy to use for everyone is simply better work. Good practice doesn’t need a regulation to enforce it.
What this means in practice
The site is built on semantic HTML and tested with both keyboard navigation and screen-reader walkthroughs.
Every interactive element is reachable by keyboard, in a logical reading order, with visible focus indicators.
Text and interface contrast is verified against WCAG ratios, with AAA targets met for body text against the page background.
Tap targets on touch devices are sized at 44 pixels minimum – above the WCAG 2.2 floor and matching Apple’s interface guidelines.
Animation and transitions respect the prefers-reduced-motion
preference at the operating system level. If your device asks for less motion,
the site listens.
Type sizes scale fluidly between small and large viewports rather than jumping at breakpoints – content stays readable at any width.
Fonts are self-hosted rather than loaded from third-party CDNs, so reading the site doesn’t involve your data being sent to advertising or analytics infrastructure outside this domain.
No cookie banner, no tracking scripts, no autoplay media, no interstitials or pop-ups.
Page transitions between sections of the site are brief by design, and respect your reduced-motion preference if set at the operating-system level.
Known limitations
I’m working through the site continuously, and a small number of areas are not yet at the standard I want them to be.
Older articles migrated from the previous site may have images without complete alternative text. These are being updated as I work through the archive.
A small number of older articles still reference images hosted on the previous site’s content delivery network. These will be brought onto this domain as the archive is reviewed.
If you find something not listed here, please tell me.
How to report a barrier
If you find something on this site that doesn’t work for you, or that you’d like to see improved, please get in touch through the contact page. I’ll respond within five working days and aim to address the issue as quickly as I can.
If you’re not satisfied with how I’ve responded, tell me. There’s no external body to refer this to, because I’m doing this voluntarily – but I want to hear when I’ve got it wrong.
A note on the practice
Accessibility isn’t a finished state. It’s a practice that keeps moving – as standards evolve, as the site grows, as I learn from people who use it differently. This statement reflects where things are today, and I update it as the work continues.