Accessibility

Last updated: 18 November 2026

KAYZEN wants Omnillink to be usable by everyone, whatever their hardware, software or disability. The site is built to the WCAG 2.2 level AA criteria.

This page is not a statement of conformity. No audit by a person has been carried out yet: it says what was checked, what was not, and what is still imperfect.

What was built

  • A skip link, identified page regions, a single main heading per page and headings in order.
  • Every control works with the keyboard: demo tabs with the arrow keys, mobile menu and accessibility panel closed with Escape, focus always visible.
  • The colours of text, controls and the focus ring are chosen from computed contrast ratios, in the light theme and in the dark theme.
  • An options panel, at the bottom left of every page: text size, higher contrast, the Atkinson Hyperlegible font, pure black in the dark theme.
  • Animations are short, and switched off when your system asks for reduced motion.
  • The language of each page is declared, as is the language of passages written in another language.
  • Loading states, results and errors in the demo are announced with text, never with colour alone.
  • Buttons and navigation links offer a target of at least 44 pixels on each side.
  • Search opens with Ctrl+K; single-key shortcuts can be turned off in the options.

What was checked

Checks carried out on 18 November 2026, with automated tools and a review of the rendered pages:

  • the contrast ratio of every text and background pair actually used, computed by a script for both themes;
  • the keyboard path through the tabs, the mobile menu, the language switcher and the accessibility panel, in a scripted browser;
  • no horizontal scrolling at a width of 375 pixels, and no error in the console;
  • the rendering of each page in French and in English, in the light and dark themes, on a wide screen and on a phone;
  • the language selector, the search and the playground forms, with the mouse then the keyboard, in the same scripted browser.

What was not checked

  • Rendering by screen readers (NVDA, JAWS, VoiceOver, TalkBack).
  • A criterion-by-criterion audit, WCAG or RGAA, by a trained person.
  • Voice control, switch devices and other assistive technologies.
  • Zoom at 400% and the forced-contrast mode of the system.
  • The PDF documents the API produces from third-party pages.

Known limits

  • The demo shows content that comes from other sites. A screenshot is an image without a detailed description: the Content tab gives its text.
  • The structure of extracted content depends on the source page; it may be incomplete.
  • Error messages returned by the API are in English. The site adds an explanation in the language of the page.
  • Long code samples scroll horizontally inside their own block.

Adjusting the display

The round button at the bottom left opens the accessibility options: theme, text size, contrast, legible font, line spacing, underlined links, reduced animations. Your choices are saved in your browser and apply to every page.

Reporting a problem

If some content or a function is not accessible to you, tell us: we will look for a solution with you.

Page written with the help of an AI tool. It replaces neither an accessibility audit nor legal advice.

Keyboard shortcuts

CtrlKor/
Open search and commands
?
Show this help
←→
Move from one tab to the next
Ctrl↵
Run the request in the playground
Esc
Close a panel or a menu

Single-key shortcuts can be turned off in the accessibility options.