Accessibility
Our commitment
Maple Byways is for everyone who wants to explore Ontario by road, including people who use a screen reader, larger text, a switch or keyboard, or who are sensitive to bright screens or motion. We aim for the app and this website to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, the international standard that Ontario's accessibility rules are based on.
We are a small team, and we check accessibility as part of every change rather than once. Where something still falls short, we say so below, and we fix barriers that people tell us about first.
In the app
- Screen readers. The app works with TalkBack on Android and VoiceOver on iPhone. Buttons and links have names, Route and Day titles are headings you can jump between, and Stops are read with their number ("Stop 3"). Each "Open in Google Maps" link says which drive it opens, and each website link says whose website it is.
- Announcements. When you change the Route filters, the app says how many Routes now match. Sign-in and account errors are read out when they appear.
- Text size. The app follows your phone's text size setting, and screens rearrange rather than cut text off, up to at least twice the default size.
- Dark mode. The app follows your phone's light or dark setting.
- Less motion. With your phone's setting to remove or reduce animations on, photos appear without fading in.
- No dragging needed. In a Trip, you can reorder Stops by dragging, or with each Stop's Move menu (Move up, Move down, Move to another Day).
- Touch targets and contrast. Buttons and links are large enough to tap easily, and text meets WCAG contrast ratios in both light and dark mode. Our automated tests check contrast, touch target size and button labels on every change.
- Not by colour alone. Labels such as "Seasonal" and "Permanently closed" are written out, not shown only as a colour.
On this website
- Pages use headings, lists and landmarks, with a "Skip to content" link at the top.
- Everything works with a keyboard, with a clearly visible focus outline.
- Pages follow your light or dark setting, keep strong text contrast in both, and stay readable in Windows high contrast mode.
- Text can be zoomed to 400% without scrolling sideways.
- Photos have text descriptions, and every form field has a label.
- There are no pop-ups, no autoplaying media and no cookies.
In the web app and the admin area
The web app (app.maplebyways.ca) and the admin area aim for the same standard as the app: WCAG 2.2 at Level AA. Here is what works and, further down, what still falls short.
- Screen readers. The web app builds its accessibility tree as soon as it opens, so it works without a hidden setting. We check it by hand with NVDA in Chrome and in Firefox, and with VoiceOver in Safari on iPhone. Other combinations, including JAWS, should work, but we have not tested them. Route, Day and Stop titles are headings (levels 1, 2 and 3), and each Stop is read with its number.
- The map. As in the app, a Route's map can't be explored with a screen reader. The list of Stops, with the drive times and a Google Maps link for each drive, has the same information, and a "Skip map" button moves the keyboard focus past the map so it never traps you.
- Reordering Stops. In a Trip you can reorder Stops by dragging, or from each Stop's Move menu (Move up, Move down, Move to another Day) with the keyboard. Dragging is never the only way.
- Keyboard, zoom and contrast. You can use the web app with a keyboard alone: Tab reaches the buttons and links, including the links inside Route descriptions. Text can be zoomed to 400% without scrolling sideways, and the web app follows your light or dark setting. Our automated tests check contrast, touch target size and button labels, and scan the main pages for accessibility problems, on every change.
- Language. The web app is in English only, like the app.
What still falls short
- The map. A Route's map can't be explored with a screen reader. The same information is in the list below it: the Stops in order, the drive time between them, and a Google Maps link for each drive.
- Keyboard timing in some browsers. In Chrome, Edge and Brave, pressing Tab through a long page can occasionally skip a link, or Enter can act on the control you were on before. This comes from the framework the web app is built on. A screen reader's link and heading keys (for example K and H in NVDA) and its list of links are reliable.
- Headings in the Android app. In the Android app, TalkBack's Headings control finds only the headings that are on the screen. The "Go to Day 1" and "Go to Day 2" buttons at the top of a Route take you between Days.
- Safari and Tab. Safari skips links when you press Tab unless "Press Tab to highlight each item on a webpage" is turned on in its settings.
- Landmarks in the web app. Each page of the web app has one landmark, for its main content. It has no others, such as navigation or header regions, so a screen reader's landmark shortcuts go straight to the main content and nowhere else; headings and the Tab key still work.
- Language. The app and the Routes are in English only. This page, the Terms and the Privacy notice are also in French.
- The places themselves. We don't yet describe the physical accessibility of Stops and Local picks, such as step-free entrances, accessible washrooms or trail surfaces. Please check with each place before you go; most Stops link to their website.
- Other companies' services. Google Maps, Sign in with Apple and Google, the app stores and the places' own websites are run by others, and their accessibility is outside our control.
Tell us about a barrier
If anything in the app or on this website is hard or impossible for you to use, please tell us: email support@maplebyways.ca with "Accessibility" in the subject. Say what you were trying to do and, if you can, which device and assistive technology you use. A person reads every message and replies.
If you need this page, the Terms, the Privacy notice or a Route in another format, such as plain text or large print, email us and we'll send it.