GuidepostAccessibility

Human accessibility review for websites, portals, mobile apps, and customer-facing documents.

Client expectations

What you will receive from Guidepost.

A Guidepost review is meant to give you a clear summary: what was reviewed, what was found, what should be fixed first, and how follow-up work will be handled.

Request a reviewSee a sample review

Plain-English promise

You should never have to guess what was tested, what the report means, or what to do next.

Before work starts

  • A written review plan that names the pages, flows, screens, documents, platforms, and exclusions for the first pass.
  • A practical access checklist for test accounts, staging links, app builds, documents, and special instructions.
  • A proposal or invoice-ready service summary that explains the deliverables, timing, and starting price or approved fee.

During the review

  • Manual review of the agreed experience using keyboard access, screen readers, browser checks, and platform-specific assistive technology where relevant.
  • Findings logged with severity, affected page or flow, user impact, steps to reproduce, expected behavior, and recommended fixes.
  • Browser checks may support the review, but human testing decides the findings.

Your deliverables

  • A written report or findings memo with an executive summary, review scope, methodology notes, priority findings, and next steps.
  • Developer-ready finding details that can be copied into a ticketing system or used directly by the team fixing the product.
  • CSV export, portal access, retest guidance, and public verification language when included.

After delivery

  • A walkthrough note that explains what matters first and which fixes should be tackled in the next sprint.
  • A retest path for fixes the client marks ready, with the result saved with the original finding.
  • Optional remediation support, monitoring, or a public verification page when the review history supports it.

Deliverables by service

Different offers produce different depth, but the next steps stay practical.

The deliverable should match the decision you need to make: fix one flow, plan a broader audit, prepare a mobile release, or support public verification.

Focused first review

Local Snapshot Review

A short findings report for the agreed web flow

  • Three to seven findings written in plain English
  • Desktop/laptop web check and mobile web check for the same reviewed flow
  • Keyboard, screen reader, form, error-message, structure, and basic technical check support
Review service details

Deeper one-flow review

Priority Flow Review

A deeper findings report and fix plan for one business-critical web flow

  • Six to twelve findings when the reviewed flow supports that depth
  • Desktop/laptop web check and mobile web check for the same reviewed flow
  • Clearer WCAG references when the mapping is confident
Review service details

Broader website review

Website Accessibility Audit

A website accessibility report and findings list for the included pages and flows

  • A report that summarizes scope, key blockers, and the review method
  • Findings across the included pages, templates, forms, and flows
  • Desktop/laptop web and mobile web coverage for included web flows
Review service details

Native mobile review

Native Mobile App Accessibility Audit

A mobile findings set with assistive-technology notes across the included app flows

  • Findings across the included iOS or Android flow
  • Notes on VoiceOver, TalkBack, focus order, labeling, and important screen changes after actions
  • Fix guidance mapped to native patterns, controls, and navigation behavior where relevant
Review service details

Fixes and follow-through

Remediation Support

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

  • 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
Review service details

Ongoing review history

Monitoring / Evidence Portal

Recurring monitoring notes, evidence history, and follow-up recommendations for the reviewed scope

  • Recurring checks for approved web routes where appropriate
  • Focused manual spot checks when changes or signals justify review
  • Plain-language monitoring notes and regression follow-up
Review service details

Public review record

Verified Scope Page and Badge Snippet

A public verification page with optional accessible badge markup linked to the reviewed work

  • A public verification page that lists reviewed areas, dates, included flows, and exclusions
  • Accessible badge markup that points back to the verification page
  • Status language that can reflect review, remediation, monitoring, expiry, or suspension
Review service details

What Guidepost needs from you

A little preparation makes the review faster and more useful.

The first review plan only needs enough detail to start testing cleanly.

The website, app build, document, or portal access needed for testing

Test accounts, coupon codes, sample data, or staging credentials if the flow requires them

The business-critical tasks customers need to complete successfully

Any launch date, procurement date, legal review, or customer commitment driving the timeline

Scope boundary

The deliverables describe the reviewed work.

Reports, retests, badges, and verification pages stay tied to the agreed scope, review dates, and client-approved language.

Start intakeRead terms and disclaimer