We build software for a living, so we don't think accessibility is a checkbox at the end of a project. This page says plainly how accessible this website is today — what we tested, what we fixed, what is still imperfect — and how to tell us if something blocks you.

The standard we measure against

We measure this site against WCAG 2.2 Level AA, the standard most accessibility law around the world points at. It covers things like keyboard operation, colour contrast, screen-reader compatibility, and text that survives being zoomed.

Where we stand

We believe this site now meets WCAG 2.2 Level AA. We audited every page in August 2026, found eleven problems, and fixed all of them. That assessment is our own — this site has not been through an independent accessibility audit, and we haven't tested it with every screen reader in use. So we'd put it this way: we know of no remaining Level AA failure, which is not the same as promising there isn't one.

The remaining known limitations are listed below. They're honest gaps rather than failures of the standard, and we'd still rather write them down than leave you to discover them.

What we fixed

The August 2026 audit turned up eleven issues. All are now corrected:

  • Portfolio screenshots can now be enlarged by keyboard. The enlarge control is a real button, so it can be reached by Tab and triggered with Enter or Space. When the larger view opens, focus moves into it, the rest of the page is held out of the way, Escape closes it, and focus returns to exactly where you were.
  • Every page now starts with a "Skip to content" link, so keyboard users can jump past the navigation instead of tabbing through it on all 35 pages.
  • The blog's topic filters now say what they did. The active filter is announced as pressed, and a live message reports the result — "Showing 3 posts tagged Case Study" — instead of the list changing silently.
  • Animations can be paused by anyone. A "Pause animations" button on the homepage stops the scrolling logo strip and the rotating screenshots, reachable by keyboard and usable on touch, not just by hovering a mouse.
  • Sideways scrolling is gone. The footer now stacks into a single column on narrow screens, so pages fit the window down to 320 pixels wide and at 400% zoom.
  • Links inside sentences are underlined again, so they no longer depend on telling green from grey.
  • Outlined buttons have a stronger border, well past the contrast the standard asks for, so the edge of a button is visible without relying on the text inside it.
  • Emphasised headings survive Windows High Contrast Mode instead of vanishing mid-sentence.
  • Breadcrumb trails are now real navigation — a labelled landmark you can jump to, with the current page marked as current.
  • Decorative symbols are no longer read aloud. Tick marks and the plus signs on collapsible questions are now silent to screen readers, cutting roughly 145 pointless announcements across the site.
  • Footer headings sit at the right level, so navigating by heading no longer suggests a missing section.

Known limitations

What we know is still imperfect. If any of it gets in your way, tell us and we'll fix it and send you what you needed in the meantime.

  • No independent audit. Everything here is our own assessment. We haven't paid for a third-party review or tested against the full range of screen readers and braille displays.
  • Three case-study screenshots are described in summary rather than in detail. On the Stickman case study, the written descriptions tell you what each screen is, but not how it's laid out. We'd rather leave an accurate summary in place than write a detailed description we haven't verified against the actual image.
  • Some industry pages use trade shorthand. Terms like POS and EHR appear without being spelled out on first use. Our glossary covers the software terms but not the industry ones yet.
  • Link previews have no description. When one of our pages is shared into Slack or LinkedIn, the preview image has no text alternative attached, so it may be announced as just "image".

What works well

Things that were already right before the audit, and still are:

  • Text contrast. Every text and background combination on the site passes, and the body text clears Level AAA — the stricter tier above the one we target — with room to spare.
  • Keyboard focus is always visible. Whatever you've tabbed to is outlined in green, at high contrast, everywhere on the site.
  • Zoom is never blocked. You can pinch-zoom and scale text on every page; nothing disables it.
  • Every image has a text description — all 43 of them, with no exceptions.
  • Reduced motion is respected. If your device is set to reduce motion, every animation on the site switches off — and there's now a pause button as well, for anyone who hasn't set that preference.
  • Page structure is consistent. Every page has exactly one main heading, one clearly marked main content area, and headings in a sensible order, so you can navigate by heading or by landmark on any page.
  • No pop-ups, no auto-playing video or audio, no timed content, and no forms to fill in — the site is plain pages and links.

How we tested

We audited every page against WCAG 2.2 Level AA in August 2026 — reviewing the code of each one, calculating colour contrast ratios arithmetically rather than by eye, and operating the site by keyboard in a real browser at a range of window sizes and zoom levels. This was our own internal audit, not an independent third-party certification, and we don't claim otherwise. Automated tools and hand review both miss things, so if you hit a barrier that isn't listed above, we'd genuinely like to know.

Accessibility in the software we build

If you're a client or thinking about becoming one: accessibility is something we can build into your project, and it's worth asking about early. Keyboard operation, screen-reader support, and contrast are far cheaper to get right while a thing is being built than to retrofit afterwards. Tell us if you have a specific obligation to meet — a public-sector contract, a procurement requirement, or a customer base that needs it — and we'll scope for it from the start rather than treating it as an extra.

Tell us about a barrier

If any part of this site stops you getting what you came for, email dan@revenantsystems.ai. A human reads it — there's no ticket queue and no form to fight with.

It helps if you can tell us the page, what you were trying to do, and what got in the way, plus your browser and any assistive technology you use. But send it however suits you — a one-line "the blog filters don't work with my screen reader" is genuinely useful.

We aim to reply within two business days. If we can't fix something quickly, we'll tell you what the timeline is and get you the information another way in the meantime.

Keeping this page honest

This page is dated, and we update it when the site changes — both to remove problems we've fixed and to add any we find. It was last rewritten on the day the fixes above went live. If it says something that no longer matches your experience of the site, that's a bug in this page, and we'd like to hear about it.