Accessibility is a working concern on this site, not a compliance exercise. The same standard I apply in client work, operationalising accessibility so that conformance is a design decision, not a late audit, applies here.
Conformance status
The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. They define three levels of conformance: Level A, Level AA, and Level AAA. This website is partially conformant with WCAG 2.1 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard. The known gaps are listed below, together with what is being done about them.
Measures taken
- Semantic structure throughout: single banner, main, and contentinfo landmarks, a skip link on every page, and headings that reflect the content rather than the layout.
- Colour is managed as a token system, with dedicated variants for text on dark surfaces checked against WCAG contrast thresholds — including third-party form styling, which is pinned to the same tokens.
- Text alternatives for informative images; decorative images are marked so assistive technology can skip them.
- No restriction on zoom or text resizing; the layout reflows at 200% magnification.
- Periodic review with automated tooling (axe-core) alongside manual checks of keyboard navigation, landmarks, and reading order. The most recent audit (July 2026) led to contrast and landmark corrections across the theme.
Known limitations
An audit on 15 July 2026 (axe-core 4.10.2 across ten representative page templates, with manual checks) found four issues: colour contrast on small labels, contact-form contrast, duplicated landmarks, and skipped heading levels in posts published before mid-2026. All four were corrected in the same cycle — the first three in the site theme, the heading hierarchy across twenty-one posts and one interactive template.
No unresolved barriers are known at the time of writing. Two structural caveats worth stating: automated tooling covers only part of WCAG, so gaps this audit could not detect may exist; and third-party components (the form plugin in particular) can reintroduce non-conformant defaults when updated. Both are checked at each review.
Two structural caveats worth stating: automated tooling covers only part of WCAG, so gaps this audit could not detect may exist; and third-party components (the form plugin in particular) can reintroduce non-conformant defaults when updated. Both are checked at each review.
Feedback
If you encounter a barrier on this site, something listed above or something the audit missed, I would like to know. Use the contact form and describe the page and the problem. I aim to respond within five working days, and reported barriers take priority over planned work.
Compatibility and technical specification
The site is built on WordPress with a block theme and relies on HTML, CSS, WAI-ARIA, and JavaScript for conformance. It is designed to work with current versions of Chrome, Firefox, Safari, and Edge, and with assistive technologies that support these standards. Content remains readable and operable without JavaScript.
Assessment approach
Self-evaluation: automated testing with axe-core 4.10.2 across the homepage, listing pages, field notes, case studies, category archives, and the contact page, combined with manual checks of keyboard access, skip-link behaviour, landmark structure, heading order, text alternatives, and zoom. Findings were remediated in the site theme in the same cycle and re-verified after deployment.
This statement was created on 15 July 2026 using the structure of the W3C Accessibility Statement Generator. It was last reviewed on 15 July 2026.