FAQ
Frequently asked questions.
Short answers about the work. Scope, fee and schedule are agreed in writing.
What does FixBarriers do?
FixBarriers agrees a written scope, repairs named accessibility barriers in that source, and hands the changes back for your team to review, merge and publish. The work is done in the templates, pages and components named in the agreement.
What is not included?
The engagement is a named part of a site, not an open-ended rebuild. Work stays inside the agreed templates, pages and components, and the source that produces them. FixBarriers does not take over hosting, accounts, or publishing.
What will it cost, and how long will it take?
Once a written scope is agreed and we have the access we need, we aim to finish the agreed repairs and the in-scope check of those repairs within about 10 business days. That is an expected schedule, not a guarantee. It does not include time for your review, merge or publication. If access is delayed, or the agreed scope changes, we will agree on a new schedule in writing. The fee is agreed in writing before work starts. Prices are not published on this site.
Do you offer a free or unlimited audit?
No. A conversation about a possible written scope is not a free or unlimited audit.
Do we need to replace our agency?
No. The default handoff is a pull request or patch in your source, for your existing team or agency to review. It is not a findings list only. FixBarriers does not take over hosting or accounts.
Who owns the code, and who publishes?
You own the code, including the repairs. Your team or agency reviews, merges and publishes. FixBarriers does not ship the change live.
Is this a legal opinion, a certificate, or protection from a complaint?
No. The work is source-code repair in a written scope. It is not a legal opinion, a conformance certificate, a VPAT, or protection from a complaint or lawsuit. Legal and policy decisions stay with you.
What does official Ontario text say about public websites?
Official Ontario text requires designated public sector organizations, and private businesses or non-profits with 50 or more employees in Ontario, to make public internet websites and web content published after 1 January 2012, on a site the organization controls, conform with WCAG 2.0 Level AA, other than live captions and pre-recorded audio descriptions, as of 1 January 2021, except where meeting the requirement is not practicable. Organizations with fewer than 50 employees in Ontario are not required under that website rule, but official guidance encourages them to follow it. Organizations with no employees in Ontario are outside that regulation’s application rule. Other duties may still apply. Whether a particular organization is covered is a legal conclusion for that organization and its counsel. FixBarriers does not judge that.
Is filing an accessibility report the same as repairing a website?
No. Official Ontario rules say businesses and non-profits with 20 or more employees in Ontario must file an accessibility compliance report. The current official deadline is 31 December 2026, then every three years. That reporting duty is not the same as the website duty, which official text attaches to designated public sector organizations and organizations with 50 or more employees in Ontario. A 20–49 employee organization may have to file a report without being under that website rule. A filed report is not a tested or repaired website. FixBarriers does not file the report.
Do you install an overlay or widget?
No. Changes are made in the agreed source, not by adding a third-party overlay or widget.
What do we need to provide?
A shareable view of the pages, access to change the agreed source, a place to review the work, and someone who can answer questions, merge and publish. Legal and policy decisions stay with you.
What do we receive?
Source changes in the agreed templates, pages and components, typically as a pull request or patch; notes on what changed and how to check it; and a limited retest of those repairs. That retest is not a new whole-site audit, not a promise that no barriers remain, and not an ongoing monitoring product.
Who does the work?
A software engineer on the FixBarriers team repairs named accessibility barriers in the agreed source, inside a written scope. You own the code, and your team or agency reviews, merges and publishes.
How do I get in touch?
This site does not collect messages.
Scope, fee and schedule are agreed in writing.
This site does not collect messages.