Terms · Privacy · Subprocessors · Security · AI · Acceptable use · Accessibility · DPA · Français

Accessibility

Version 1.0 · Effective 2026-08-20 · Last updated 2026-08-20

This statement describes how accessible LobiPlan is today — what we have measured, what does not work, and what we will do for you while it is broken. It covers the LobiPlan web application at app.lobiplan.com and the marketing site at lobiplan.com, both published by LobiSolutions.

What we are telling you

LobiPlan is built by a very small team. We have done substantial, measured accessibility work in some areas and none at all in others, and this page says which is which.

We do not claim conformance to WCAG 2.1 Level AA. No independent auditor has assessed this product, and no assistive-technology user has ever tested it. We would rather tell you that than let you find out.

Conformance status

Partially conformant with WCAG 2.1 Level AA. Self-assessed. Not independently audited.

"Partially conformant" means parts of this product meet the standard and parts do not. The known exceptions are listed below. There are almost certainly others we have not found, because we have not yet done the kind of testing that finds them.

We have not produced a VPAT or an Accessibility Conformance Report, and we will not produce one before an audit. A self-assessment dressed as a supplier representation is worse than no document.

What we have measured, and how

These are not intentions. Each of the first four is enforced by an automated test that runs on every build and reads the code that actually ships — not the code we meant to ship.

• Colour contrast, solved per role. Every colour in the product carries three separate values rather than one: a background fill, a text colour meeting at least 4.5:1, and a border colour meeting at least 3:1 for non-text elements. Using a fill as a text colour is the failure this design prevents. The values are checked automatically against the stylesheet we actually publish, across five page surfaces and four themes including a pure-black mode.
• Higher-contrast modes you can switch on. Under Account → Preferences, More contrast raises every text colour in the product to at least 7:1 — WCAG's AAA threshold — including the semantic status and level colours, not just body text. Maximum contrast goes further and removes decorative background washes and translucency entirely.
• Colour-vision deficiency. Every semantic colour and the whole chart palette is checked against six computable colour-vision tests, including the separation between adjacent chart series. Colours that failed were replaced, not excused.
• Reduced motion. If your system asks for reduced motion, animation is switched off — including JavaScript smooth-scrolling, which the standard browser setting cannot reach.
• Charts are not the primary content. Every chart in the product carries a real data table with it, in the page. The table is the content; the picture is the enhancement.
• Guided tours do not trap you. Tour mode is deliberately non-modal: there is no backdrop, no focus trap, and the page underneath stays reachable.
• Target size. The help badge that appears on roughly three hundred controls has a 25-pixel target, above WCAG's 24-pixel minimum, while staying visually small.
• Focus is always visible, with a thicker outline in the high-contrast modes.
• Language and direction are set on the document itself for the language you are using, including right-to-left support.
• Layout is checked at 375, 768 and 1280 pixels wide, with no horizontal scrolling of the page itself.

Known exceptions — what does not meet the standard today

We are listing these because you deserve to know before you buy, not after.

1. Page titles do not change between screens. Every page reports its title as "LobiPlan". If you rely on the page title to know where you are, you cannot. (WCAG 2.4.2, Level A)
2. Error messages are not announced. When something goes wrong, the message appears on screen but is not announced by a screen reader, and it is not programmatically linked to the field that caused it. (WCAG 4.1.3 Level AA and 3.3.1 Level A)
3. There is no "skip to content" link. Keyboard and screen-reader users pass the whole navigation menu on every screen. (WCAG 2.4.1, Level A)
4. Some information is carried by colour alone. The four levels of the work hierarchy are distinguished on small chips by colour only. (WCAG 1.4.1, Level A)
5. Some things can only be done by dragging — moving cards on the Board, moving meetings on the calendar. There is no keyboard or single-pointer equivalent for those specific actions. (WCAG 2.1.1 Level A, 2.5.7 Level AA)
6. No screen reader has ever been tested against this product, and no keyboard-only walkthrough has been completed. We therefore cannot tell you how the rest of the product behaves with assistive technology. We are not going to guess.
7. A few faint text styles fall below 4.5:1, in about nine places where a transparency setting bypasses our colour system. The worst we have measured is 1.69:1. (WCAG 1.4.3, Level AA)
8. Live captions in LobiMeet video calls are produced by your own browser's speech recognition, not by us. They are best-effort, work best in English, and are not available in every browser. Do not rely on them as an accommodation — tell us what you need instead, and see below.

Exception 6 is the one that makes the other seven honest. Without it, this list reads as exhaustive, and you would be entitled to assume that everything not on it works. We do not know that, so we will not imply it.

What we are doing about it

In order, because a plan whose first item takes a quarter is a plan that does not start:

• First, and soon. Announce error messages properly and tie them to the field that caused them; set a real page title on every screen and announce navigation; add a skip-to-content link. These are exceptions 1, 2 and 3, they are the cheapest items on the list, and they matter most.
• Then. Add a shape to the level chips so colour is not the only carrier (exception 4); complete a keyboard-only walkthrough of the highest-traffic screens; give every drag a keyboard alternative (exception 5); close the remaining faint-text cases (exception 7).
• Then. Screen-reader testing on the flows that matter most — signing in, creating and completing work, reading the dashboard, running an approval, reading a financial statement, and cancelling a subscription.
• Only after that, a third-party audit and a formal conformance evaluation. An audit of a product with open Level-A failures buys an expensive list of things the first item would have fixed for free.

We will update the date at the top of this page whenever an item moves, and we will not remove an item from the list above until it is actually fixed.

We will not install an accessibility overlay or accessibility widget. They do not work, and here one would layer a generic contrast toggle over a colour system that is already solved and tested.

If something does not work for you

Write to bsimba6@gmail.com. Tell us what you were trying to do, what happened, and what you use — a screen reader, keyboard only, magnification, voice, whatever it is. A screenshot helps but is never required, and you never need to know the name of the problem.

What we promise:

• We will confirm we have your message within 2 business days.
• We will give you a real answer within 10 business days — what we found, whether we can fix it, and when. If a fix will take longer than that, we will say so and give you a date.
• While it is broken, we will do it for you. If something in LobiPlan is unusable for you, a person here will carry out the action on your behalf — including exporting all your data, cancelling your subscription, or closing your account. You do not have to fight the software to leave. This is not an aspiration: the tools to export a member's data and to close an account are already built and already operator-executable, and a subscription can be cancelled by hand.
• We will not ask you to prove a disability, and we will not ask you to explain why you need it.

We keep a dated log of what was reported, what we did, and when.

If you would rather not use email, tell us how you would prefer to reach us and we will arrange it. We do not publish a postal address today; not publishing one must never be the reason a barrier goes unreported, so ask and we will find a way that works for you.

If you are not satisfied with our response

You may complain to the Nova Scotia Human Rights Commission (humanrights.novascotia.ca). If you are a customer elsewhere in Canada, your provincial human rights commission can help.

We would much rather you came to us first. We are not going to hide that this route exists.

The law that applies to us

We are stating this because the common assumption is wrong in a way that would mislead you about your own position.

What binds LobiPlan today is human rights law, specifically the Nova Scotia Human Rights Act: we may not discriminate in the provision of a service on the basis of physical or mental disability, and we have a duty to accommodate short of undue hardship. It has no employee-count threshold and no phase-in date. A customer who cannot use LobiPlan because of a disability has a complaint available to them today, and being a small operation is a factor in remedy, not a defence.

What does not bind us today, whatever a vendor questionnaire may assume:

• The Accessible Canada Act applies to federally regulated entities — banks, telecoms, broadcasting, interprovincial transport, the federal government. We are not one.
• Ontario's AODA web-content requirement applies to designated public-sector organizations and to organizations with 50 or more employees in Ontario. We are neither.
• Nova Scotia's Accessibility Act sets a barrier-free target for the province by 2030, implemented through standards made by regulation. The standards in force to date do not target private-sector software.

We expect that to change, and we would rather build toward the standard now than retrofit against a deadline.

Formal notes

• Standard referenced: Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, W3C.
• Assessment method: self-assessment. Automated testing of colour, contrast, chart palette and motion built into our build pipeline and run against the code we publish; manual layout inspection at three viewport widths; an adversarial internal review of the colour system in July 2026. No third-party audit, no assistive-technology testing and no formal WCAG-EM evaluation has been performed.
• Scope — in: the LobiPlan web application at app.lobiplan.com and the marketing site at lobiplan.com.
• Scope — out: content produced by our customers inside their own workspaces; the Stripe payment pages and the Stripe customer portal, which are operated by Stripe; and the Plaid bank-connection screens, which are operated by Plaid. We have not assessed those and we will not imply that we have. ⚠ Note that the subscription-cancellation path runs through a page we do not control and have not assessed. That is exactly why the promise above — a person here will cancel it for you — is part of this statement rather than a courtesy.
• Feedback and accommodation: bsimba6@gmail.com.

Related: Terms of Service · Privacy Policy · How LobiPlan uses AI

Changes to this document

We will notify you in advance of material changes to this document. We update the date at the top whenever an exception is added, removed or reworded, and we treat a change in the product's behaviour without a matching change to this page as a defect.

Previous versions are available on request.

LobiPlan for organizations · LobiPlan for households · bsimba6@gmail.com