Government Website Accessibility in Canada: 2026 Guide

Government website accessibility in Canada is governed by a mix of federal regulations, provincial accessibility laws, government policies and technical standards. There is no single WCAG rule that applies to every public sector website in every jurisdiction. The applicable requirement depends on who owns the website, where the organization operates, what type of content is involved and when the page or application was created or updated.

For a new government or public sector web project, WCAG 2.2 Level AA is a sensible technical target because it includes newer accessibility criteria and remains backward compatible with WCAG 2.1 and 2.0. That target does not replace a jurisdiction specific legal review. Some Canadian rules still name WCAG 2.0, while others refer to WCAG 2.1, a broader ICT standard or the most current WCAG version.

This article provides general information, not legal advice. Organizations should confirm their scope, exceptions and deadlines with the responsible authority or qualified counsel.

What government website accessibility means

An accessible government website lets people obtain information and complete essential tasks using different devices, input methods and assistive technologies. This includes residents who use screen readers, keyboard only navigation, magnification, voice control, captions or alternative formats.

The work goes beyond colour contrast and image descriptions. It also covers the structure of content, forms, error messages, focus order, authentication, documents, video, mobile layouts and complete service journeys. A page may pass an automated scan and still prevent someone from renewing a permit, applying for a benefit or finding public health information.

Is WCAG a law in Canada

WCAG is a technical standard, not a statute on its own. It becomes mandatory when legislation, a regulation, a government directive, a contract or another binding instrument incorporates it. The Web Content Accessibility Guidelines are published by the World Wide Web Consortium, or W3C, and organize accessibility around four principles: content should be perceivable, operable, understandable and robust.

WCAG has three conformance levels. Level A addresses foundational barriers. Level AA includes Level A and adds criteria commonly used in public policy and procurement. Level AAA is the highest level, but W3C does not recommend requiring Level AAA for an entire website because some content cannot satisfy every AAA criterion.

Federal government website accessibility requirements

The Accessible Canada Act applies within federal jurisdiction, including the Government of Canada and other federally regulated entities. It does not automatically govern every provincial ministry, municipality or private organization in Canada.

In December 2025, the federal government published amendments to the Accessible Canada Regulations for digital technologies. For federal public sector organizations, the official guidance sets the following milestones:

• December 5, 2027: new and updated public facing and employee facing web pages, including web applications, must meet the applicable requirements in clauses 4 to 7 and 9 of CAN/ASC EN 301 549, to the extent required by the regulations.
• December 5, 2027: an accessibility statement for regulated web pages is required and must then be updated every 12 months.
• December 5, 2027: employees involved in developing, maintaining or purchasing regulated digital technologies must receive accessibility training, with refreshers at least every three years.
• December 5, 2028: procurement related conformity assessments and gap analyses apply in the situations described by the regulations; requirements for new or updated digital documents and certain mobile applications also begin. The federal requirements are broader than a simple WCAG checklist because CAN/ASC EN 301 549 addresses accessibility across information and communication technology. During the transition, federal departments have been directed to maintain public facing websites and device based mobile applications to at least the WCAG 2.0 baseline and to plan for the new regulatory standard. Exact coverage and exceptions should be checked in the regulations and current federal guidance.

How provincial requirements differ

Provincial obligations are not uniform. The following comparison focuses on selected jurisdictions with official web requirements or public sector standards. It is a starting point, not a complete legal inventory for every organization or service. Provincial requirements vary by jurisdiction. Ontario's AODA regulation names WCAG 2.0 AA; Manitoba's Accessible Information and Communication Standard names WCAG 2.1 AA; Québec's SGQRI 008 3.0 uses WCAG 2.1 with selected WCAG 2.2 criteria; British Columbia's government web policy refers to the most current WCAG AA; Alberta uses WCAG based government digital experience standards; and Nova Scotia's information and communication standards were still developing as of the review date.

Ontario requirements deserve special attention

Ontario's rule is often summarized too broadly. Under section 14 of the Integrated Accessibility Standards Regulation, the Government of Ontario and Legislative Assembly have requirements for both internet and intranet websites. Designated public sector organizations and large organizations have public internet website requirements. The regulation names WCAG 2.0 Level AA and contains scope rules, schedules and exceptions. For covered public websites, Ontario guidance notes exceptions for live captions and prerecorded audio descriptions in specified cases.

Using WCAG 2.2 AA on a new Ontario project can be a prudent development choice because WCAG 2.2 conformance also satisfies WCAG 2.1 and 2.0. However, the project team should still map its evidence to the version and exceptions named in Ontario's regulation.

What WCAG 2.2 AA adds to a modern project

WCAG 2.2 builds on WCAG 2.1 and adds criteria that are especially relevant to modern digital services. Examples include visible keyboard focus, focus that is not hidden by sticky interface elements, minimum target sizes, alternatives to dragging movements, consistent help and more accessible authentication.

A practical public sector specification should address at least:

• semantic page structure, descriptive headings and meaningful link text
• text alternatives for informative images and accessible names for controls
• keyboard access with a logical focus order and no keyboard traps
• sufficient contrast, text resizing and reflow without lost content or function
• captions, transcripts or other required alternatives for multimedia
• clear form labels, instructions, validation and recoverable error messages
• accessible PDFs and office documents, or an equivalent accessible format
• plain language, predictable navigation and consistent help
• accessible authentication that works with password managers and copy and paste

How to plan an accessible government website

1. Confirm jurisdiction and scope. Identify the organization, governing statute or policy, website type, audience, employee facing content, third party services and publication dates.
2. Write accessibility into procurement. Name the required standard and version, evidence format, test coverage, remediation process, acceptance criteria and maintenance responsibilities.
3. Design complete journeys. Test the full task, not only individual screens. Include account creation, authentication, search, forms, file uploads, payment, confirmation and error recovery where relevant.
4. Use more than automated testing. Automated tools can identify some code level issues, but manual keyboard review, screen reader testing, zoom and reflow checks, and testing with people with disabilities reveal barriers that scans miss.
5. Document decisions and evidence. Keep issue logs, test results, exceptions, alternative access methods, vendor reports and sign offs. Federal procurement rules will require conformity assessments in specified cases from December 5, 2028.
6. Publish an honest accessibility statement. Describe the standard used, known limitations, feedback channels and alternative ways to access information or complete a task. Do not claim full conformance without evidence covering the full stated scope.
7. Maintain accessibility after launch. New content, PDFs, templates, software updates and third party components can introduce barriers. Assign ownership, train contributors and schedule regression testing.

Why automated scans are not enough

Automated tools are useful for repeatable checks, but they cannot determine every accessibility issue. A tool may detect missing alternative text, for example, but it cannot reliably decide whether the text communicates the image's purpose. It may identify a form control without a programmatic label but miss confusing instructions or an unusable service flow.

A defensible review combines automated checks with manual inspection and task based testing. The strongest programs also involve people with disabilities during research, design and validation. This approach supports accessibility as an operational practice rather than a one time launch certificate.

Accessibility statements should be specific

An accessibility statement should help users understand what they can expect and how to get assistance. It should identify the website or service covered, the standard or target used, the date of review, known limitations, contact methods and available alternatives. Federal organizations subject to the amended regulations will have detailed statement requirements and annual updates on the applicable timeline.

Avoid unsupported claims such as “fully accessible,” “AODA certified” or “100% compliant.” Accessibility is not established by a widget or a single automated score. Use evidence based wording that matches the actual audit scope.

Build accessibility into the project from the start

Government website accessibility is easier to manage when it is part of discovery, content design, component development, procurement and quality assurance. Retrofitting a complex service after launch can create avoidable cost and can leave residents without equal access while repairs are underway.

WebNeuro designs and develops websites and digital services for public and regulated organizations. A project can be scoped around the applicable jurisdiction, an evidence based WCAG target, content and document requirements, manual testing, and a clear remediation record. Legal applicability and final compliance conclusions should remain with the responsible organization and its advisers.

Discuss an accessible government website project with WebNeuro.

Official sources and further reading