accessibility statement

The theme on this website appears to be old-school CSS doing skeuomorphic dot-matrix and other printer type output. It looks like something from 1998 pretending it’s 1980. It is visually distinctive.

However, this is simply a skin built on top of a highly technical, accessible foundation, rather than just an art project. It embraces contemporary (202x) technology to make it as accessible and usable for as many people as possible.

You can change the “theme” and the “media”, so from something that looks like it was spat out of a 9-pin dot-matrix printer onto ruled paper, to the crispness of a high-resolution laser-writer on plain paper, and many others between.

The theme supports dark/light mode.

More or less contrast is accommodated.

Accessible labeling is provided.

If you find the skeuomorphic approach too much, try theme “daisy” or “laser” on media “plain” for something more considered.

Reader mode is supported for a cleaner view.

Scope

This statement applies to content published on this website.

Accessibility approach

The minimum target is to meet WCAG 2.2 Level AA success criteria, and to implement applicable Level AAA criteria where feasible.

Assessment approach

Our process to assess and maintain accessibility includes:

Automated accessibility checks on key routes and states using tools such as Lighthouse, Arc Toolkit and Axe DevTools.

Integrated QC gate (checking accessibility and markup validation) when we deploy major or minor updates into production.

Manual testing for keyboard and assistive technology behavior.

Issue triage and remediation as part of normal maintenance.

Current status

Accessibility work is ongoing. We regularly test and improve this site.

We prioritise contrast: the light palette targets AAA-level contrast for main reading colours (WCAG 2.2 1.4.6-style thresholds). Dark mode stays high-contrast and is close on many pairs; we do not claim full WCAG 2.2 AAA site-wide conformance.

Lighthouse indicates accessibility score of 100% across both mobile and desktop devices. We get 100% across performance and best practices too.

Automated scores reflect a subset of checks, not full WCAG conformance.

Known limitations

Some parts of the site may not yet be fully accessible in every browser, device, or assistive technology combination. We are actively working on incremental improvements.

For the best experience, we recommend using current browser versions where possible.

JavaScript and fallback behavior

This website and theme use JavaScript to provide an enhanced, fluid experience.

However, if JavaScript is not available or is disabled, non-JavaScript fallbacks are provided. In such instances:

theme and contrast will be controlled by the browser or operating system and cannot be adjusted in-browser.

authentication and authorization may be less elegant, and may involve a few more clicks instead of being hands-off.

We also provide a print-friendly rendering to support reading comfort and alternative consumption, in addition to core web accessibility improvements.

Feedback and contact

If you encounter an accessibility barrier, contact us via the contact page and include:

the page URL

what you were trying to do

your browser/device and any assistive technology used

We will review and prioritize fixes as quickly as possible.

$LastModified: 2026-05-14 14:56:13Z (Thu, 14 May 2026) $