Accessibility

The standard we work to

WCAG 2.2 Level AA. That is the bar Canadian accessibility legislation points at, and it is the one Kaza is built against: whether or not the legislation reaches us.

What has actually been measured

On Kaza’s own public pages, the front page and the pages linked from it:

• Colour contrast checked against the real rendered colours, not the design file. Every text style measured clears 4.5:1; most sit above 6:1.
• One h1 per page and no skipped heading levels, so a screen reader’s outline matches what a sighted reader sees.
• Every image carries a real alt description, not a filename.
• Interactive targets are at least 44px, including the menu on a phone.
• Keyboard operation with a visible focus ring everywhere. The navigation menu is a native disclosure element rather than a scripted one, so it works without JavaScript and cannot trap focus.
• No horizontal scrolling at 390px, measured rather than assumed.
• Motion is respected. Anything that animates stops when the operating system asks it to. There is no carousel and nothing moves on its own.

What has not been measured

The signed-in staff application: the leasing desk, the property editor, the reporting screens, now meets the same standard on the two things that used to fail it: every field a person can type into is named, so a screen reader says what it is instead of “blank”; and every link and button shows where the keyboard is. Those are checked automatically on every change rather than promised, so they cannot quietly regress.

What is still not claimed for the staff side is a full AA audit. Parts of it are dense and table-heavy, and nobody has walked every screen against all fifty-odd criteria. Naming the two we fixed is honest; calling the whole application conformant on the strength of them would not be.

Nor has Kaza been tested end to end with every assistive technology. It has been checked with a keyboard and against the criteria above; that is not the same as being tested by somebody who uses a screen reader every day.

Where the law actually sits

Ontario’s AODA imposes website accessibility duties on organisations with 50 or more employees, and the Accessible Canada Act applies to federally regulated organisations. Kaza is neither, so neither compels this page.

Your company may well be covered even though we are not. If you need something specific for your own compliance (a conformance report, a fix to an identified barrier) ask, and you will get a straight answer about whether and when.

Telling us something is wrong

Email info@3d3d.caand describe what you were trying to do and what stopped you. You do not need to know the standard or name the criterion: “I could not get past the second step with my keyboard” is a perfect report.

A barrier that blocks somebody from applying for a home is treated as a fault in the product, not a request.