Accessibility
I want this site to be usable by as many people as possible, regardless of technology or ability. The aim is to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, and to improve continuously as the site grows.
What this site is built to support
- Semantic HTML. Pages use structured markup so screen readers and other assistive technologies can navigate headings, landmarks, lists, and forms reliably.
- Keyboard access. Primary navigation, links, forms, and interactive controls are intended to be reachable and operable with a keyboard alone. A “skip to main content” link is provided at the start of each page.
- Colour and contrast. Text and interactive elements are designed to meet or exceed a 4.5:1 contrast ratio against their backgrounds. Colour is not used as the only means of conveying information.
- Resizable text. Content should remain readable and usable when browser zoom or system text size is increased.
- Images. Informative images should include alternative text. Decorative images are marked so assistive technology can ignore them.
- Forms. Form fields use visible labels, clear focus states, and error messaging that does not rely on colour alone.
- Motion. The site avoids decorative animation that is essential to using content. No autoplaying video is used by default.
Technical approach
This site is published as static HTML and CSS. Public pages do not require JavaScript to read content. Where a small amount of script is used (for example, the mobile navigation toggle or cookie notice), content remains available if scripting is unavailable.
The site is generated with Chinaski, a self-hosted static CMS. That architecture keeps the public site simple, fast, and dependency-light for assistive tools and older browsers.
Known limitations
Accessibility is ongoing work, not a one-time claim. As new pages, media, embeds, or third-party tools are added, some content may temporarily fall short of the standard I aim for. PDF or document downloads, if provided, may not always meet the same accessibility level as HTML pages. Embedded third-party content (maps, video players, widgets) is outside full control of this site.
Compatibility
Pages are tested with modern browsers on desktop and mobile. Assistive technology varies by user and device; I welcome reports of failures with specific browser, OS, and assistive tool combinations so they can be fixed.
Feedback and accommodations
If you encounter a barrier on this site, or if you need information in a different format, please contact me. Describe the page and the problem if you can — that helps resolve issues faster.
I will respond within a reasonable time and work to remediate confirmed issues.
Updates
This accessibility statement was last reviewed in July 2026 and will be updated as the site and its practices change.