The offer
A named part of a site, repaired in source.
FixBarriers agrees a written scope, repairs accessibility barriers in that source, and hands the changes back for your team to review, merge and publish.
What can be in scope
The engagement is a named part of a site—not an open-ended rebuild. Typical inclusions, when they are listed in the written scope:
- Templates and listed pages
- Named components
- The source that produces them
What is not included
A whole-site rebuild
Work stays inside the agreed templates, pages and components.
Hosting, accounts or publishing
FixBarriers does not take over your infrastructure or ship the change live.
Legal advice or a certificate
The work is a source-code repair in a written scope, not a legal determination or a conformance certificate.
An overlay or plugin
Changes are made in the agreed source, not by adding a third-party overlay.
What you provide
A shareable view
A public URL or another authorised way to inspect the pages.
Source access
Access to change the agreed templates, pages and components.
A place to review
Staging, a preview, or your team’s existing review environment.
A reviewer and publisher
Someone who can answer questions, merge and publish. Legal and policy decisions stay with you.
How the work moves
Before work
Agree the scope
Name the templates, pages and components. Agree scope, fee and schedule in writing.
During
Repair and retest
Change the agreed source, then check those repairs within that scope.
Handoff
You publish
Your team or agency reviews, merges and publishes. Change notes stay with you.
A description of the engagement, not a claim about a completed client project.
What you receive
Source changes
Edits in the agreed templates, pages and components, typically as a pull request or patch.
A limited retest
A check of the repaired work inside the written scope—not a new whole-site audit, and not a promise that no barriers remain.
Change notes
What the barrier was, what changed, and how to check the repair again.
Two questions before the work
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 we need to replace our agency?
No. The default handoff is a pull request or patch for your existing team or agency. FixBarriers does not take over hosting or accounts.
A fuller list is on the frequently asked questions page.
A short page on barriers and official rules is also on this site: Why source-code repairs matter.
Scope, fee and schedule are agreed in writing.
This site does not collect messages.