Skip to content

Edition 01 · 2026 · Toronto

A computer that listens.
A hand when the keyboard is in the way.

EasyAccess is a voice-first agent that operates a computer on your behalf. Ask it to open an app, read a page aloud, draft a document, fill a form — it hears you, acts, and narrates what it is doing. Built for people for whom the mouse and keyboard are friction, not a tool.

The cockpit

A window into what the agent is thinking.

Every EasyAccess session opens in a small cockpit window. You see your own voice, the agent's transcript, and a running account of what it is doing — each step visible before it happens, each step logged after. Nothing silent, nothing invisible.

  • Hear yourself. Live waveform from your microphone.
  • Hear the agent back. Narrated intent before every action.
  • See the trail. A plain-language log of actions taken.

What it does

A small set of capable things, done well.

EasyAccess deliberately does less than a full-stack AI assistant and more than a voice shortcut. It is a hand on the keyboard — one that listens, waits, and explains itself.

  1. 01

    Hears plain speech.

    You talk to EasyAccess the way you'd talk to a capable assistant sitting next to you. No command syntax, no voice-menu tree. English to start, with French coming alongside pilot deployments.

  2. 02

    Operates the computer, not a specific app.

    Opens apps, clicks links, fills fields, reads pages aloud, drafts short documents. It works across the system the way a person does — not inside a single walled garden.

  3. 03

    Narrates what it's doing.

    You always hear what the agent is about to do before it does it, and what it did after. No silent actions. You can interrupt or correct at any point.

A position

Consent is a feature, not a setting. The agent does nothing it has not told you it is about to do — and afterwards, nothing it cannot explain in plain language.

EasyAccess principle № 01

Principles

What we will and will not do.

Assistive technology lives or dies on trust. These are the stances we are prepared to defend in front of a pilot partner or a regulator.

01

Consent is a feature, not a setting.

The agent does nothing it has not told you it is about to do. You can pause, redirect, or reverse at any point. What the agent does is logged plainly and readable in your own language.

02

Calm by default.

No celebratory sound effects, no confetti, no emoji. Interfaces for assistive use should be quiet. The accessibility audience tells us this, repeatedly; we listen.

03

English and French, first.

Canadian pilot deployments get both official languages on day one. Additional languages follow real deployments, not a marketing page.

04

Honest about what it cannot do.

The agent is not a safety-critical device. It will not file your taxes, approve a purchase, or act on a regulated instrument. Where it stops, we tell you in advance, not after.

A laptop on a quiet wooden desk, lit by a nearby window — a calm workspace viewed from above
Figure III·A quiet workspace

What a pilot looks like

Six months, end to end.

We publish the pilot arc in advance because nobody should sign a six-month contract wondering what month three looks like. Here is the rough shape; every deployment adjusts the edges around it.

  1. Month 01

    Fit

    We meet your team, map the accessibility obligations on your plate, and decide which five to twenty users go first.

  2. Month 02

    Onboard

    Device provisioning, voice calibration, and in-person or remote training with the first cohort of users.

  3. Month 03

    In flight

    Daily use begins. A named contact on our end is available for questions and adjustments. Weekly check-ins.

  4. Month 04

    Tune

    Pattern of use stabilises. We tune the command vocabulary and agent behaviours to what your team actually asks.

  5. Month 05

    Expand

    Optional: broaden the pilot to an additional cohort. Second-language or additional role coverage reviewed here.

  6. Month 06

    Decide

    Findings report with usage data, qualitative interviews, and a plain-language summary. Annual contract or exit.

Writing

Plain-English notes on accessibility in Canada.

We write about AODA, the Accessible Canada Act, and where voice-first technology helps (and where it does not). Working notes from a team building accessible software, with no hype and no inspiration framing.

Pilot

If you run a Canadian organisation that takes accessibility seriously, we want to hear from you.

We are running a small number of six-month pilots through 2026 with Canadian nonprofits, municipalities, and service providers with AODA obligations. Pilots include onboarding, in-person training, and a named contact for the duration.