Trust
Accessibility statement
Our target is WCAG 2.2 level AA across this site, the product and the owner portal. Here is how we test it, what we know is not there yet, and how to tell us when something does not work for you.
The last audit
No audit is on record for this build. Until one is, treat everything on this page as our intent rather than as a measurement, and tell us what you find.
What we are aiming at
Level AA of the Web Content Accessibility Guidelines, version 2.2, for the public site, the application and the owner portal.
Owner facing documents we generate are produced with tagged headings and a defined reading order, so a screen reader can work through a statement or a notice rather than reading a wall of positioned text.
How we test
Automated accessibility checks run over every route on every build, and a critical or serious finding fails the build rather than being logged. Colour contrast is asserted against the colours a browser actually paints, not against the values in a stylesheet, because a stylesheet can be correct and lose to a later rule.
A manual pass runs at each release gate: a screen reader pass over the recurring tasks, keyboard only traversal with visible focus and no trap, 200 percent zoom without horizontal scrolling, and a check that reduced motion is respected.
What we know is not there yet
Live captions on a recorded meeting depend on the accuracy of the transcription provider. They are useful and they are not a substitute for a human captioner where accuracy matters.
Embedded third party components, such as the payment onboarding flow, are covered by the vendor's own accessibility statement rather than by ours. We name them rather than implying we control them.
The most recent audit found that the analytics banner on this site can completely cover a link while that link has keyboard focus, on every page of the public site. That fails a WCAG 2.2 requirement and it is not fixed yet. Several manual checks in the same run, a screen reader pass among them, were not performed at all, and the audit record says which.
Telling us something is wrong
Write to accessibility@boardbutler.com. Tell us the page, what you were trying to do, and what happened. We answer every message and we will tell you what we are doing about it.
If you need a document in an alternate format, ask and we will produce it. Owners can also request an accommodation from inside the portal, which routes to the corporation as well as to us.
Ontario and United States commitments
For Ontario customers, we intend to meet the accessibility requirements that apply to us under the Accessibility for Ontarians with Disabilities Act and its information and communications standards.
For United States customers, we intend to meet the obligations that apply to us in respect of accessible digital services. What exactly applies to a software vendor serving condominium corporations is a question we have put to counsel, and this page will carry the answer rather than our guess at it.
Tell us when something does not work
Write to accessibility@boardbutler.com with the page and what you were trying to do. Every message gets a reply from a person.