Plain-English summary (non-binding). We want Chantro to be usable by everyone on the team, including people who rely on assistive technology. We target WCAG 2.1 Level AA across the product, our marketing site, and our transactional emails. If you run into a barrier, email the address in Section 7 and we will investigate and respond.
1. Our commitment
We believe an operating system for construction should be usable by everyone on the team, including people who use assistive technologies. Accessibility is not an add-on — it is a design requirement for every feature in Chantro, from the public marketing site to the deepest parts of the product.
2. Conformance standard
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the W3C. Where reasonable, we also implement WCAG 2.2 enhancements. Our ongoing conformance target applies to the Chantro web application, our marketing site, and the transactional email templates we send to Users.
3. What we build for
- Keyboard navigation. Every interactive control — navigation, forms, dialogs, menus, calendars, and kanban boards — is reachable and operable by keyboard alone.
- Screen readers. Our accessibility reviews include testing with common screen readers such as NVDA and VoiceOver on major browsers, and we use semantic HTML and ARIA only where the semantics are not already conveyed natively.
- Focus management. Focus state is visible, predictable, and returned sensibly when dialogs open and close.
- Color & contrast. Text and interactive elements are designed to meet AA contrast. All colors in the product resolve through a central design-token system, so when we adjust the palette the whole product moves together.
- Motion & animation. We respect
prefers-reduced-motionand suppress non-essential animation for users who request it. - Resizable text & responsive layout. Content reflows at 400% zoom without loss of information or functionality.
- Forms. Every input has a label, error messages are tied to the field they describe, and required fields are programmatically indicated.
4. Known limitations
Despite our best efforts, some parts of the product may not yet fully conform. We track known gaps and fix them on a rolling basis. Current areas of focus include:
- Complex data visualizations (dashboards, gantt views). We are adding structured table alternatives and summarized text descriptions.
- Drag-and-drop surfaces (kanban boards, org chart). Keyboard and screen-reader affordances are supported; we continue to improve announcement quality.
- User-uploaded content. We cannot guarantee the accessibility of documents or images uploaded by Customers — we provide tools to add alt text and descriptive captions.
- Third-party integrations. Embedded third-party interfaces may not match our conformance target.
5. Testing & review
Our approach combines automated and manual testing:
- Automated accessibility checks run in our pull-request pipeline for common, testable issues.
- Manual keyboard and screen-reader walkthroughs are required for new features and for changes to shared UI primitives (dialogs, menus, popovers, tables, forms).
- We periodically engage external reviewers to test user journeys and advise on improvements.
6. Third-party content
Pages may include embedded third-party content (for example, third-party integrations the Customer chose to connect, or videos from YouTube/Vimeo). We cannot guarantee that third-party content meets our standard. Where possible, we offer accessible equivalents (such as transcripts) and will work with Customers to find alternatives.
7. Report a barrier
If you encounter an accessibility barrier, we want to know. Please email accessibility@chantro.com and include, where you can:
- the page or feature where you encountered the issue;
- what you were trying to do;
- what happened or what was missing;
- the assistive technology, browser, and operating system you were using.
We aim to acknowledge reports within two business days and provide a remediation plan or workaround within fifteen business days, depending on complexity.
8. Alternative formats
If you need information or an action in an alternative format — for example, a large-print version of a document you received in the product, or help completing a form — contact accessibility@chantro.com and we will work with you and your Workspace Administrator to provide a reasonable equivalent.
9. Formal complaints
If you are not satisfied with our response, you may contact our legal team at legal@chantro.com. You may also have a right to file a complaint with a relevant accessibility authority in your jurisdiction.
10. Ongoing improvement
Accessibility is a journey. We will update this statement as we ship improvements, as new barriers are identified, or as standards evolve. The “Last updated” date at the top of this page reflects the most recent review.