Skip to main content

Websites built for Canadian rules.

Accessibility for Ontario, consent for commercial messages and French for Quebec customers are part of the build, not an afterthought.

10
Products built in-house
12
Web projects in the portfolio
04
Site languages: EN, TR, ES, DE
UTC+3
Overlaps US mornings and the full EU workday

A Toronto company that sells across Canada meets three sets of rules on one website: Ontario's accessibility law, the federal anti-spam law and, the moment it sells to Quebec, French. Each is cheaper to build in than to retrofit, so we ask about them in the first conversation.

Accessibility under AODA

Ontario's AODA expects public websites of larger organizations to meet WCAG 2.0 level AA, and the standard is a reasonable target for any site. We test keyboard use, focus order, contrast, form labels and error messages as part of the build, and we say in the handover what was checked and what was not. Whether your organization is covered is a question for your counsel.

Consent for commercial messages

CASL requires consent before a company sends commercial electronic messages, and the sender must be able to show it. Newsletter forms, WhatsApp opt-ins and any automated follow-up we build record who agreed, when and to what, and every message carries a working way out. That record lives in your admin panel where your staff can export it.

Selling into Quebec

Quebec's language law expects commercial websites that serve its consumers to be available in French. A machine-translated French page costs more in trust than it saves in time. We write the French copy with a native reviewer and set up its own address, so the English and French sites do not compete with each other in search.

Same clock as New York

The clock is New York's: seven hours behind Istanbul in summer, eight in winter. The overlap is the morning, roughly 9 to 11 a.m. Toronto time, and the table below gives the full picture.

Time difference with Toronto

Toronto hours against Istanbul

Time in the cityIstanbul, summerIstanbul, winterOn our side in summer
08:0015:0016:00Working hours, team online
10:0017:0018:00Working hours, team online
12:0019:0020:00Evening, handoff notes
15:0022:0023:00Offline, reply next morning
17:0000:00 (next day)01:00 (next day)Offline, reply next morning

How a project runs

From first conversation to launch

Read the full process
  1. Discovery

    We document the business goal, audience, available material, and technical constraints.

  2. Scope

    Pages, features, priorities, responsibilities, and review criteria are written down.

  3. Design

    We establish the interface, component rules, and a CSS design system when the project needs one.

  4. Development

    We implement the approved interface and connect the required panels, CRM functions, or messaging tools.

  5. Quality review

    We review mobile behavior, performance, core accessibility requirements, and technical SEO.

  6. Launch

    The approved release goes live with the agreed support period and content handoff.

Technology used in this work

  • CSS Custom Properties
  • Design Tokens
  • Next.js
  • TypeScript
  • Supabase
  • PostgreSQL
  • GSAP
  • Lenis

Frequently asked questions

Does the site have to be bilingual?

Only if you sell to consumers in Quebec, or want to. We can start English-only and add French later, provided the structure leaves room for it. We build it that way by default.

Can you meet WCAG 2.0 AA?

We build to a documented checklist that covers keyboard use, focus, contrast, labels and errors, and we list what was tested. A formal audit by a third party is a separate engagement.

Do you invoice in Canadian dollars?

Currency and invoicing terms are agreed in the contract. Raise it with the first brief.

Tell us what you need built.

Write the business, the market you sell to and what a visitor should be able to do. We reply with the questions that settle scope.

Chat