A Generic Website Template Left a Non-Profit Board Exposed

The situation

The email arrived on a Tuesday morning, forwarded to Simone by the manager of the third clinic in the chain, subject line still visible: Complaint - your feedback process is not accessible. The sender identified himself as an advocate assisting a client who used a screen reader, and who had tried three separate times to submit a complaint about a missed appointment through the clinic group's online contact form without success. He gave the organization ten days to respond before referring the matter further.

Simone owned the chain of clinics outright, a business that had grown to roughly forty million dollars a year in billings across its locations, but the shared administrative systems, including the website and its feedback tools, belonged to a not-for-profit she had set up years earlier with two other physicians, Niran and Somchai, to run patient-facing services across the group. The board met quarterly, and accessibility had never once been a dedicated agenda item on its own. When the complaint landed, Niran, a specialist physician who had built the original contact form himself using a website template he had found through a general search, was confident it already met the requirements, because the template's marketing had said as much.

The board pulled up the checklist the template vendor had supplied Niran when he first built the site. It covered colour contrast and font sizing, and little else beyond that. Nobody on the board had a background in accessibility law, and the checklist had given a comfortable, false sense that the matter was settled, so it had not really been looked at since. Somchai, the third board member, wanted to send a quick reply defending the form as it stood, arguing the sender was likely fishing for a settlement. Simone was not willing to reply without knowing where the organization actually stood, so before anyone answered the complaint, the board retained our office to work out what the ten-day deadline in that email really meant, and what the template had actually failed to do.

What made the timing worse was that the clinic group's busiest referral season was starting in two weeks, and any public escalation of a complaint like this, even an unfounded one, risked becoming a distraction the board did not have room for. Simone wanted an answer that would hold up, not a quick one that might not.

The legal question

Ontario's accessibility rules are requirements, not expectations, and the accessible customer service standard reaches essentially every organization that provides goods or services to the public and has at least one employee, with no exception for modest size. Size affects the extra duties to document policies and file compliance reports, and the separate website accessibility requirements only apply to larger organizations, but the duty to offer a feedback process that people with disabilities can actually use, in accessible formats or with communication supports where asked, covers how a business communicates with customers who have disabilities, including making sure the channels people use to reach the organization, like an online feedback or complaint form, actually work with the assistive technology those customers rely on. A colour-contrast checklist speaks to one narrow requirement under a much broader standard; it says nothing about whether a screen reader can actually navigate the form's fields, submit them, and receive confirmation that the submission went through.

When we tested the clinic group's form directly, using the same kind of assistive technology the complainant had described, it failed in exactly the way he described. The form's fields were not properly labelled for a screen reader, so a user moving through it by keyboard, rather than a mouse, could not reliably tell which box corresponded to which piece of information, and the submit button gave no confirmation once pressed. It was not a deliberate barrier. It was a template built for visual appearance, sold as compliant in general marketing language that did not match what the standard actually requires, and never independently checked by anyone with the expertise to catch the gap.

The ten-day deadline in the complaint email was not itself a legally binding trigger of anything; there is no fixed statutory countdown that begins the moment a customer emails a complaint. What the deadline signalled was the sender's own patience, and a credible threat to escalate to the appropriate oversight body if the organization did not respond meaningfully. Ignoring it, or replying defensively, would have made an eventual referral more likely and put the organization in a worse position when it came, since a body reviewing the matter afterward would ask what the organization had done once it knew about the problem, not only what had gone wrong originally.

The more serious question for the board was how long the form had been broken in this way. It had been in continuous use for several years, across every clinic in the chain, which meant this complaint was very unlikely to be the first time a patient using assistive technology had tried and failed to use it. It was, more likely, simply the first time anyone had said so directly to the organization rather than giving up quietly.

What we did

1. Tested the feedback form directly against assistive technology rather than relying on the template vendor's own compliance claims, using the same category of screen reader the complainant had described, working through the entire submission process field by field, to confirm precisely which parts of the form failed and why, before drafting any response to the complaint or deciding what needed to be rebuilt.
2. Reviewed the template vendor's original marketing and documentation that Niran had relied on when building the site years earlier, to understand exactly what had been represented as compliant and what had not, since that gap mattered both for fixing the form correctly and for framing an honest account of how the failure had happened in the first place, rather than treating the vendor's claim as settled fact.
3. Drafted a direct, non-defensive response to the complainant within the window his email had suggested, acknowledging the specific failure he had described rather than disputing whether it had occurred, confirming a screen reader could not reliably complete the form, and explaining that a proper fix was already underway, because a defensive first response tends to escalate an accessibility complaint that a straightforward one can often resolve on its own.
4. Commissioned a proper rebuild of the form's accessible elements with a developer experienced in the applicable standard, rather than patching the existing template piecemeal, so that field labelling, keyboard navigation, and submission confirmation all worked the way the standard actually requires, not just the way the original vendor's marketing had claimed, and had the rebuilt version independently tested before it went live.
5. Advised the board on what the ten-day deadline did and did not legally require, correcting the assumption that ignoring it or minimizing the complaint carried no real consequence, so Simone, Niran, and Somchai understood the actual stakes of the sender's stated timeline, and the realistic range of what escalation to an oversight body could involve, before deciding how quickly to act.
6. Reviewed the organization's broader accessibility practices beyond the single form, given that a gap this basic in one customer-facing system raised a fair question about what else had been assumed compliant without ever being tested rather than actually checked. A board that had trusted one vendor's marketing for years had no way of knowing whether the same mistake had been repeated elsewhere, and the review identified two more tools needing the same independent check: an appointment-request page and a printed intake form, neither ever tested against the standard.
7. Coordinated with each clinic manager across the chain to confirm the rebuilt form was rolled out consistently at every location rather than only at the clinic where the complaint originated, since a fix applied unevenly across a multi-site organization would have left the same gap open elsewhere, and would have made it look, to a future complainant at a different location, as though the organization had learned nothing from the first one. Each manager confirmed in writing once the new version was live.
8. Prepared a short written record of the correction for the board's files, documenting when the gap was identified, what testing was done, what was rebuilt, and when each step occurred, so the organization would have something concrete to point to if the same complainant, a future one, or an oversight body, ever asked what had happened after the complaint was received.

The outcome

The complainant did not escalate further. Once he received a direct acknowledgment of the specific failure, confirmation that a proper rebuild was already underway, and a working version of the form to test once it was ready, he considered the matter resolved on his end and did not refer it to the oversight body he had mentioned. That was the best realistic outcome available once the complaint had already landed; it did not undo the fact that the form had been failing people for years before anyone said so, quietly, without anyone at the organization knowing.

The board absorbed the cost of the rebuild, the independent testing, and the time spent reviewing its broader practices at a point in the year it would rather have spent preparing for its busiest referral season. Niran, who had built the original form in good faith using a tool marketed directly to people without technical or legal training, took the gap between the vendor's marketing and the actual standard personally, and the board did not treat the resolution as something to be proud of when we discussed it afterward. A years-long gap, once identified, does not become a clean win simply because the complaint that surfaced it was handled well once it arrived.

The review of the appointment-request page and the printed intake form turned up smaller issues in both, neither serious enough to have drawn a complaint on its own, but each worth correcting while the organization already had the right expertise engaged. Fixing those alongside the main form cost more time in the short term but meant the board was not left waiting for the next complaint to find the next gap.

What limited the damage was speed, honesty, and a willingness to test the fix properly rather than patch it and hope. The organization avoided a formal referral and kept its standing with the complainant and, by extension, with any body he might otherwise have approached, but the underlying lesson stayed with the board well past the immediate resolution: a vendor's marketing claim is not the same thing as an actual compliance review, and the two should never have been treated as interchangeable across a chain serving patients who depended on those systems working.

What you can learn from this