WCAG 2.1 AA conformance and the path for reporting access barriers.

Standard

This site is built to substantially conform to WCAG 2.1 Level A and Level AA. “Substantially conforms” is the term for content that meets the standard with minor, known, documented exceptions. The known exceptions are listed below.

What conforms

• Keyboard navigation. Every interactive element is reachable via keyboard alone. Skip-to-content link present on every page.
• Focus visibility. Focus indicators are visible against page backgrounds; focus order matches visual order.
• Semantic structure. Headings nested correctly (one h1 per page, no skipped levels). Landmarks (header, nav, main, footer) present. Lists use list markup.
• Color contrast. Body text meets 4.5:1; large text and UI elements meet 3:1. The Utelogy-leaning navy / sky palette was chosen partly for this.
• Text alternatives. Images include alt text. SVG diagrams include role and title attributes. Decorative SVG and dividers are marked decorative.
• Resize and reflow. Content reflows at 200% zoom without horizontal scrolling at standard viewport widths.
• Calculator accessibility. Every field has a visible label. The (?) help icons are keyboard-focusable and the help text is announced via aria-describedby.
• Motion. No autoplaying motion. No flashing or parallax patterns that risk vestibular triggers.

Known exceptions (under remediation)

• Some SVG diagrams use color to differentiate the two product circles in the Venn fusion. The labels include the product name in text so the diagram is intelligible without color; the underlying SVG also includes a long-description text in the <desc> element for screen readers.
• The calculator's (?) tooltip pattern is keyboard-focusable but uses a focused-element CSS rule that may render as a popover on touch devices in older browsers. A click-toggle alternative is also wired up.

How to report an access barrier

If you encounter content on this site that is not accessible to you, please report it. We aim to respond within five business days and to remediate, or to publish a plan with a target date, within thirty business days.

• Email: accessibility@cybriq.io
• Subject line: “Access barrier” followed by a short description.
• Include where helpful: the page URL, the assistive technology and version, the browser and version, the operating system, and a description of the barrier.

Last reviewed: 2026-05-12.