Accessibility Statement

Important Notice About Language

The English version of this Accessibility Statement is the single authoritative document. Translations are for convenience only. In any inconsistency, the English text governs.

1. Our Commitment

AIOCANA Technologies Inc. (“AIOCANA,” “we,” “us,” “our”) is committed to ensuring digital accessibility for people of all abilities. We believe that the web should be usable by everyone, and we continually improve the user experience of our Platform and the websites we build for our customers to meet or exceed applicable accessibility standards.

This commitment applies to: (a) the AIOCANA marketing website at www.aiocana.com; (b) the AIOCANA customer dashboard and administration interface; (c) AIBOT widgets and embedded components; and (d) customer websites built and hosted on the AIOCANA Platform, to the extent within our control.

2. Legal Framework

AIOCANA’s accessibility obligations are governed by:

• Accessibility for Ontarians with Disabilities Act, 2005 (AODA) — including the Integrated Accessibility Standards Regulation (IASR, O. Reg. 191/11), which requires WCAG 2.0 Level AA (and, for new content, WCAG 2.2 Level AA by applicable deadlines);
• Accessible Canada Act, 2019 (ACA) — federal legislation requiring federally regulated entities to meet accessibility standards;
• Québec’s Act to secure handicapped persons in the exercise of their rights (CQLR c. E-20.1) — provincial accessibility requirements for organizations operating in Québec.

3. Conformance Status

AIOCANA targets WCAG 2.2 Level AA conformance. This is the most current version of the Web Content Accessibility Guidelines published by the World Wide Web Consortium (W3C). Specific WCAG 2.2 success criteria we have implemented or are actively implementing include:

• SC 2.5.8 — Target Size (Minimum): All interactive elements (buttons, links, form controls) have touch target sizes of at least 24×24 CSS pixels;
• SC 2.4.11 — Focus Not Obscured (Minimum): Focus indicators remain visible when elements receive keyboard focus and are not completely hidden by author-created content;
• SC 3.2.6 — Consistent Help: Help mechanisms (documentation, contact information, chat) are located in consistent positions across the Platform;
• SC 3.3.7 — Redundant Entry: Information previously entered by the user is auto-populated where appropriate to reduce redundant re-entry;
• SC 3.3.8 — Accessible Authentication (Minimum): Authentication does not require cognitive function tests (memory, puzzles, calculations).

We also maintain conformance with WCAG 2.1 Level AA and WCAG 2.0 Level AA as incorporated by reference in applicable regulations.

4. Accessibility Measures

AIOCANA integrates accessibility into our development lifecycle through the following measures:

• Automated Testing: axe-core (≥ 4.10.x) integrated into our CI/CD pipeline and E2E test suite. Every new component and every production deployment is scanned for WCAG violations;
• Manual Testing: Keyboard-only navigation testing of all interactive flows. Screen reader testing with NVDA (Windows) and VoiceOver (macOS/iOS);
• Semantic HTML: All components use semantic HTML5 landmarks, ARIA roles where appropriate, heading hierarchy (h1-h6), and descriptive link text;
• Color Contrast: All text and non-text content meets WCAG 2.2 AA contrast ratios (4.5:1 for normal text, 3:1 for large text and graphics);
• Visual Asset Audit: All images include descriptive alt text. Decorative images use empty alt attributes. Video content includes captions;
• Third-Party Audits: Periodic external accessibility audits by qualified independent assessors (scheduled, not yet completed).

5. Technical Specifications

Accessibility of the AIOCANA Platform relies on the following technologies to work with the particular combination of web browser and assistive technologies or plugins installed on your device:

• HTML5 (semantic elements and landmarks);
• WAI-ARIA 1.2 (Accessible Rich Internet Applications);
• CSS (for visual presentation and responsive design);
• JavaScript (for interactive functionality, with fallbacks where feasible).

These technologies are relied upon for conformance with WCAG 2.2. If your assistive technology does not support these standards, you may experience reduced functionality.

6. Browser & Assistive Technology Compatibility

AIOCANA is designed to be compatible with current versions of:

• Google Chrome (most recent 2 versions);
• Mozilla Firefox (most recent 2 versions);
• Apple Safari (most recent 2 versions);
• Microsoft Edge (most recent 2 versions);
• Mobile browsers: Safari (iOS) and Chrome (Android), most recent 2 versions.

Screen reader compatibility is tested with NVDA (Windows), VoiceOver (macOS/iOS), and TalkBack (Android).

7. Known Limitations & Alternative Access

Despite our best efforts to ensure accessibility, there may be some limitations. We are actively working to identify and resolve any accessibility issues. Known areas of ongoing work include:

• Third-party embedded content (e.g., payment interfaces from Stripe) may not fully conform to WCAG 2.2 AA;
• AI-generated content may occasionally produce markup or text that does not fully meet accessibility standards — this content is flagged for human review;
• Some legacy components or pages not yet rebuilt may have WCAG compliance gaps.

If you encounter an accessibility barrier, please contact us and we will work with you to provide the information or service in an alternative format.

8. Feedback & Contact

We welcome your feedback on the accessibility of the AIOCANA Platform. If you encounter any accessibility barriers, or if you require information in an alternative format, please contact us:

Accessibility Coordinator — AIOCANA Technologies Inc.
Ottawa, Ontario, Canada
accessibility@aiocana.com

We aim to respond to accessibility feedback within five (5) business days. For formal complaints under the AODA or ACA, please contact the appropriate regulatory body.

Version: v1.0.0 — Effective: 2026-05-01 — English is the single authoritative language.