Review step
Scope the task and platforms before review starts
Public review record
Verified Scope Page and Badge Snippet
A public verification page, with an optional accessible badge snippet, tied to real review dates, current status, and the exact work completed.
Best fit
- Teams that want to communicate active accessibility work responsibly
- Organizations with clear review boundaries and a documented retest history
- Products that need a public-facing status page rather than vague marketing claims
First step
Name the flow that matters most, confirm the platforms, and choose the right review size.
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
Is the reviewed scope ready to explain publicly?
Choose this after reviewed scope and dates are stable enough to publish a truthful public scope page and optional badge snippet.
Boundary
What this is not
Not an audit by itself and not a claim that every part of the organization was reviewed.
Next step
What to prepare
Confirm the reviewed areas, exclusions, review dates, current status, and where the badge or verification link should appear.
What you receive
Clear deliverables for the agreed review
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
Plain-language notes that keep the public verification page accurate and date-bound
Main deliverable
A public verification page with optional accessible badge markup linked to the reviewed work
Included review areas
Reviewed areasCurrent statusMonitoring statusReview dates
Main result
Visitors, partners, and procurement teams can understand what was reviewed and how to read the current status without guesswork.
Good fit: Best once the review work and dates are stable enough to communicate publicly
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.
Status language
Public trust language stays narrow, dated, and tied to scope.
The badge avoids broad claims such as fully approved, guaranteed compliant, or certified forever. Every badge points to a public page that spells out the reviewed areas, dates, included flows, exclusions, and status history.
Example statuses
Verified ScopeReviewed with remediation in progressUnder ongoing monitoring
Badge placement examples
The mark changes wording based on where it will appear.
A full-site mark and a page-specific mark can use the same public verification record, but the embed language needs to stay honest about scope. This keeps the badge useful without implying a blanket review.
Site-wide mark
For headers, footers, or global templates. Use only when the public scope applies anywhere the mark appears.
Page-specific / snapshot mark
For a reviewed landing page, form, checkout, or snapshot flow. This avoids implying a broader review.
Clients receive copy-ready HTML in their portal after Guidepost marks a public scope as Verified Scope.