Accessible virtual tours: how WCAG and AODA apply to 360

The short answer is yes. A 360 photo virtual tour can be made accessible, and when it is built to the right standard it serves the people who need it most: visitors with low vision, limited mobility, or anxiety about an unfamiliar building, who want to know what they are walking into before they go. The standard that matters in Canada is WCAG 2.0 Level AA, and an accessible tour is one that has been built against it from the start rather than patched at the end. Below is what that involves, how the rules apply, and why a clear accessibility statement keeps you moving through procurement.

What WCAG 2.0 AA is, and why Canadian rules point to it

WCAG stands for the Web Content Accessibility Guidelines, published by the World Wide Web Consortium. Version 2.0 organizes accessibility around four principles: content must be perceivable, operable, understandable, and robust. Each principle has testable success criteria sorted into three conformance levels, A, AA, and AAA. Level AA is the practical bar that almost every public body and large organization is measured against. It is the level Canadian regulations have historically referenced, which is why a buyer who asks whether your tour is accessible is, in nearly every case, asking whether it meets WCAG 2.0 AA.

How the AODA applies

In Ontario, the Accessibility for Ontarians with Disabilities Act sets accessibility requirements through its Integrated Accessibility Standards Regulation. The information and communications standard requires Ontario public-sector organizations and large private and non-profit organizations to make their public-facing web content conform to WCAG 2.0 Level AA. A virtual tour that lives on a covered organization's website is web content, so it falls inside that obligation. If a municipality, college, or large institution embeds a tour, that tour is expected to clear the same AA bar as the rest of the site. Other provinces have their own accessibility legislation moving in the same direction, and the federal Accessible Canada Act applies to federally regulated bodies, so AA is the common reference point across the country, not just in Ontario.

What an accessible 360 tour actually includes

Accessibility is not a single feature you switch on. It is a set of decisions baked into how the tour is built. A tour we build to WCAG 2.1 AA includes the things below.

• Keyboard operability. Every action a mouse can do, a keyboard can do too. You can move between scenes, open hotspots, and reach controls with the Tab and arrow keys, with a visible focus indicator so you always know where you are.
• Captioned and labelled hotspots. The clickable points that carry a tour are given clear text labels and, where they open media, captions, so they are not just unlabelled dots that a screen reader skips over.
• Sufficient contrast. Controls, labels, and text meet the AA contrast ratios so they stay legible for people with low vision and in bright conditions.
• A navigable structure. Scenes, menus, and controls are exposed in a logical order with proper names and roles, so assistive technology can announce them and move through them predictably.
• Alternative text and descriptions. Images and scenes carry meaningful text alternatives, and key views get written descriptions, so the content is available to someone who cannot see the panorama.
• A no-JavaScript fallback. When scripting is blocked or fails, the page still presents the tour's images and information rather than a blank frame, so the content does not disappear behind a broken viewer.
• Respect for reduced motion. Automatic panning and transitions are dialled back or stopped for visitors who set a reduced-motion preference, which matters for people sensitive to movement.

The result is a tour that works the way the rest of an accessible website works. You can read more about our approach on the accessibility page, and if you are new to the format, what a 360 virtual tour is sets the groundwork.

Accessibility is not a layer you add at the end. It is decided when the tour is structured, which is exactly why it has to be planned in from the first capture.

Pre-visit access and wayfinding

An accessible tour does more than satisfy a checklist. For a public facility, it is a genuine access tool. Someone who uses a wheelchair can see the entrance, check for steps, and find the accessible route before leaving home. A parent can show a child the space ahead of a first visit. A person with sensory sensitivities can preview a busy lobby on their own terms. This pre-visit access lowers the anxiety and uncertainty that keep people away, and it does practical wayfinding work: where the doors are, where reception sits, where the elevator is. That is real value for a counter, a clinic, a campus building, or a community centre, and it is exactly the kind of service public-sector buyers are looking for. See how this fits the public sector, and specifically municipal facilities and education.

Why procurement teams ask for an accessibility statement

When a public body buys anything that goes on its website, the accessibility obligation is theirs. A purchasing or communications team has to be able to show that what they bought meets WCAG 2.0 AA, so they ask suppliers to say, in writing, what was built and to what standard. An accessibility statement is that document. Ours describes the conformance target, the features included, and any known limitations, in plain language a reviewer can attach to a file. It is what lets a procurement officer tick the box honestly rather than taking a vendor's word for it.

We are careful here. We build to WCAG 2.1 AA and we will state exactly what each tour includes, but we do not claim a certification we do not hold, and conformance always depends on the final embed and the surrounding page. We hold ISN registration for supplier compliance; we do not hold COR or SECOR. What we offer is honest, documented work against a clear standard, which is what a serious buyer actually needs.

It works on a phone too

Accessibility and mobile go together. The tours are mobile friendly, so the same keyboard-and-screen-reader thinking that helps on a desktop carries over to a phone or tablet, where touch targets are sized to be reachable and the layout reflows rather than forcing a pinch-and-drag. A visitor checking your building from a bus is using the same accessible tour as the reviewer signing off on it.

The short version

• Yes, a 360 tour can be accessible when it is built to WCAG 2.0 Level AA from the start.
• AA is the standard Canadian rules reference, and the AODA requires it of Ontario public-sector and large organizations.
• An accessible tour is keyboard operable, screen-reader navigable, captioned, contrast-checked, described, reduced-motion aware, and works without JavaScript.
• It is also an access tool, giving people a way to plan a visit and find their way before they arrive.