Reviewing the Recite Me Accessibility Solutions

review of Recite Me 2026

Disclosure: we are the Recite Me team and this is our first-party review of Recite Me. This review of Recite Me explains what the platform does, how its parts fit together, and where it helps most.

Quick summary

Best for	Organisations that need an integrated accessibility programme across many sites and channels
Not ideal for	Very small sites that only need a single free scanner or teams wanting a single-purpose developer tool
Pricing model	Subscription. See our website or contact sales for plan details
Review scores	See third-party review sites such as G2, Capterra and Trustpilot for current ratings

What Recite Me includes

Overall positioning

Recite Me is an all-in-one accessibility platform. All products use the same list of websites and the same scan data. That means findings do not have to be copied between tools. The single data source links testing, tasks, reports and governance so teams work from one record of truth.

Setup and overview

Dashboard

What it does: a single-screen summary of accessibility across every tracked site. It shows a WCAG pass rate, open issues by severity and trends over time as score cards and charts.

How it works: dashboards use the platform’s central evidence store so numbers reflect the same data other tools use.

Why it matters: executives get an at-a-glance view without opening other tools.

Good to know: dashboards summarise findings but are not substitute evidence for audits.

Domains

What it does: lists every website you track, with pages found, scan coverage, issue counts and the chosen accessibility standard.

How it works: a crawler discovers pages automatically. Every other product uses the same site and page data so the estate size is visible from day one.

Why it matters: you can group pages into collections and set the applicable standard per site.

Good to know: crawler discovery shows what is found, not necessarily every hidden page.

Get Started / onboarding

What it does: a short guided questionnaire that asks region, sector, audience and current maturity and picks a standard from a catalogue of 16.

How it works: the questionnaire sets the chosen standard on your sites and suggests a starter roadmap and products.

Why it matters: many organisations do not know which overlapping standard applies. This gives quick guided help.

Good to know: the guidance helps with choices but is not legal advice.

Core testing and monitoring

WCAG Checker

What it does: the core scanner. A crawler finds pages and an automated engine built on axe-core with additional custom rules tests each page against WCAG success criteria. Issues are logged against a criterion, a page and a severity of High, Medium or Low.

How it works: views include a principle Summary, a Full Report of failing criteria and an Issues list. Journeys let a user record multi-step flows with a browser extension so interactive steps are replayed automatically.

Why it matters: it finds many technical failures fast and ties them to specific WCAG criteria.

Good to know: automated testing only finds part of WCAG, so manual review is still needed. Journeys need a recording first.

Guardian (continuous monitoring)

What it does: runs alongside the Checker to catch regressions as content changes and shows new issues separately from long-standing ones.

How it works: Guardian watches content changes and flags fresh failures.

Why it matters: accessibility can drift as teams publish new pages. Guardian acts as a safety net between audits.

Good to know: it monitors changes but does not replace full audits.

Document Remediator

What it does: scans uploaded PDFs for problems such as missing tags, reading order, alt text and contrast, then fixes what it can automatically and returns a corrected PDF.

How it works: the service analyses a document, applies automated fixes where possible and hands back a corrected file.

Why it matters: PDFs are a common failure point and many fixes are routine to automate.

Good to know: it fixes issues where possible, so some documents will still need manual attention.

Media Manager

What it does: lists images and audio or video found on the sites and shows their accessibility state, such as missing alt text, captions or transcripts.

How it works: media found by the crawler is mapped to failures and shown in one place so teams can act.

Why it matters: media maps to WCAG 1.1.1 and 1.2 criteria and is a high-volume failure type that is easy to lose in a general issue list.

Good to know: it highlights media gaps but does not create captions or transcripts for you.

Mobile

What it does: brings native mobile app accessibility results into the platform using the same severity and criterion model as web.

How it works: mobile results appear in the platform beside web findings in a familiar structure.

Why it matters: standards such as Section 508, the EAA and the ADA can apply to apps as well as websites.

Good to know: do not describe how apps are scanned beyond this. Results are reported in the platform.

Content (readability)

What it does: analyses reading age and spelling across crawled pages. It shows how many pages were analysed, reading-age bands and a “harder than target” index. You can filter to pages over a target reading age.

How it works: the content scanner measures readability scores and flags pages outside the chosen target.

Why it matters: plain language supports cognitive accessibility and relates to WCAG 3.1.5 Level AAA.

Good to know: it measures readability, not whether wording is right for a given audience.

Toolbar

What it does: the visitor-facing Recite Me accessibility toolbar that you add to your site. Features include screen reading, translation and styling controls.

How it works: a per-site toggle lets teams turn features on or off and brand the toolbar.

Why it matters: the toolbar helps visitors tailor their experience while the organisation fixes the site.

Good to know: it helps visitors but does not replace fixing the underlying site.

Issue Reporter

What it does: a small widget added through the Universal Tag that lets visitors report accessibility problems.

How it works: visitor reports go into a queue the site owner reviews and acts on.

Why it matters: scanners cannot catch every real-world barrier. Visitor reports add human feedback from real use.

Good to know: it is visitor-led feedback and depends on users choosing to report issues.

Audits and assessments

Audits (manual)

What it does: structured manual audits where every WCAG criterion and page in scope is a checkpoint for a human auditor.

How it works: where automated scans are confident, verdicts are pre-filled so auditors focus on judgement calls.

Why it matters: automated tools only test part of WCAG. Manual checks are needed for full conformance evidence.

Good to know: audits are human-led and recordable in the platform.

Physical Assessments

What it does: guided audits of real-world locations such as buildings and facilities in the style of ADA Title II.

How it works: an assessor follows a guided workflow and records findings and remediation options.

Why it matters: it extends accessibility coverage beyond the web.

Good to know: assessor-led, not automated.

Hardware Assessments

What it does: guided audits of devices such as kiosks and ATMs, in the style of Section 508 hardware requirements.

How it works: a step-by-step wizard records findings and offers remediation options of A, B or C for each item.

Why it matters: hardware can create barriers in public services and retail settings.

Good to know: assessor-led, not automated.

Vendor Management

What it does: tracks accessibility risk from third-party suppliers. Teams record vendor data such as VPAT availability and known issues and the platform calculates a risk score.

How it works: the score depends on the information entered about each vendor.

Why it matters: third-party widgets and plugins can add failures outside direct control, and procurement checks are expected by many standards.

Good to know: the risk score is only as accurate as the data you add.

Programme management

Evidence

What it does: the central record of every issue found with page, criterion and status.

How it works: summary figures are pre-calculated so dashboards and reports load quickly.

Why it matters: Evidence is the single source of truth behind the Dashboard, Checker, Reports, Roadmap and monitoring.

Good to know: evidence is central but must be kept up to date by teams using the tools.

Reports

What it does: pre-built report templates plus a custom Report Builder with around 40 widgets for leadership, auditors or regulators.

How it works: build exportable documents and dashboards using charts and tables from the builder.

Why it matters: dashboards are not deliverables. Organisations need exportable reports to show progress.

Good to know: reports are flexible and intended to support external review.

Roadmap

What it does: turns issues into tasks that can be assigned and tracked on a kanban board and exported to CSV. It includes an audit trail and a “My Tasks” view.

How it works: issues become accountable remediation work and can be traced through to closure.

Why it matters: it creates traceable evidence of an active compliance effort.

Good to know: tasks require people to update statuses to show progress.

Governance Toolkit

What it does: templates and generated documents such as accessibility policies, accessibility statements and procurement checklists using the organisation’s assigned standard and current conformance data.

How it works: templates are populated with your standard and data to create starter documents.

Why it matters: most standards expect documented policy and a public statement as well as technical conformance.

Good to know: templates are a starting point and may need legal review.

Integrations and developer tools

Universal Tag

What it does: one embeddable snippet that switches on visitor-facing features such as the Issue Reporter, with per-site toggles.

How it works: one tag saves integrating each feature separately.

Why it matters: it simplifies deployment of visitor features.

Good to know: the tag controls visitor-facing features only.

Plugins and Extensions

What it does: home of the browser extension, used to record Journeys for the Checker and companion plugins.

How it works: a browser add-on records multi-step flows for automated replay.

Why it matters: Journeys let you test interactive flows, not just static pages.

Good to know: it needs only a browser add-on.

Integrations

What it does: connects the platform to outside systems such as ticketing tools so accessibility work can feed existing workflows.

How it works: integrations pass tasks and data to other systems to fit your processes.

Why it matters: most teams already use ticketing and need accessibility work to appear there.

Good to know: connect to external workflows but do not expect every tool to be pre-built.

Developer Tools

What it does: API key management, a JavaScript SDK and a command-line tool.

How it works: use the tools to run scans in CI or pull data into other systems.

Why it matters: they help integrate accessibility into developer workflows.

Good to know: they are aimed at teams that can run CI and work with SDKs.

Learning and support

Academy

What it does: guided WCAG courses with quizzes where answers are checked. Completion requires a genuine pass.

How it works: courses test knowledge so learners must demonstrate understanding.

Why it matters: tools do not fix accessibility on their own. Teams need to know why issues matter.

Good to know: training measures knowledge, not certification outside the platform.

Resources

What it does: a library of guidance and articles organised by topic to explain how to fix scanner findings.

How it works: resources link directly to typical failure types.

Why it matters: practical guidance helps teams act on issues faster.

Good to know: resources are a reference, not personalised consultancy.

Support

What it does: a direct support and contact route inside the account.

How it works: support is available from inside the platform.

Why it matters: teams can raise questions or report problems without leaving the account.

Good to know: we do not state response times or channels here.

Adjacent checks

SEO

What it does: checks technical SEO such as meta tags, robots rules and sitemaps. It includes a summary and page list.

How it works: the SEO checks overlap with accessibility basics such as page titles and heading structure.

Why it matters: many accessibility basics help SEO and vice versa.

Good to know: these checks are extras, not core accessibility tests.

GEO

What it does: checks how well a site is set up for discovery by AI answer engines and how AI crawlers see the site.

How it works: it audits site readiness for AI-driven discovery.

Why it matters: it parallels making content readable by assistive technology.

Good to know: treat GEO as an emerging, adjacent concern.

Web Security

What it does: reports TLS configuration and mixed-content problems with a simple score and specific findings.

Why it matters: basic security issues can affect availability and trust.

Good to know: this is an extra check, not a full security audit.

Data Privacy

What it does: scans public pages for exposed personal information. Results are masked and the service never stores raw data.

Why it matters: accidental exposure of personal data is a risk and must be managed.

Good to know: results are masked to protect privacy.

OKF export

What it does: produces portable, machine-readable evidence bundles for a domain so accessibility data can be used outside the platform.

Why it matters: you can take evidence with you and use it in other tools.

Good to know: use the abbreviation OKF only when exporting.

How the platform works together

All products share the same site and page list and the same scan data. That is the key benefit. Here is a worked example.

1. The Checker crawls a site and finds a failing form field tied to a WCAG criterion.
2. The issue is recorded in Evidence and appears on the Dashboard and the Issues list.
3. The issue becomes a task on the Roadmap and is assigned to a developer.
4. The developer fixes the markup and marks the task done in the Roadmap.
5. Guardian monitors the page and confirms the failure no longer appears.
6. A Report is generated showing the issue closed and the improvement in the organisation’s trend charts.

Because all products read and write the same data, you do not have to copy issues between tools or reconcile multiple spreadsheets.

Review: performance

The platform finds many technical failures quickly. The Checker is built on axe-core with custom rules and reports failures by criterion and severity. Journeys let you test interactive flows when you record them first. Guardian provides continuous monitoring for regressions.

Limitations are clear. Automated testing covers only part of WCAG, so manual audits remain necessary. Document Remediator automates many PDF fixes but some documents need human work.

Review: standards coverage

Recite Me tests pages against WCAG success criteria and lets you select an applicable standard from a catalogue of 16 during onboarding. The platform helps find, fix and evidence issues against a named standard and supports manual audits for the checks automated tools miss.

The platform also supports evidence work related to laws such as the ADA, Section 508, EN 301 549, the European Accessibility Act, the Equality Act 2010 and the DDA 1992 where they apply. It does not make a site legally compliant on its own.

Review: pricing and plan limits

Pricing is subscription based. Plan names and limits are available on our website or from sales. Contact us to discuss estate size, document volumes and feature needs such as mobile reporting and manual audits.

Review: support and learning

Support is available inside the account and the Academy provides guided WCAG courses with quizzes and genuine pass requirements. A resources library offers how-to guidance. These elements help teams act on findings rather than leaving them as lists.

Review: usability

The single evidence store and pre-calculated summaries make the platform easy to navigate. Dashboards, Roadmap and Reports are joined so teams see cause, task and result in one place. Journeys and the browser extension are simple to use for recording flows.

Review: integrations and scalability

One Universal Tag deploys visitor features. Integrations link work back into ticketing systems and developer tools include API key management, a JavaScript SDK and a command-line tool for CI. The platform is suited to organisations tracking many sites because every product uses the same discovered page list.

What users say

Users praise the single source of truth model and the way findings flow into tasks and reports. Visitor tools such as the toolbar and Issue Reporter are valued for real-world feedback. Teams also find the Report Builder useful for leadership and audit deliverables.

Where Recite Me may not be the right fit

• Very small sites that only need a free scanner and not a full programme.
• Teams that want a single-purpose developer tool without the programme management layer.
• Organisations wanting a full security audit from the same provider, as web security checks are extras.

Pros and cons

• Pros: single data source across tools, integrated roadmap and reporting, visitor-facing toolbar, continuous monitoring.
• Cons: automated scans need manual follow-up, some PDF fixes require human work, pricing details require contact for larger estates.

Our verdict

We believe Recite Me suits organisations that must run a joined-up accessibility programme across many sites and channels. The shared data model is the strongest feature. It links testing, tasks and evidence so remediation is accountable and visible to leadership.

If you run a large estate, need visitor-facing aids and want integrated reporting, this platform provides clear value. If you run a tiny site and only need a single free scan or a single developer tool, a simpler option may be better.

FAQs

How much does Recite Me cost?

Contact sales or visit our website for current subscription plans and pricing.

Is there a free trial?

Check our website or contact sales for trial availability and demo options.

Which WCAG level does Recite Me cover?

The platform tests against WCAG success criteria and lets you pick the specific standard during onboarding.

Will Recite Me make my site legally compliant?

No. We help find, fix, track and evidence issues against a named standard. Manual audits are required for full compliance claims.

How does Recite Me compare to single-purpose developer tools?

Recite Me combines testing, monitoring, tasking and reporting in one place, unlike tools that focus only on CI or local scans.

What support and training are available?

Support is available inside the account. The Academy offers guided WCAG courses with quizzes and pass requirements.

Can I integrate Recite Me with my ticketing system?

Yes. The platform supports integrations so accessibility tasks can feed existing workflows.