Accessibility statement

• Automated checks. Before every release, axe-core checks every page at seven widths, from 360 to 2560 pixels, against the WCAG 2.0, 2.1 and 2.2 rules at levels A and AA. A release does not ship while axe reports a violation.
• Keyboard. The checks press Tab through the Work cards and the Process stages, to the case studies’ recordings and past the forms’ security check, and check that the focus ring shows on Home’s first controls, the Work cards and the Process stages. In November 2026 a keyboard walk of thirteen pages, forward and back, reached every control, and each showed a focus ring.
• Reduced motion. With your system set to reduce motion, the site stops its animations, keeping only short fades, and the checks hold that at every release. The Pause motion button stops what moves on its own.
• Forced colours. The checks load Home and the AI Systems page with forced colours, as Windows contrast themes use them, emulated in Chromium, and confirm that the logo, its focus ring and the pressed state of a switch stay visible.
• Text over pictures. Automated checks leave the contrast of text that stands on a picture for a person to review, so at the places most at risk, the checks measure it from the pixels on the screen.
• Browsers. Every accessibility check runs in Chromium. Firefox and WebKit load Home, the Work page, a case study and the Process page, to check that they render and work.

We have not tested the site with a screen reader or with speech input, and we have not tested it in Safari on a Mac, an iPhone or an iPad.

• On some windows narrower than 1000 pixels, the line of fine print under the stage timeline on the Process page crosses a lit sphere in the picture behind it, and the letters over the sphere fall below the 4.5:1 contrast WCAG asks for.
• Most text is sized to the window, not to the default font size set in your browser, so changing that setting changes little.
• Browser zoom enlarges body text in full on windows up to 1920 pixels wide. On wider windows, and in the largest headings, it enlarges text less, so at 200% it may not reach twice its size.
• Pause motion stops what moves on its own. It does not stop what moves as you scroll.
• The layout is not composed for a phone held on its side.
• On touch screens some links are smaller than the 44 pixels we aim for: a few footer links, the sources at the foot of a note, and the links in a note’s contents rail. Each meets the minimum WCAG 2.2 sets, by its size, its spacing or because it sits in a line of text.
• When a form is sent with mistakes, each field announces its own error, so a screen reader may read several at once.
• The figure on the AI Systems page is named by its whole caption, which is long to hear.
• The contact form and the newsletter sign-up use Cloudflare’s security check, which is Cloudflare’s control, not ours.

If something on this site is hard to use, or you cannot reach it, write to hello@kordalsystems.com. Tell us the page and what happened. We reply within one business day.