Flow-based triage
We review the agreed flows against the accessibility criteria in scope, reproduce the barriers with keyboard and screen-reader checks, and separate blocking issues from lower-impact findings.
People using a keyboard or screen reader cannot finish the task.
An automated scan can flag markup. It cannot tell you whether a person can actually complete checkout, submit the form, or understand the error. We triage the blocked flows, fix the barriers in a scoped sprint, and require an agreed human keyboard and screen-reader retest before delivery acceptance.
Fees
Triage$500
Remediation sprintfrom $3,500
The assessment fee is credited toward the matching approved sprint. You get a written scope and quote after the assessment; work starts only after you approve it.
Prices are in USD. The sprint is quoted from the assessment findings; the amount shown is the starting point, not a fixed total.
A clean scan is not the same as a usable page.
Focus can disappear, a form label can be missing, a dialog can trap the keyboard, or a screen reader can announce a control with no useful name. Automated tools catch some of it. The rest shows up when a person tries to complete the task.
The barrier is in the task, not the file
The same component can be fine on one page and blocking on another. We test the agreed flows rather than only the component library.
Overlays do not close the gap
A widget can change what a scanner sees without fixing the underlying markup, focus order, or names.
Retesting is part of delivery
A fix is not accepted until the agreed keyboard and screen-reader checks pass on the scoped flows.
What you get
Triage the blocked task, fix the barrier, then retest it with a person.
The triage is a fixed-fee first step. The remediation sprint is quoted from the agreed flows and barriers.
Remediation scope
A written plan naming the flows, the fixes, the retest method, and what is out of scope. The $500 triage fee is credited toward the approved sprint.
Scoped fixes
Markup, component, style, and interaction changes for the agreed barriers, with regression notes for the flows they touch.
Agreed human retest
Before delivery acceptance, a person performs the agreed keyboard and screen-reader retest on the scoped flows. Automated checks can support the result; they do not replace it.
What this is not
Remediation is scoped to agreed flows. It is not a blanket claim that every page or every assistive technology has been covered.
- A legal accessibility certification, VPAT, or accessibility conformance report unless separately scoped.
- A full-site audit or a guarantee of WCAG conformance.
- Native mobile app accessibility, document remediation, or content rewriting outside the agreed flows.
- Fixes inside third-party embeds or vendor widgets we cannot change; we document the boundary.
- A guarantee that no user will encounter any barrier after the sprint.
How it works
Find the blocked flow, fix it in scope, and retest before acceptance.
The exact browser and screen-reader combinations are agreed before the retest.
- 1
Intake
You describe the blocked task, the affected users, the stack, and the deadline. Do not send credentials or customer data through this form.
- 2
Triage the flow
We reproduce the barrier with keyboard and screen-reader checks, review the relevant markup and interaction, and separate blocking issues from lower-impact findings.
- 3
Scope and approve
You get the remediation plan, the retest method, the acceptance checks, and a written quote. The triage fee is credited toward the approved sprint.
- 4
Fix and retest
We make the approved changes, run automated checks as a supplement, and complete the agreed human keyboard and screen-reader retest before delivery acceptance.
Requirement
Human retest is required before acceptance.
Automated scans are not delivery acceptance. The agreed keyboard and screen-reader retest is performed by a person on the scoped flows, and the result is recorded before the sprint is accepted.
Related rescue services
PHP and Laravel upgrades
Assess framework, dependency, and deployment risk before moving a working Laravel app to a supported PHP version.
View service →Security remediation
Turn a confirmed finding into a scoped fix, with verification and an independent review before completion.
View service →Cloud cost optimization
Find the cost drivers in your cloud bill before changing infrastructure. Qualification first, implementation only where the evidence supports it.
View service →Questions about accessibility remediation.
What is the human retest?
A person completes the agreed flows using only a keyboard and with a screen reader, on the browser and assistive technology combinations named in the scope. The method and the flows are agreed before the sprint.
Do automated tools still help?
Yes, as a supplement. They catch some issues quickly, but they do not prove that a task is usable or that a screen reader announces it correctly.
Do you provide a VPAT or certification?
Not in this service. Those are separate deliverables with their own scope and evidence requirements. We do not claim certification for the remediation.
What if the barrier is in a third-party widget?
We document it and the boundary. If the vendor controls the fix, we say so; we do not claim a change we cannot make.
How much does it cost?
Triage is $500 and is credited toward the approved remediation sprint, which starts at $3,500. The quote follows the triage and the agreed scope.
Which screen readers do you test with?
The exact browser and screen-reader combinations are agreed before the retest. We do not claim coverage of every assistive technology.
Accessibility remediation
Which task is blocking people today?
Send the flow, the users affected, and any launch or procurement deadline. We will reply with the triage next step.