Accessibility

Last updated & effective: September 10, 2026

The short version

We build Listing Launchpad against WCAG 2.2 Level AA.
We do not claim to have reached it everywhere. This page names what is in place and what is not.
This is a self-assessment — our own review of our own code. It is not a third-party audit and not a certification.
If something in the product blocks you, write to info@listinglaunchpad.com. A person reads it, and we aim to reply within two business days.
Anything on this site is available in another format on request, at no charge. See Accessible formats.

The standard we measure against

We use the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, as the target for the marketing site, the signed-in product and the public pages agents publish through it. Where a specific criterion is named on this page, it is because we measured against it rather than assumed it.

We aim at 2.2 rather than the older 2.0 because 2.2 is the current version, and its newer criteria — visible focus, target size, dragging alternatives — are exactly the ones a dense, form-heavy tool like this one gets wrong.

What is in place today

A visible keyboard focus indicator on every control. Buttons, links and anything given a tab stop draw a two-pixel outline on keyboard focus. Its colour is chosen per theme so it clears the 3:1 that WCAG 1.4.11 asks for on all four backgrounds the app paints, including the cream document pages.
Reduced motion is honoured. If your system asks for less motion, animations and transitions are neutralised across the app — including their delays, so nothing is left invisible waiting for a reveal. Loading spinners keep turning on purpose: a frozen one reads as a broken screen.
Text contrast is computed, not eyeballed. Colour pairs are measured, and the palette carries separate ink values for the lighter surfaces where the standard pair would fall short. On agent-branded pages the outline colour is calculated against that agent’s own brand colour, because a fixed one cannot be legible on every hue.
Form fields have real labels. Every label points at the control it names, and grouped controls (radio sets, checkbox sets) are announced as a labelled group rather than as loose inputs.
Images carry alternative text. Meaningful images are described; decorative ones are marked as decorative so a screen reader skips them instead of reading a filename.
Status that only appears visually is also announced. The listing workspace saves as you type and has no Save button, so the save state is published to assistive technology through a live region rather than living only in a small chip.
Records that used to be click-only are keyboard-operable. Client cards, lockbox rows and professional contacts can be reached with Tab and opened with Enter or Space.
The brochure PDF is tagged. Exports carry a real document structure — headings, paragraphs, and photographs with alternative text naming the room they show — along with the document’s language and title. A screen reader reads the brochure in order rather than guessing an order from where things sit on the page, and the page number and address repeated at the foot of every page are marked as decoration and skipped. The same descriptions travel into the PowerPoint export, so they survive an import into Canva. We have not put the file through a formal PDF/UA conformance checker.
Documents can be filed without a mouse. Every file and folder in the document manager opens from the keyboard, and each row carries a menu button holding the same actions right-click gives — move, star, share with the client, delete. Dragging is one way to file a document, not the only one.
The product does not use native browser alert boxes for confirmations, so focus and reading order stay inside the page rather than jumping to a dialog the page does not control.
Every page declares its language and uses ordinary headings, lists and landmarks, so heading navigation works.
A skip link opens every page that has navigation before its content — the marketing site, the legal documents, the listing workspace, the rest of the signed-in app, and the public property pages. Press Tab once on arrival and it appears in the top-left corner; Enter jumps past the chrome to the content. In the workspace that is the account rail, the top bar and the whole section sidebar in one keystroke.

Where we fall short

These are known, current, and written down so you do not have to discover them yourself.

Generated videos have no captions. They carry music and on-screen text rather than speech, but there is no caption track and no described alternative.
Photo editing is inherently visual. The image tools rely on seeing the result, and we do not have a non-visual path through them.
We have not tested with assistive-technology users. The work above is structural and measured; it is not the same as watching someone use a screen reader to file a listing. We would rather say that than imply a level of validation we have not done.

The pages you publish

Agents use Listing Launchpad to publish property pages, open-house sign-in screens, client portals and forms that members of the public fill in. Those pages are read by buyers, sellers and tenants, so their accessibility matters more than the app’s own.

The public templates carry the same focus, contrast, labelling and reduced-motion behaviour described above.
Property photos use the name you give them as their alternative text, so a descriptive photo name (“south-facing kitchen”) becomes a useful description, and a camera filename does not.
Public forms — open-house sign-in, rental applications, client intake — use labelled fields and can be completed with a keyboard.

You remain responsible for the content you publish. If you serve the public in Ontario, the duty to accommodate under the Human Rights Code applies to your practice regardless of your size, so plain descriptions and named photos are worth the minute they cost.

Parts we do not control

Some of what you see is served by another company, and their accessibility is theirs:

Payment is handled on Stripe’s own checkout.
Maps on public property pages are a Google embed.
Board and MLS® systems. Our browser extension types into the board’s own forms. It does not change how those forms behave, and it cannot make an inaccessible board system accessible.
Email. How our messages render is finally up to your mail client. We send real text with real headings rather than an image of a message, which is the part that is ours to get right.

If one of these blocks you, tell us anyway. We can usually give you another route to the same outcome — including doing it for you.

Accessible formats and support

Anything we publish — this page, the Terms, the Privacy Policy, an invoice, your own listing data — can be provided in another format that works for you, at no extra charge. Large print, plain text, a structured document, or read out to you over a call. Ask at info@listinglaunchpad.com and tell us the format that helps; we will agree on it with you rather than guess.

If a task in the product is not usable for you, we will do it with you or for you while the underlying problem is fixed. That is not a favour and you do not need to justify the request.

Tell us where it breaks

Reports of specific barriers are the most useful thing we receive, and they change what gets built next.

Email info@listinglaunchpad.com, or use Help & support inside the app.
What helps: the page or screen, what you were trying to do, and what happened instead. If you use assistive technology, naming it helps us reproduce the problem — but a report without any of that detail is still worth sending.
What we do: we aim to acknowledge within two business days, tell you whether we can fix it and roughly when, and give you a way to get the task done in the meantime.
If our answer is not good enough, reply and say so. It escalates to the person who runs the company, because it is a small company.

Where the law sits

We would rather state this accurately than imply an approval we do not hold.

Ontario (AODA). The Integrated Accessibility Standards Regulation requires public websites to meet WCAG 2.0 Level AA, and that requirement applies to organizations with 50 or more employees. Cekan Holdings Ltd. is well under that threshold, so it does not bind us, and we do not describe ourselves as AODA compliant.
The Ontario Human Rights Code applies to organizations of every size. Its duty to accommodate people with disabilities, to the point of undue hardship, is the reason the work on this page happens regardless of employee count.
Federally. The Accessible Canada Act applies to federally regulated entities. We are not one.

None of this limits any right you have under applicable law. Where the law requires more than this page promises, the law governs.

Keeping this page honest

This statement describes the product as it is on the date above, not a plan. When we close one of the gaps listed here, it moves out of that section; when we ship something that introduces a new barrier, it gets added. If you find a claim on this page that is not true of the product you are using, that is itself a bug worth reporting, and we will fix the page or the product.

Contact

Cekan Holdings Ltd. · Hamilton, Ontario, Canada · info@listinglaunchpad.com

Listing Launchpad is a product of Cekan Holdings Ltd. · listinglaunchpad.com