Accessibility Statement
What we have built in, where the site still falls short of the standard, and how to tell us when something blocks you. Written openly, because a statement that only lists successes is not much use to anyone.
Our commitment
Niagara Falls should be reachable by everyone, and so should the site that helps you plan a visit. We build this site so that people who use screen readers, navigate by keyboard, rely on magnification, or need reduced motion can browse, compare and book without hitting a wall.
This statement covers visitingniagarafalls.com. It does not cover the operators who run the experiences, or the booking platform that completes your purchase — those are separate sites with their own accessibility statements.
Conformance status
We aim to meet WCAG 2.2 Level AA. The site is currently partially conformant: most of the standard is met, and the exceptions are listed openly below rather than left for you to discover.
"Partially conformant" means some content does not yet fully meet the standard. We would rather say that plainly than claim a clean bill of health. Everything we know about is in known issues, with what we intend to do about it.
What we have built in
Keyboard
- Every page starts with a skip to main content link, so you are not tabbing through the whole navigation on each page.
- Tour and attraction cards are one tab stop each, on a link named after the tour or attraction, rather than several stops per card.
- The photo galleries open, close with Escape, and return focus to the thumbnail you came from.
- Menus, accordions and filters all respond to Enter and Space.
Screen readers
- One
<main>landmark per page, headings in order, and lists marked up as lists. - Every image carries alt text, and decorative graphics are hidden from the accessibility tree so they are not read out.
- Links say where they go. A "Learn More" button also announces which attraction it belongs to.
- Filtering the tours announces how many results came back.
Seeing and reading
- Body text and interface colours meet the AA contrast ratio of 4.5:1, checked programmatically across the whole site rather than by eye.
- Links inside coloured panels are underlined, so colour is never the only thing marking them.
- Layouts reflow to a single column and stay usable at 320px and at 200% zoom.
Motion
- If your device is set to reduce motion, the fade-in animations are switched off and content appears immediately.
- Nothing flashes, auto-plays with sound, or moves in a way you cannot stop.
Accessibility information for the attractions themselves
Beyond the site, the guides tell you what to expect on the ground, because that is usually the thing that decides whether a day works:
- Step counts and whether there is a lift, for the gorge attractions where it matters most.
- Which routes are wheelchair accessible and where the accessible path diverges from the main one.
- Where a boarding process, a moving walkway or a confined tunnel is involved.
- Age, height and mobility restrictions, stated on the listing before you pay rather than at the gate.
If you need something we have not covered for a specific attraction, ask us before you book and we will find out.
Known issues we are still working on
Assessed as of the date at the top of this page:
| Issue | Who it affects | Status |
|---|---|---|
| The gold star rating glyphs sit at about 1.8:1 against white, below the 4.5:1 the standard asks for. | Low-vision users, who may not be able to make out the stars. | The numeric rating and review count appear next to every star row, so the information is always available as text. We are reworking the colour. |
On most pages the <h1> sits in the hero, just outside the <main> landmark. |
Screen reader users jumping straight to main content land just below the page title. | Structural change, scheduled. |
| Text inside tour and attraction cards cannot be selected by dragging, because the whole card is a click target. | Anyone copying a tour name or price. | Known trade-off of making the full card clickable. Titles remain selectable elsewhere on the tour's own page. |
| Some blog cards and a few footer links do not lead anywhere yet. | Everyone, but especially confusing with a screen reader. | Those pages are being written; the links will be connected or removed. |
How we test
- Automated checks across every page for contrast, heading order, landmark structure, ARIA validity, link names and image alt text — run against the rendered page in a real browser, not against the source, so what is measured is what a visitor gets.
- Keyboard passes through the booking path: find a tour, open a gallery, filter, save to a wishlist, reach checkout.
- Reduced-motion and zoom checks at 200% and at 320px width.
- Automated tools catch perhaps half of what matters, so findings are confirmed by hand before we call something fixed.
This site is built as static HTML with progressive enhancement: the content is in the markup, and JavaScript adds behaviour on top rather than being required to read the page.
Compatibility
The site is designed to work with current versions of Chrome, Edge, Firefox and Safari on desktop and mobile, together with the assistive technology built into those platforms — VoiceOver, TalkBack, Narrator — and with NVDA and JAWS on Windows.
It relies on HTML, CSS, WAI-ARIA and JavaScript. Where JavaScript is unavailable, page content still renders, though interactive features such as filtering and the wishlist will not run.
Tell us about a barrier
If something on this site blocks you, we want to know — it is the fastest way for us to find the gaps our testing misses.
- Email info@visitingniagarafalls.com with "Accessibility" in the subject.
- Or use the contact form.
Please tell us the page, what you were trying to do, and the browser or assistive technology you were using. We aim to reply within 5 business days. If a fix will take longer, we will tell you what we are doing and offer another way to complete your booking in the meantime — including simply booking over email with our help.
If you cannot complete something here
No one should miss out on a tour because a page did not work. Contact us and we will take the booking through directly: we will confirm availability, price and pickup details with you, arrange the reservation with the operator, and send you the confirmation. There is no extra charge for this.
Regulatory context
We sell to visitors on both sides of the border, so several frameworks are relevant. We treat WCAG 2.2 AA as the standard that satisfies them in practice:
- Americans with Disabilities Act (ADA) — United States.
- Accessibility for Ontarians with Disabilities Act (AODA) and its Information and Communications Standard — Ontario, where much of what we list operates.
- Accessible Canada Act (ACA) — federal Canada.
- EN 301 549 and the European Accessibility Act — for visitors from the EU.
If you have raised something with us and are not satisfied with the response, you may escalate to the relevant body in your jurisdiction. We would much rather resolve it directly first.
About this statement
This statement was prepared on 11 August 2026 following an assessment of the live site, and reflects its state on that date. It is reviewed whenever we make a substantial change, and at least annually.
It is written to follow the structure recommended by the W3C's accessibility statement guidance: our target standard, our actual conformance, what we have done, what is still outstanding, and how to reach a person about it.