Fixes and follow-through

Remediation Support

Follow-through for teams that need help interpreting findings, prioritizing work, validating fixes, and, when needed, making approved accessibility fixes under a written scope.

Best fit

  • Lean teams with accessibility work alongside existing product roadmaps
  • Engineering leads who want faster clarification during remediation
  • Small businesses without an in-house web developer for straightforward accessibility fixes
  • Agencies implementing fixes for multiple clients

First step

Name the flow that matters most, confirm the platforms, and choose the right review size.

Starting point

Monthly Accessibility Help starts at $150-$300/month; scoped implementation support is quoted separately

Final pricing depends on the confirmed pages, flows, platforms, documents, timeline, and retest expectations.

Review step

Scope the task and platforms before review starts

Review step

Test the agreed flow with assistive technology and keyboard behavior

Review step

Write findings with impact, reproduction steps, and expected behavior

Review step

Retest the same flow when fixes are ready

Best question

When to choose this

Do you already have findings that need follow-through?

Choose this after findings already exist and the team needs clarification, fix planning, retest support, or scoped implementation help.

Boundary

What this is not

Not the first audit, not an open-ended development retainer, and not permission for Guidepost to make changes without written scope and access approval.

Next step

What to prepare

Share the findings list, choose the fixes in motion, and decide whether support is guidance-only or includes scoped implementation help.

What you receive

Clear deliverables for the agreed review

Written clarification on existing findings, expected behavior, and fix intent

Review of proposed fixes, implementation questions, and edge cases that come up during remediation

Optional implementation support for approved accessibility fixes when the client needs Guidepost to make the change directly

Written authorization, limited access, change notes, and client review before any implementation-support work begins

Retest notes that confirm what changed and what still needs attention

Support keeping public status or verification language aligned with the current state of the work

Main deliverable

Remediation guidance, retest follow-up, and optional implementation support tied to documented findings

Included review areas

WebMobile WebiOSAndroid

Main result

The work stays active after delivery, with a steadier path from findings list to verified fixes or carefully scoped implementation support.

Good fit: Best after a report has landed and the team is actively working through fixes

How Guidepost works

Task-based review, plain language, and practical follow-through

The work is centered on the tasks people need to complete, the barriers that interrupt those tasks, and the written guidance a team needs in order to fix them.

Request a review