If you can say it,you can ship it.
The front door is a sentence. Ask by , read the answer in words, then the change behind the same approval gate — no dense grid to cross first.
Built for how people actually work.
Ad platforms are dense grids designed for a mouse, a big screen and a lot of practice. Offloda's primary interface is a conversation — which removes most of that barrier instead of bolting a workaround onto it.
Conversation first, not a grid
The main way to use Offloda is to type or say a sentence. No drag-and-drop, no forty-column tables, no nested dialogs to cross before anything happens.
Your assistive stack comes with you
You drive Offloda from Claude, ChatGPT or any MCP client — so the dictation, screen reader, switch access, braille display or system zoom you already use with those apps keeps working. Nobody has to learn a new surface to be accommodated.
Dictation is a first-class path
Intent is expressed as a plain sentence, so speaking it isn't a workaround — it's the normal way in. And because every write is read back as a diff first, a dictation error surfaces before it costs anything.
Plain-language output
Answers come back as sentences, not dashboards — linear, readable text is the friendliest thing you can hand a screen reader. Ask for it without the jargon and you get it without the jargon.
Contrast measured, not guessed
Every text and background pair in the design system is computed against the WCAG contrast formula from the tokens themselves. Primary copy holds between 7.8:1 and 18:1 across the whole page — AAA at its worst point.
Motion you can switch off
Turn on “reduce motion” in your operating system and the animated hero holds a still frame, the chat demos jump to their final state, transitions collapse and smooth scrolling stops. There's no separate setting to find.
A palette that earns its contrast.
The site and the app run on one continuous gradient, which makes contrast a moving target rather than a fixed pair of hex codes. So the palette is defined by measured ratios instead of by taste: a darkening veil rides the bottom two-fifths of the page, primary copy stays pure white, the primary button's ramp stops where white type still reads, and accent type switches to a sunrise-white set exactly where the vivid gradient would lose legibility.
The numbers beside this are computed from the design tokens by a script in the repo — so they can be re-checked, and corrected, whenever the palette moves.
- Primary text 7.8:1 to 18:1 against the page — WCAG AA asks 4.5:1
- Every stop of the primary button's gradient carries its white label at 5:1 or better
- In the approval diff, every line carries an explicit +, ~ or − sign as well as its colour
- Keyboard focus is a 2px white outline — 7.8:1 against the page at its worst
- The white header and footer are translucent over the page, so they're measured against that composite rather than against white — 4.6:1 at their worst
Computed from the live design tokens, not eyeballed. WCAG 2.2 asks 4.5:1 for body text, and 3:1 for large text and focus indicators.
Worst case across the whole page gradient, darkening veil included. Re-run after any palette change.
The strategist and the operator are the same person now.
Most marketing teams split in two: the people who decide what should happen, and the people who know which screens to click. That split is a skills barrier — and for anyone who finds those screens hard to operate, it's an accessibility barrier wearing a job title.
Say the strategy
“Move the Display budget into Shopping and add last week's waste terms as negatives.” One sentence, spoken or typed, with no tour of three consoles first.
Read the diff
Offloda turns it into an exact, line-by-line change and stops. Nothing has been applied, so nothing has to be undone — and the plan can be read aloud, or read by a screen reader, before anyone commits to it.
Approve it yourself
One approval executes every step across every connected platform, logged. The person with the judgement ships the change instead of handing it to whoever is fluent in the interface.
The standards we build to.
We say “build to” on purpose. Conformance is something you re-earn on every release, not a badge you win once — so here's the target, and below it, the honest state of it.
WCAG 2.2 Level AA
The W3C's Web Content Accessibility Guidelines, version 2.2 — a Recommendation since October 2023 — at Level AA, the level regulators worldwide point at. It's our working target for this site and for the Offloda app.
EN 301 549 · European Accessibility Act
The European standard for accessible ICT, harmonised with WCAG at Level AA. It's the technical yardstick behind the European Accessibility Act, and the one EU buyers ask about in procurement.
Section 508 · ADA (United States)
US federal procurement under Section 508 incorporates WCAG at Level AA. Title III of the ADA sets no codified technical standard for private websites, so WCAG 2.2 AA is the benchmark the Department of Justice and the courts keep pointing back to.
AODA · Accessible Canada Act
Ontario's AODA requires WCAG 2.0 Level AA — excluding live captions and pre-recorded audio description — of large private organizations. We're a Canadian company; the Accessible Canada Act sets the federal frame we work inside.
Accessibility statement
Offloda Labs Inc. is working to make offloda.ai and the Offloda application usable by as many people as possible — including people using screen readers, dictation, keyboard-only navigation, magnification and reduced-motion settings.
Conformance status
Our target is WCAG 2.2 Level AA. We consider this site partially conformant with that target: most of it meets the requirement, and the specific gaps we know about are listed below. We won't describe ourselves as fully conformant, or publish an Accessibility Conformance Report, until an independent audit says so.
What's in place
- Semantic landmarks, a skip-to-content link, and a visible keyboard focus ring on every interactive element.
- Contrast computed from the design tokens rather than judged by eye, with the worst case across the page gradient treated as the number that counts.
- Full prefers-reduced-motion support: the animated hero holds still, the chat demos render their end state, transitions collapse and smooth scrolling is disabled.
- Text that reflows without a horizontal scroll down to phone width, and no content that needs hover to be reachable.
- Plain-language answers as a product default — the same output that makes the tool approachable also makes it readable aloud.
Known gaps, as of 13 September 2026
- The smallest muted meta text on the page gradient floors at about 4:1 — clear of the 3:1 large-text threshold everywhere, but under the 4.5:1 body-text one at its smallest sizes. Next on the list.
- The pink accent used for hover states and eyebrow chips inside the white header and footer sits between 3.8:1 and 4.1:1 on the backgrounds it actually lands on — clear of the 3:1 large-text bar, under the 4.5:1 body one.
- The animated hero backdrop is decorative and hidden from assistive technology. It carries no information, so it has no text alternative — if you think it should, tell us.
- Product screenshots carry alt text describing what the screen shows, but a dense dashboard is summarised rather than transcribed cell by cell.
- Testing so far is internal: keyboard traversal, reduced-motion behaviour, reflow, and contrast maths against the tokens. We haven't yet commissioned a third-party audit or completed a full assistive-technology test pass — and we won't claim conformance we haven't verified.
The parts we don't control
Offloda is driven from an AI client you choose — Claude, ChatGPT or another MCP-capable client. Those surfaces have their own accessibility behaviour and their own statements, and the confirmation step that approves a change is a control in that client rather than in our interface. Our side of the bargain is that everything we send into those surfaces is linear, labelled text.
Tell us where it breaks
If something here or in the app is hard or impossible to use, email hello@offloda.ai with the page, the assistive technology you were using, and what happened. We aim to reply within one business day and to tell you what we're going to do about it — including when the answer is “not soon”.
Last reviewed: 13 September 2026.
The part they didn't expect.
“Wow. It's the first time I truly understand what is going on in our marketing campaigns with such detail.”
“I just cleared my weekly account checklist by 11am on Monday. I might have to find some new clients to stay busy.”
“I audited our site and fixed 3 issues on Search Console and Key Events missing in Google Analytics that I did not know were missing.”
Accessibility questions
Is Offloda usable with a screen reader?
The surface you drive Offloda from — Claude, ChatGPT, your editor — is where a screen reader does most of its work, and a text conversation is about the friendliest thing you can hand one. Our own web app is built with semantic landmarks, labelled controls and a visible focus ring, but we haven't finished a full assistive-technology test pass, so we won't tell you it's certified. If something breaks, it goes to the top of the list.
Can I run campaign work entirely by voice?
The Offloda half, yes: dictate the request into your AI client, have the plan and the diff read back, then approve. The approval itself is a control in that client rather than in our interface, so what it takes to activate depends on that client — every major assistive stack can, and nothing applies until it happens.
Do you support reduced motion?
Yes, from the operating-system setting, with no separate toggle to find. With “reduce motion” on, the hero canvas holds a still frame instead of animating, the chat demos render their final state immediately, CSS transitions and animations collapse, and smooth scrolling is turned off.
Which standard do you actually target?
WCAG 2.2 Level AA, as the single technical target. Section 508, EN 301 549 and the AODA all resolve to WCAG at Level AA, so building to the newest version covers the regulatory frames our customers are held to — rather than us maintaining four checklists that mostly say the same thing.
Does the white-label portal our clients see inherit all of this?
It's the same application under your brand, so the structure, the focus behaviour and the reduced-motion support come with it. The colours don't: once you set your own palette, contrast becomes your call. The branding settings show you the exact hex values you've chosen so you can check them — and we're happy to check them with you.
Do you have a VPAT?
Not yet. We'd rather publish an Accessibility Conformance Report after an independent audit than self-certify one now. If you need documentation for a procurement process, get in touch and we'll tell you exactly where we stand, in writing.
Tell us where it breaks.
The page, the assistive technology, and what happened — specifics get fixed. We aim to reply within one business day.