Our commitment
Canary IQ Inc. is committed to providing a website that is accessible to the widest possible audience, including people who use assistive technologies. We work to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, published by the World Wide Web Consortium (W3C), and we treat accessibility improvement as an ongoing obligation, not a one-time project.
Conformance status
canaryiq.com is partially conformant with WCAG 2.2 Level AA. Partial conformance means that some parts of the content do not fully conform to the accessibility standard. The limitations are described below.
Measures taken
To support accessibility, CanaryIQ has taken the following measures:
Internal accessibility audit (July 2026). We ran an automated accessibility audit using axe-core 4.12.1 across nine representative pages — covering the home page, top-level marketing pages, a learn article, the glossary, the intelligence index, an intelligence topic page, and the contact page — supplemented by a static markup scan across all ~300 published pages and a manual template inspection. The audit identified ten categories of issue.
Remediation of high-priority findings. Issues identified as high or medium severity — including colour contrast failures on breadcrumb links, intelligence-page metadata labels, and topic-page overlays; an incorrect logo aria-label carried over from the starter kit; FAQ accordion markup; landmark violations on the cookie banner; mobile navigation focus containment; the skip-to-content link at mobile breakpoints; and heading hierarchy on topic pages — were remediated as part of the same compliance sprint in July 2026.
Baseline markup standards applied site-wide. The static-markup scan confirmed that all images carry alt text, no links or buttons are empty, all visible form inputs are labelled, each page has exactly one h1, and no positive tabindex values are used across the full ~300-page site.
Ongoing testing programme. An npm script (`npm run a11y`) using axe-core is committed to the repository for use in development and CI environments. We intend to expand automated test coverage and conduct manual keyboard and assistive-technology testing as additional pages and features are developed.
Known limitations
Despite our remediation work, the following limitations remain. We are actively working to address them:
Limited page sample tested. Nine of approximately 300 pages were included in the July 2026 axe audit. The untested pages share the same templates as the tested ones, so issues found on tested pages are likely to be present on untested pages as well. A broader automated sweep and manual checks of remaining page types are planned.
Interactive and dynamic states not fully tested. The automated audit tested static page-load DOM. Interactive states — including the open mobile navigation overlay, expanded FAQ accordion panels, cookie-banner settings, and hover/focus states on the intelligence widgets — were not tested in the automated pass. Browser-based interactive and assistive-technology testing is in progress.
Full keyboard and assistive-technology walk not yet completed. Manual tab/shift-tab traversal, visible focus verification on all interactive elements, and screen-reader testing across the site have not been completed. These are scheduled as part of the ongoing accessibility programme.
Colour contrast on focus rings at light backgrounds. The gold (#facc15) focus-visible outline provides adequate contrast on dark backgrounds but its contrast against light (stone-100) backgrounds has not been formally measured. This is scheduled for verification.
Reporting an accessibility barrier
If you encounter an accessibility barrier on canaryiq.com, we want to know about it. Please email us at [email protected] with a description of the barrier and the page where you encountered it. We aim to respond within 5 business days and will work with you to provide the information or assistance you need while we address the issue.
Technical information
canaryiq.com relies on the following technologies for conformance with WCAG 2.2: HTML, CSS, JavaScript (Alpine.js), and SVG. This statement was prepared on 9 July 2026 and will be reviewed and updated as remediation work progresses.