The restaurant with the ramp: why accessibility is a business decision

When I was about eight, my parents took the family to a Greek restaurant in Hamilton. The dining room was in the basement, and one entire wall was fish tanks, which for an eight-year-old should have been the highlight of the evening. It wasn't. Outside the front door sat a ramp, the first one I remember ever noticing, and inside was an open elevator that looked borrowed from a construction site.

All evening, older people came and went on that elevator, some in wheelchairs, some just glad to skip the stairs, and eventually I asked my dad why this restaurant had so many wheelchairs. "Because they're the only restaurant that caters to them," he said. I was a kid. I didn't get it.

I get it now. That basement restaurant was making a business decision, and a sharp one. Every family in the region with a grandmother who used a wheelchair drove past a lot of other restaurants to reach the one that welcomed her, and the whole family came with her, and they came back. The ramp was the reason the room was full.

The short version

• Accessibility is a business decision first and a compliance box second.
• The accessible path costs your other visitors nothing, and for some of them it is the only path in.
• You can run an honest first check yourself in two minutes, using only your keyboard.
• Built in from the start, accessibility stays a small line item instead of a scary retrofit.

Websites have ramps too

On a website the ramps are just harder to see. Captions on a video serve the person who can't hear it, and they also serve the person watching in a quiet waiting room. Strong colour contrast serves low vision, and it rescues anyone squinting at a phone in July sunlight too. Then there is keyboard navigation, which I will come back to in a minute, because it is the one you can test for yourself today. Building the accessible path costs the rest of your visitors nothing, and for some of your visitors it is the only path there is.

The W3C draws the same line on its business case page: in physical environments, everyone takes advantage of lower curbs, automatic door openers and ramps. The W3C says captions, 1.2.2, are there so people who are deaf or hard of hearing can watch synchronized media. For text, 1.4.3 asks for a contrast ratio of at least 4.5:1.

The ramp was the reason the room was full.

The two-minute test

Here is the fastest honest audit you can run without hiring anyone. Unplug your mouse, or just refuse to touch it. Now use your own website: reach the menu, open a page, get to the contact form and fill it in, using nothing but Tab, Enter, and the arrow keys. Watch for the places where the little focus outline vanishes and you're lost, where a menu opens for a hover you can't perform, where the form traps you in a field. If you finish the test frustrated, you've just met your website the way some of your visitors meet it every day.

Keyboard operation is the criterion behind everything you just tried with Tab and Enter, and it notes that content a keyboard can operate is also operable by people with no vision. Focus visible is the W3C's criterion for the vanishing outline, and no keyboard trap is the one for a field that won't let you leave.

If you are in Ontario

Worth remembering: that restaurant built its ramp and its elevator decades before any law asked it to, because the owners understood who fills a dining room. Today, if you lead a school, a college, a municipality, or a larger organization in Ontario, a good portion of this stopped being advice years ago. The accessibility deadlines under provincial law have already passed, and public-facing websites are squarely inside them. But treating the law as the goal misses what the restaurant understood: compliance keeps you out of trouble, while welcome fills the room. Your students and your patrons travel with families, and families choose the places that work for everyone at the table.

Ontario's website guide is plain about it: as of January 1, 2021, the AODA requires all public websites to be accessible for designated public sector organizations and for businesses and non-profits with 50 or more employees, and the standard is WCAG 2.0 Level AA.

What baked-in actually looks like

Accessibility behaves like plumbing: easy while the walls are open, expensive once they're closed. Baked in, it looks small at every step: colour contrast gets checked when the palette is chosen and changing it is still free, image descriptions get written while the person uploading still remembers why the image is there, keyboard behaviour gets tried the day the menu is built, and captions ride along with the video order while the transcript is fresh. Each one is a minor line item in the moment, and together they mean there is never a scary retrofit project waiting at the end.

Run the two-minute test on your site this week, or make it the first item in a proper audit if the stakes warrant one. And if the test goes badly, ask me where to start. That question is one I always make time for, the same way I make time to fix plugins I don't own.

Where does the focus outline disappear on your site?

Common questions about accessibility

Is accessibility just about following the law? The law is the floor. That restaurant was full for decades before any law asked it to build a ramp, because the owners were aiming at the room, and the compliance came along with it.

Will accessible changes make my site worse for everyone else? Nothing on that list takes anything away from the visitor who never notices it, and every item opens the door a little wider for the visitor who needs it.

Where do I start if the two-minute test goes badly? Start with the check itself, then fix the spots where you got stuck one at a time. If you would rather not do it alone, just ask me where to begin.

References

Checked against the Ontario website guide, the W3C business case and the five W3C WCAG 2.2 Understanding pages listed below, on 2026-10-11.

• How to make websites accessible, Government of Ontario.
• The business case for digital accessibility, W3C Web Accessibility Initiative.
• Understanding success criterion 1.2.2: captions (prerecorded), W3C.
• Understanding success criterion 1.4.3: contrast (minimum), W3C.
• Understanding success criterion 2.1.1: keyboard, W3C.
• Understanding success criterion 2.1.2: no keyboard trap, W3C.
• Understanding success criterion 2.4.7: focus visible, W3C.