Accessibility Statement

Standard we target

cybriq.io is built to conform to Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. This is the same standard most US public-sector procurement and Section 508 alignment work cite, and the standard we hold ourselves to for both the marketing site and the customer-facing CybrIQ platform.

What that means in practice

• Keyboard-navigable. Every interactive element on this site can be reached and activated with a keyboard alone. The site provides a "Skip to content" link as the first focusable item on every page.
• Visible focus indicators. All interactive elements show a visible focus state when reached by keyboard. The mobile-menu toggle, the search button, and form fields all surface focus.
• Sufficient color contrast. Body text and most UI elements meet or exceed WCAG 2.1 AA contrast ratios (4.5:1 for body text, 3:1 for large text and UI components). The brand orange and brand blue are reserved for accents on dark or off-white backgrounds where contrast holds.
• Semantic HTML. The site is built on plain HTML elements — landmarks (header, main, nav, footer), headings in document order, lists for lists, and form labels for every input.
• Image alt text. Informational images carry descriptive alt text. Decorative images use empty alt or are marked aria-hidden.
• Captions and transcripts. Videos that explain product or company material include captions on the source platform (YouTube). Where a video carries information not available in nearby text, we provide a transcript or text equivalent on the same page.
• Resizable text. The site uses relative units in most places. Browser zoom up to 200% does not cause loss of content or function on the pages we test against.
• Respects motion preferences. Animated elements (the hero rotator, the InfoComm announcement banner pulse) honor the prefers-reduced-motion setting where the browser reports it.

Known limitations

We are honest about what we have not finished. Today the following are known gaps we are working on:

• Some product diagrams and SVG illustrations have generic alt text. We are working through them to add more descriptive equivalents.
• The interactive tour at /tour.html uses keyboard-accessible controls, but the screen-reader experience for the spotlight overlay has not been validated end-to-end against assistive technology yet.
• The ROI calculator at /calculator.html reports results visually but does not yet announce them to screen readers as live regions. We are adding aria-live in the next iteration.
• A handful of older one-pager PDFs in the resources area were produced before our PDF accessibility check was in place. Replacement versions are in production.

How we test

Each new page is checked against an automated accessibility scanner during development, and the navigation, hero, and form patterns are tested by keyboard before publish. We periodically validate critical paths (homepage, product pages, contact form) with VoiceOver on macOS and NVDA on Windows.

Automated tools catch a meaningful subset of issues but not all of them. Human reports from actual users are the most reliable signal we have, and we treat them that way.

Reporting a barrier

If you ran into something on cybriq.io that did not work for you, please tell us. We treat accessibility reports as customer-impact issues, not feedback.

Email accessibility@cybriq.io with:

• The page URL
• What you were trying to do
• What happened (or did not happen)
• The browser and assistive technology you were using, if you know

We aim to acknowledge accessibility reports within two business days and to provide a substantive response or remediation timeline within ten business days. Critical barriers (a blocking issue on a primary path) get prioritized inside the same week.

CybrIQ platform accessibility

This statement covers the cybriq.io marketing site. Customer-facing administrator interfaces of the CybrIQ platform itself follow the same WCAG 2.1 AA target and are tested against the same patterns. Customers and prospective customers can request a current Voluntary Product Accessibility Template (VPAT) for the platform from their account team or by writing to the address above.

Changes

This statement is reviewed when meaningful site changes ship and at least once per quarter. The "Last updated" date at the top reflects the latest review.

Questions about this statement? Write to accessibility@cybriq.io or contact_us@cybriq.io.