CybrIQ
● For security leaders at SMB.
Leaders site › Company › Accessibility
Accessibility statement

Our conformance target, what works today, and how to tell us when something does not.

CybrIQ aims to make the entire CybrIQ website usable to anyone working in security and IT, including people who use assistive technologies. This page is honest about where we are.

Conformance target

We aim for WCAG 2.2 Level AA across the CybrIQ website. Where we fall short, we say so on this page and we have it on the work list.

What works today

  • Semantic HTML throughout (proper heading hierarchy, landmarks, lists, tables).
  • Skip-to-content link as the first focusable element on every page.
  • Keyboard-operable navigation (no mouse required to reach any link or form).
  • Visible focus indicators on every interactive element.
  • Alt text on every meaningful image; role="img" and aria-label on every SVG diagram.
  • Form fields paired with explicit labels (no placeholder-only labels).
  • Color contrast meets WCAG AA on body text and interactive elements.
  • Reduced-motion preference honored: hero rotators pause when the visitor has prefers-reduced-motion: reduce set.
  • The site is responsive and reflows down to 320px viewport width without horizontal scroll.

Known limitations

  • Some of the editorial article SVGs (the 1200×1200 article billboards) use display-scale typography that may rasterize at lower resolutions on some screen readers. The supporting text is still present in the surrounding article body.
  • The diligence builder uses an html2pdf bundle for PDF export; the export step itself is not a screen-reader-friendly workflow. The builder’s data entry is fully accessible; the export download is the inaccessible step.
  • Long technical tables (API documentation, comparison grids) are best read on a desktop viewport. On mobile they reflow but require horizontal scroll within the table region.

How to report an issue

If you encounter an accessibility barrier on any page, email contact_us@cybriq.io with “Accessibility” in the subject line. Include the page URL and what you were trying to do. Response within two business days; fix scoped within one week if it is a code change, longer if it requires a content rewrite.

Testing methodology

The site is built without a JavaScript framework, so every page renders directly to HTML. We test with macOS VoiceOver (Safari), NVDA (Firefox + Chrome on Windows), and the keyboard-only navigation path. Color contrast is checked with the Stark plugin and verified against WCAG 2.2 AA thresholds. Reduced-motion is tested by enabling the macOS “Reduce motion” system preference.

This statement

Last reviewed 2026-05-15. We review the conformance posture every quarter or whenever a substantive site change ships, whichever comes first.