Accessibility

DeedRead is used by realtors on laptops, in cars, and at open houses, and the reports they produce are read by their clients. It has to work with a keyboard, with a screen reader, at 200 percent zoom, and in daylight on a phone. This page states where we are, plainly.

The standard we build to

We target WCAG 2.2 Level AA. That is the level Canadian federal and provincial accessibility law points at, and it is what our own review is measured against. We are not claiming a completed third-party audit; we are stating what has been implemented and tested, and what is still open.

What is in place

• Keyboard access throughout. Every control, including uploading documents and opening a cited excerpt, can be reached and operated without a pointer. Dialogs move focus in, keep it inside while they are open, close on Escape, and return focus to the control that opened them.
• A visible focus indicator that survives dark backgrounds. A dark ring over a white halo, so the same indicator reads on a white form and on the navy analysis screen.
• Skip to main content as the first stop on every page, so the nav is not re-read on every navigation.
• Text contrast at 4.5:1 or better for body copy, and 3:1 for form-control borders and meaningful graphics. The palette is checked by an automated test, so a colour cannot quietly drop below the line.
• Labels bound to fields, with hints and errors announced rather than shown only in colour.
• Progress you can hear. A report takes a few minutes; the analysis screen reports its stage and progress to assistive technology instead of going silent.
• Reduced motion honoured. If your device asks for less motion, the animations stop. Nothing is conveyed by movement alone.
• Meaning never carried by colour alone. Every severity, band, and status also carries text.
• A light and a dark theme, switched from the button in the header on the public pages and inside your workspace. It follows your device setting until you choose otherwise, and your choice is remembered on that browser. Both themes are checked against the same contrast minimums. Printing and PDF export are a separate choice, made on the download button and set to light unless you change it, so a report you send a client is readable on paper.
• Four languages (English, French, Simplified Chinese, Traditional Chinese), with the page language set correctly so a screen reader uses the right voice.

Known gaps

Stated rather than omitted, because a statement that lists only successes is not useful to the person deciding whether they can do their job with this tool.

• Uploaded documents are the author's. DeedRead reads what a strata or seller produced. A scanned, image-only PDF is read with on-device OCR, but we cannot make an inaccessible source document accessible, and the report quotes it as written.
• The generated PDF is not tagged. It is produced in the browser from the on-screen report. The web report is the accessible version; if you need the content in another form, ask us.
• No published third-party audit yet. Our conformance claim rests on internal review and automated checks.
• The charts (score ring, radar, projections) carry text alternatives, and every figure they draw also appears as text in the report body. They are not separately keyboard-navigable data views.

Telling us about a barrier

Email info@deedread.ca with "Accessibility" in the subject. Tell us the page, what you were trying to do, and the assistive technology and browser you were using, if you know them.

We aim to acknowledge within 2 business days and to tell you either the fix or the workaround, and when to expect it. If you need something from DeedRead in an alternative format, ask in the same email and we will arrange it at no charge.

Feedback we act on

A reported barrier is treated as a defect, not a suggestion: it is triaged with the same priority as any other bug that stops a realtor from finishing a report, and where it affects a shared control, the fix lands in the one implementation every page uses.