Home›Accessibility

Accessibility statement

Updated September 26, 2026 · Oleksandr Korop, publisher

This site is built to be readable with a keyboard, a screen reader or a magnifier. Where it falls short, we would rather hear about it than not know.

What we aim at

We target WCAG 2.2 level AA. This is a self-assessment, not a certified audit, and we say so rather than implying a conformance claim we have not paid anyone to verify.

What is in place

• Semantic headings in order, with no skipped levels, so a screen reader can navigate by structure.
• A skip-to-content link as the first focusable element on every page.
• Real button and a elements for every control, so the keyboard reaches all of them.
• Body text at a contrast ratio of at least 4.5:1 against its background, and large text at 3:1.
• Colour never used as the only carrier of meaning: the AI-disclosure chips differ in fill, outline and wording, not hue alone.
• Every chart and schematic is inline SVG with an aria-label describing what it shows, and a caption repeating the finding in words.
• Tables use real th scopes and captions rather than styled divs.
• Touch targets of at least 44 by 44 pixels.
• Text reflows to a single column at 320 pixels with no horizontal scrolling.
• No autoplaying media, no motion that cannot be stopped, no flashing.

Known limitations

• Long comparison tables scroll horizontally on a narrow phone. The data is reachable, but a wide table is awkward with a screen magnifier.
• Some third-party app icons carry text inside the image that a screen reader cannot read; the alt text names the app instead.
• We have not tested with every assistive technology combination in use.

Telling us about a barrier

If something here is unusable for you, write to us with the page and what happened. We treat access problems as defects, not requests, and we will tell you what we are doing and when.