Eave Desk legal

Accessibility Statement

Last updated: 19 September 2026

Eave Desk wants every building company user, and every member of the public who opens a company's building designer, to be able to use it, including people who rely on screen readers, keyboard navigation, magnification, or other assistive technology.

Our target

We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA for the company workspace, the building designer that companies publish to their customers, the customer portal, generated documents, and this website.

Where we are today

Eave Desk has not yet completed a third-party accessibility audit and does not yet publish a Voluntary Product Accessibility Template (VPAT). We say that plainly rather than claim a conformance level we have not verified. [CONFIRM: add the date and tool of any automated scan already run, and any manual screen reader testing done.]

What is built in today:

Known limitations:

For building companies

If you publish an Eave Desk designer on your website, you may need to reference this statement in your own accessibility statement, and you should give customers a direct way to reach you that does not depend on the designer. If your customers or procurement contacts need a VPAT or an Accessibility Conformance Report, contact us and we will tell you exactly what has been tested and share the results we have.

Feedback and help

If you encounter a barrier in Eave Desk or in a company's designer, or need content in an alternative format, email accessibility@eavedesk.com. Tell us the page or screen, the company whose designer you were using if any, what you were trying to do, and the assistive technology you use. We aim to respond within 5 business days and to fix confirmed barriers in core workflows as a priority. If the barrier is in a company's own contact process rather than the designer, we will pass your message to that company.

Continuous improvement

Accessibility is reviewed as part of design and code review for new features, and we re-test the core workflows when the interface changes. This statement is updated when our status changes.

Document version 967b1fed00323b1e. This version identifier changes whenever the text changes; an acceptance records the identifier it was shown.