Accessibility Statement
This statement sets out the standard Isimo aims for, the places we currently fall short of it, and exactly how to reach a person who will do something about it. We would much rather hear about a barrier than have you quietly work around it.
Isimo exists to help you think clearly. If the interface itself is the thing standing in your way, it has failed at the only job it has. We treat an accessibility barrier as a defect in the product, not as a special request.
We build Isimo to be operated with a keyboard, read by a screen reader, magnified, driven by voice, and used without motion. We are a small team and we will not pretend we have got all of that perfect. What we will promise is attention: report a barrier and a person reads it, answers you, and either fixes it or tells you honestly when it will be fixed.
We aim at WCAG 2.2 Level AA — the Web Content Accessibility Guidelines published by the W3C, at the level most regulators treat as the working benchmark.
Because we operate from the Province of Ontario, Canada, the standard that applies to us by regulation is the WCAG 2.0 Level AA requirement in the Integrated Accessibility Standards Regulation made under the Accessibility for Ontarians with Disabilities Act, 2005. We aim past that floor on purpose, because the floor is older than the web we are actually building on.
Isimo is partially conformant with WCAG 2.2 Level AA. That is the precise term, and we use it deliberately: most of the product meets the standard, and some of it does not yet. The parts we know about are listed below rather than left for you to discover.
Accessibility work that is already part of how Isimo is written and reviewed:
None of this is a conformance claim on its own. It is the floor we work from, and what follows is what still sits under it.
These are the barriers we currently know about. Publishing them is not an excuse for them — it is so you can decide whether Isimo works for you without spending an afternoon finding out the hard way.
| Where | The barrier | What works today |
|---|---|---|
| The Clarity Field | It draws your goals as a three-dimensional graph on a canvas. A screen reader cannot read that canvas, and the camera controls expect a mouse or a trackpad. | Every node in the field also exists as ordinary text elsewhere in the product. Nothing lives only in the graph. |
| The vision board and brainstorm canvases | Placing, dragging, and resizing cards is pointer-driven. Keyboard and voice control cannot yet reach every one of those gestures. | You can create, edit, and read the content of every card without touching the canvas. Only the spatial arrangement needs a pointer. |
| Charts in statistics and analytics | Trends are drawn visually. The shape of a line carries meaning that is not announced. | The figures behind each chart are available as text on the same page. Ask us if you need a period exported. |
| Mismo replies | Answers stream in a word at a time. Some screen readers announce that steadily, others repeat or truncate it. | The finished reply is static text and reads correctly once it has settled. Tell us which reader you use and we will test against it. |
Two more, smaller but real: the site does not yet offer a skip to content link, so keyboard users pass through the navigation on every page — that one is on our list and is a small fix. And where you upload your own images, the alternative text is whatever you wrote; we cannot describe your pictures for you, though we do prompt for it.
If any part of Isimo is not usable for you, we will get you the same information or the same outcome another way. That might be an export, a plain list instead of a visual, a document in a format your software reads, or a person walking you through the step over email.
There is no charge for this and you do not have to justify the request. Write to accessibility@isimo.app and tell us what you were trying to do. We aim to have an accessible alternative to you in a timeframe that matches how urgent it is for you, not how convenient it is for us.
Accessibility feedback is welcome and it is genuinely useful.
Write to accessibility@isimo.app. If it is easier, use the contact page instead — it reaches the same people. Anything you can include helps, though none of it is required:
What we do with it. We acknowledge accessibility reports within 5 business days. We then try to reproduce the barrier and come back to you with one of three things: a fix, a workaround that gets you moving in the meantime, or a dated plan if it is a larger piece of work. If we cannot reproduce it, we will say so and ask you rather than quietly closing it.
You never have to disclose a diagnosis or a disability to report a barrier or to ask for an alternative format. We do not ask, and you should not have to explain.
Before starting formal proceedings of any kind about accessibility, please contact us and give us 30 days to put it right. Write to accessibility@isimo.app and set out what the barrier is and what you need. This mirrors the notice period in our Terms of Service, and it applies to us as much as to you.
We ask for this because it works. A barrier that reaches us directly is usually understood within days and fixed in the next release. The same barrier routed through a formal process takes months, costs both of us money, and — this is the part that matters — leaves the barrier in place the whole time. We would rather spend that time fixing the product.
If 30 days pass and we have not resolved it or given you a credible dated plan, escalate. Ask for it to be reviewed by someone senior at hello@isimo.app, and if that still does not land, you are entitled to take it further.
To be clear about what this section does not do. Asking you to come to us first is a request for the chance to fix our own defect. It is not a waiver, and it does not remove or delay any right you have under law. You keep every statutory and human rights remedy available to you — including filing an application with the Human Rights Tribunal of Ontario, raising a complaint under the Accessibility for Ontarians with Disabilities Act, 2005, or pursuing whatever equivalent exists where you live. Nothing on this page, and nothing we say in response to a report, should be read as asking you to give any of that up.
Some of what you see passes through other companies. Signing in with Google shows you Google’s screens, and content other members share with you is written by them, not by us. We do not control the accessibility of either.
Report it to us anyway. We will press the vendor where we have standing, and where we cannot move them we will look for a route around them — an alternative sign-in, an export, or a change on our side that means you do not have to go through the inaccessible thing at all.
This statement was last reviewed on 22 August 2026. We revisit it when we ship a significant interface change, when we close one of the barriers listed above, and at least once a year regardless.
Our testing combines automated checks in development with manual keyboard and screen reader passes over the flows people use most. We have not commissioned an independent third-party audit, and we are not going to imply otherwise — when we do, this section will say who carried it out and what they found.
This statement covers the Isimo marketing site and the signed-in product. It sits alongside our Terms of Service and Privacy Policy.
Questions
We would rather explain a clause than have you agree to something you do not understand. Write to privacy@isimo.app for anything about your data, or hello@isimo.app for everything else. A person answers.