Accessibility statement

We aim for conformance with Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the W3C. WCAG defines requirements for designers and developers to improve accessibility for people with a wide range of disabilities including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.

We comply with the Accessibility for Ontarians with Disabilities Act (AODA) and design with the Americans with Disabilities Act (ADA) Title III in mind for our US visitors.

• Semantic HTML across the site so assistive technologies can navigate the structure of every page.
• Visible focus indicators on every interactive element, with keyboard navigation supported on all pages.
• Color contrast ratios that meet or exceed 4.5:1 for body text and 3:1 for large text and interactive controls.
• Alt text on meaningful images. Decorative images are marked aria-hidden so they do not clutter screen-reader output.
• Form labels tied to their inputs. Required fields and validation errors are announced.
• Reduced-motion preferences respected. Animations stop or simplify when the operating system requests reduced motion.
• Heading hierarchy that follows the page structure (h1, h2, h3) without skipping levels.
• Buttons and links that describe their purpose. No bare 'click here' or 'learn more' without context.

The following are known gaps we are actively addressing. None are blockers for the core flows, but they fall short of full WCAG 2.1 AA in the workspace product specifically:

• DAG viewer keyboard navigation: hovers reveal task details that are not yet fully reachable by keyboard. We are wiring this in Q2 2026.
• Marquee carousels on the home and integrations pages: pause-on-focus is implemented, but a manual pause control is not yet visible.
• Embedded media: a few pages with embedded video are missing transcript-style alternatives. Replacement is in progress.

The site and product are tested manually with the following assistive technologies on a regular cadence. We do not promise perfect compatibility, but we fix issues we find or that you report:

• VoiceOver on macOS and iOS
• NVDA and JAWS on Windows
• TalkBack on Android
• Keyboard-only navigation in Chrome, Firefox, Safari, and Edge

If you find a barrier or have feedback about our accessibility, email [email protected]. Include the page URL, the assistive technology you are using, a description of the problem, and any specific suggestions you have. We aim to acknowledge reports within two business days and resolve confirmed barriers within thirty.