Ottawa compliance snapshot
The compliance stack behind an Ottawa website
Ottawa is a rare Canadian market where a marketing website routinely has to answer to a federal language regime, a municipal bilingualism policy and a provincial accessibility law at the same time. These are the published rules a build has to clear.
Legal duties that shape the build
Sources: Ontario.ca, How to make websites accessible and Completing your accessibility compliance report; Accessibility Standards Canada, CAN-ASC-EN 301 549:2024 clause 9; Official Languages Act s.22 and Accessible Canada Act (SC 2019, c.10), Justice Laws Canada.
Ontario businesses and non-profits with 50 or more employees, and designated public sector organisations, must make public web content published after 1 January 2012 meet WCAG 2.0 Level AA, with only success criteria 1.2.4 and 1.2.5 excepted. Source: Ontario.ca, How to make websites accessible.
Ontario businesses and non-profits with 20 or more employees file an accessibility compliance report every three years, and the current deadline is 31 December 2026. Designated public sector organisations file every two years. Source: Ontario.ca, Completing your accessibility compliance report.
Canada's adopted standard CAN-ASC-EN 301 549:2024 states at clause 9 that web pages must satisfy the five WCAG 2.1 conformance requirements at Level AA. That is a higher bar than AODA and it is the one federal work tends to reference. Source: Accessibility Standards Canada.
Under section 22 of the Official Languages Act, federal institutions must let the public communicate with and obtain services from head or central offices in either official language, and within the National Capital Region. Source: Justice Laws Canada.
The Accessible Canada Act sets that date and names information and communication technologies, and the procurement of goods, services and facilities, among its priority areas. Accessibility questions in federal bid documents trace back to it. Source: Justice Laws Canada, Accessible Canada Act (SC 2019, c.10).
Ottawa market and language demand
Sources: Statistics Canada, 2021 Census, knowledge of official languages, Ottawa (City); Ontario's French Language Services Act, designated areas; CanadaBuys small business procurement lens guidance; CBRE Scoring Tech Talent 2024 as cited by Invest Ottawa.
36.4 percent of City of Ottawa residents reported knowledge of English and French in the 2021 Census, down from 37.6 percent in 2016. An English-only site is invisible to a large slice of the local audience. Source: Statistics Canada, 2021 Census.
Ontario's French Language Services Act lists the City of Ottawa in full among its designated areas, where provincial government services must be available in French. Organisations delivering or bidding on those services are read against that expectation. Source: Ontario's French Language Services Act, designated areas.
CanadaBuys guidance sets a mandatory small business procurement lens for procurements with a contract value of $10,000 or more and less than $5 million, including option years and taxes. That is the band most first federal wins sit in, and your own website is usually the first thing that buyer opens. Source: CanadaBuys.
Ottawa recorded 51.7 percent growth in tech employment across that period, described as one of the highest among North American cities. Competing for that audience means competing against well-funded in-house web teams. Source: CBRE Scoring Tech Talent 2024, cited by Invest Ottawa.
Ottawa's technology base
Ottawa is not only a government town. Kanata North sits at the west end of the city and is described by Invest Ottawa as Canada's largest technology park, which is why so much of the local web brief involves cybersecurity, telecom, semiconductor and SaaS positioning rather than plain local services marketing.
The short version: in Ottawa, a website is a compliance artefact as much as a marketing asset. Budget for the French version and the accessibility testing at the start, because retrofitting both after launch costs more than building them in.
What a bilingual, accessible WordPress build includes
Six things we treat as non-optional on an Ottawa project, and why each one exists.
Template site versus compliance-ready WordPressHow the builds differ
Requirements referenced from Ontario.ca AODA guidance, Accessibility Standards Canada CAN-ASC-EN 301 549:2024 clause 9, and the Canada.ca design specifications published at design.canada.ca, which set mandatory design elements and content style for in-scope federal institutions.
| Feature | Typical template build | Dcrayon Ottawa build |
|---|---|---|
| Second official language | ||
| Accessibility target | ||
| Evidence for a buyer or auditor | ||
| Federal look and feel | ||
| Plugin policy | ||
| Forms and data path | ||
| Ownership at handover |
| Feature | Typical template build |
|---|---|
| Second official language | |
| Accessibility target | |
| Evidence for a buyer or auditor | |
| Federal look and feel | |
| Plugin policy | |
| Forms and data path | |
| Ownership at handover |
How an Ottawa WordPress engagement runs with Dcrayon
Four stages, each with a written output you keep whether or not the project continues.
- 1Free audit against the rules that actually apply to you
We review your current site against WCAG, page performance and the indexation of both language trees, then against the obligations you personally sit under: whether you cross the AODA fifty-employee line, whether you file an Ontario accessibility compliance report before the 31 December 2026 deadline, and whether the CAN-ASC-EN 301 549:2024 clause 9 bar applies because you sell to the federal government. You get the findings in writing at no cost and with no obligation.
- 2French and English page inventory agreed before design
We fix the page inventory in both languages, who supplies and approves the French, and how parity is held after launch. The City of Ottawa Bilingualism Policy expects publications addressed to the public in both official languages simultaneously, or in the language of the target group, and that standard is far cheaper to meet by planning the French pages now than by catching up on them later. This is where most bilingual projects quietly fail, because the English site keeps growing and the French one does not.
- 3Accessible build, tested on both language trees
Templates are built with focus states, contrast, target sizes and heading structure decided up front rather than patched later, and each template is checked as it is completed by keyboard-only navigation and a screen reader pass, with Core Web Vitals measured on the French tree as well as the English one. Where Canada.ca design specifications apply because an in-scope federal institution's content is involved, they are implemented as published rather than approximated in a theme.
- 4Handover with evidence a buyer or auditor can read
You receive the accessibility conformance statement, the remediation log and a plain-language maintenance guide, which is the material a bid team cites instead of asserting compliance. Launch maps redirects across both language trees and verifies analytics and search console on each, and the named lead who ran the audit stays with the site through core, theme and plugin updates, backups and periodic accessibility re-checks.
Honest about location
Remote delivery, French review and Ottawa working hours
Web development work from the Dcrayon portfolio
Recent website and CMS projects, with the brief, the approach and the measured outcome for each.
Ottawa WordPress questions, answered by Dcrayon
It depends on who you are. A private Ottawa business with no federal or provincial service role has no statutory duty to publish in French. The City of Ottawa's own Bilingualism Policy requires documents published by the City and addressed to the public to appear in both official languages, with publications made available in both languages simultaneously or in the language of the target group. Ontario's French Language Services Act lists the City of Ottawa in full among its designated areas, where provincial government services must be available in French. Commercially, Statistics Canada's 2021 Census recorded 141,560 Ottawa residents with French as their first official language spoken and 36.4 percent of residents with knowledge of both languages, so the case for a French site is usually market-driven rather than legal.
For an Ontario business or non-profit with 50 or more employees, Ontario.ca guidance says AODA requires public web content published after 1 January 2012 to meet WCAG 2.0 Level AA, excepting success criteria 1.2.4 and 1.2.5, and that deadline passed on 1 January 2021. If you supply the federal government or want to, the reference point is Canada's adopted CAN-ASC-EN 301 549:2024, whose clause 9 requires web pages to satisfy the WCAG 2.1 conformance requirements at Level AA. We build to the higher of the two that applies to you, and note where WCAG 2.2, published by W3C as a Recommendation dated 12 December 2024, adds criteria worth adopting early.
Your own site is often the first thing a federal buyer looks at, and an inaccessible one undercuts any accessibility claim in your bid. The Accessible Canada Act names procurement of goods, services and facilities as a priority area on the way to a barrier-free Canada by 1 January 2040. CanadaBuys guidance also sets a mandatory small business procurement lens for procurements with a contract value of $10,000 or more and less than $5 million, including option years and taxes, which is where most first federal wins sit. We give you a written conformance statement and remediation log so your bid team has something concrete to cite.
Yes, with care. The Canada.ca design specifications published at design.canada.ca set mandatory header, footer, typography, template and content style rules for in-scope federal institutions, and they describe design elements rather than a required publishing tool, so the platform itself is not the obstacle. What matters is implementing those rules faithfully in a WordPress theme rather than approximating them. If you are a supplier or an association rather than an in-scope institution, you are usually free to use your own brand, and we will say so instead of selling you compliance you do not need.
Because the plugin layer is where the risk concentrates: of the WordPress ecosystem vulnerabilities Patchstack disclosed for 2025, 91 percent were found in plugins and only six were in WordPress core. In Ottawa the consequence is commercial rather than theoretical. A federal buyer, a designated public sector body or a national association will ask what is installed, who maintains it and how quickly a patch reaches production, and a site carrying whatever a theme demo bundled has no credible answer to give. Every plugin is a standing maintenance commitment, so we add few, check each one has an active maintainer, and document the set.
Indian Standard Time runs nine and a half hours ahead of Eastern Daylight Time, so live calls sit in your morning and the Indian working day covers build and testing. French content is produced by professional translators and reviewed by a francophone reader before publication, never by a machine-translation plugin sitting on top of the English site. Your named lead is the same person throughout, and the first step is a free audit, so you can judge the quality of the thinking before any money changes hands.
Request a free website audit
Send us your URL and we will come back with an accessibility, bilingual-readiness and performance review in writing. No cost, no obligation.
Get a free audit of your Ottawa website
Tell us your URL and who your site has to satisfy: customers, an AODA compliance report, a federal buyer, or all three. You get a written review of what passes and what does not, from a named lead who stays with the project.





