Accessibility

The standard

This site is built to WCAG 2.2 Level AA. That is a step beyond the WCAG 2.1 Level AA baseline referenced by EN 301 549, which is the harmonized standard behind the European Accessibility Act. We target the newer version because the criteria it adds are the ones this kind of site gets wrong.

What we do about it

Criterion	What we did
1.4.3 Contrast	A script reads the design tokens and checks every color pair the site puts together against AA, in both the light and dark themes. At the last run it passed all 106 pairs.
2.4.1 Bypass blocks	A skip link is the first focusable element on every page.
2.4.11 Focus not obscured	The header is sticky, so every focusable element carries scroll margin and never lands underneath it.
2.4.13 Focus appearance	A two-pixel outline plus a ring, contrasting against both the focused and unfocused state.
2.5.8 Target size	Interactive targets are at least 24 by 24 pixels, and buttons are 44.
1.4.10 Reflow	The site works at 320 pixels with no horizontal scrolling.
1.4.12 Text spacing	Layout uses no fixed heights, so increased line and letter spacing leaves text unclipped.
2.3.3 Animation	Animations last 180 milliseconds at most and never run on scroll. A reduced-motion preference turns all of them off.

What our check finds today

Before every release an automated check reads every page in the sitemap, plus the pages deliberately left out of it: search, the not-found page, partner sign-in, the site directory and the API index. That is 70 pages today. It looks at page language, titles, heading structure, image alternatives, form labels, link and button names, the skip link, tab order and table headers.

What a clean result leaves out

Passing an automated check is a floor. A tool can confirm that alternative text is present and has no way to judge whether it is useful. Whether the tab order makes sense to somebody who cannot see the layout is also beyond it.

So a person checks three things by hand each time: keyboard-only navigation through every interactive element, screen reader output on the mega menu and the search overlay, and whether every image description would tell you what the picture shows if you could not see it.

Known limits

• The product screenshots are complex images. Each has a description of what it shows, but a description is not the same as reading the interface, and the underlying data is not available in another format on this site.
• The hover explanations on the product row are hidden on touch devices, where there is no pointer to summon them. Each product page carries the same information.

Telling us

If something here blocked you, mail contact_us@cybriq.io or call (877) 547-3264. Tell us the page and what happened. We will reply within a working day and we will tell you when it is fixed.