Accessibility statement

We want this website to be usable by as many people as possible, regardless of how they access the web. We are working towards the Web Content Accessibility Guidelines (WCAG) 2.2, level AA as our standard.

What is implemented

• Semantic HTML landmarks (header, navigation, main and footer) so assistive technology can navigate the page structure.
• A "skip to content" link as the first focusable element on every page.
• Full keyboard operability, with a visible focus indicator on interactive elements.
• Status and meaning conveyed by text and shape, never by colour alone.
• Text alternatives for meaningful images, and decorative graphics hidden from assistive technology.
• Support for reduced-motion preferences, honouring the operating-system setting.
• Readable, resizable text and layouts that reflow on small screens without loss of content. Wide tables and diagrams scroll within their own container.
• Important content is server-rendered, so it is available without relying on client-side scripting.

What we have measured

We do not assert conformance. Here is what was checked, and how. Each of these ran across every one of the 215 pages this site serves, and not a sample. The colour sweep was a one-off on 25 August 2026. Everything below it is re-run on every release: each count is an assertion in our check chain, a non-zero one exits non-zero, and a release is packaged only after the chain has passed. So these are gates and not a snapshot of one afternoon.

• Colour contrast (1.4.3). Each text node measured against the surface it sits on, resolving gradient backgrounds to their worst-case stop. Zero elements below the AA threshold. Getting there meant darkening the terracotta accent, the warning colour and nine syntax-highlighting colours in our code blocks — the code theme accounted for almost all of the original failures.
• Headings (1.3.1). Exactly one h1 per page and no skipped levels anywhere.
• Images (1.1.1). Each image carries an alt attribute, and a build fails if one does not, across all published pages. Most of the archive was reviewed image by image and described, or marked decorative where it is decoration. Sixteen images imported on 9 September 2026 carried alt text naming the section each one sits in instead of describing the picture, because nobody had looked at them. Each was opened and described on 24 September 2026. One of them is a code snippet shipped as an image, so its alt carries the code.
• Names and labels (4.1.2). Each form control has an accessible name. No link is left without accessible text.
• Parsing (4.1.1). No duplicate element ids; lang set on every page.
• Reflow (1.4.10). Checked at 390 px: no page scrolls horizontally. Wide tables scroll inside their own focusable container, leaving the page still.
• Without JavaScript. Article content, navigation and the full 104-item archive render server-side. Scripting adds filtering. Access does not depend on it.
• Link targets. Every in-page anchor resolves to an element that exists.

Known limitations

Being specific is more useful than a clean bill of health:

• Contrast was measured programmatically. That catches text on a resolvable background. It does not judge text over a photograph, and it is not a substitute for testing with a real screen reader, which we have not commissioned.
• Some diagrams in migrated articles are complex enough that an alt description tells you what the diagram shows without fully replacing it. Where that matters, ask us and we will describe it properly.
• Decorative images carried over from our previous site have an empty alt because the original had no description to migrate.
• We have not audited keyboard operation of the interactive tools with assistive technology, only by keyboard.

Reporting a problem

If you encounter a barrier, or need information in a different format, please tell us. Email info@flexiana.com with the page address and a short description of the problem, and we will respond and work to put it right.