Accessibility testing service
Combines journey-based manual review with reproducible automated findings.
- For
- Web agencies delivering customer sites
- Solves
- Automated scans miss contextual accessibility problems.
- Delivers
- Accessibility findings and retest evidence
- Built in
- about 4 weeks of creation time, MVP in 5 days
- Investment
- $8,500 for the MVP, $33,000 for the full product
- Run it
- Inside your business, or as part of your offer to clients
What it does
For web agencies delivering customer sites, turn authorized sites, user journeys and agreed testing criteria into accessibility findings and retest evidence.
- Run automated checks.
- Inspect keyboard flows.
- Review semantics.
- Document user impact.
- Prioritize fixes.
- Retest remediations.
What goes in, what comes out
- Authorized sites
- User journeys
- Agreed testing criteria
AI drafts, people review. Evidence review and quality assurance workspace.
- Accessibility findings
- Retest evidence
How it works
The workflow
- InStart with
Authorized sites, user journeys and agreed testing criteria
- 1
Agree review criteria
- 2
Ingest a sample
- 3
Generate candidate findings
- 4
Inspect supporting evidence
- 5
Let reviewers confirm or dismiss each item
- 6
Assign corrections
- 7
Recheck the affected material
- OutFinish with
Accessibility findings and retest evidence
AI does the heavy lifting, people stay in charge
Propose possible inconsistencies, omissions and rubric matches. Combine extraction with deterministic checks where rules are explicit. Reviewers make the final judgment. Keep false positives and missed cases visible during evaluation.
What your team sees
Key screens: Journey inventory, issue evidence, fix verification. Open on a review queue ordered by reviewer-selected priorities. Show each finding beside the original evidence and applicable rule. Provide accept, dismiss and needs-information controls with reasons. A separate report view summarizes confirmed findings and unresolved items, not raw AI flags. In this product, the first view is journey inventory, followed by issue evidence and fix verification.
Accounts and administration
Versioned review criteria, evidence links, reviewer decisions, disagreement handling, correction assignments, recheck status and exportable review history.
Integrations and data access
Authorized repositories, technical documentation, application APIs and logs. Source repositories, task trackers and report exports. Keep findings as review proposals until authorized owners accept the resulting actions. These are candidate integration categories, not verified supported connectors.
How we build it
We build with our own AI software development factory, so most implementations take days to a few weeks of creation time, not months. You see working software at every step, and exact timing depends on availability.
- 1
Scoping call
Day 1Thirty minutes on your process, your data and how you want to run it: for your own team, or for your clients. You get a fixed scope and price for the MVP.
- 2
MVP
5 daysOne buyer segment, one recurring use case; first modules: run automated checks; inspect keyboard flows. Manual review in the loop. Built by our AI software factory.
- 3
Paid pilot
6 daysAccounts, roles, review states, audit trail and the first integration, hardened for two to three paying pilot customers.
- 4
Full product
10 daysRemaining modules: document user impact; prioritize fixes; retest remediations. Self-serve onboarding, billing, monitoring and the wider integration set.
- 5
Run and improve
MonthlyWe host, monitor and improve it for a fixed monthly fee, or hand it over to your team. How the retainer works.
Why we start with an MVP
An MVP, or minimum viable product, is the smallest version that your users can actually work with. It is not a cheap version of the full solution. It is a test, built to answer the questions that decide whether the rest is worth building.
- Pick the riskiest assumption. Here: will web agencies delivering customer sites use it to solve "automated scans miss contextual accessibility problems"?
- Build only what tests it. One team, one use case, a few core modules. People do the rest by hand for now.
- Run a paid pilot. Have a qualified reviewer independently assess the same sample.
- Measure, then decide. Track verified issues resolved and false alarms. Then expand, change course or stop, with evidence instead of opinions.
MVP scope for this solution. Begin with web agencies delivering customer sites and one recurring use case. Build the first two modules: run automated checks; inspect keyboard flows. Provide operator assistance for the third module: review semantics. Deliver accessibility findings and retest evidence through a manual review queue. Perform other necessary full-scope functions manually during the pilot. Include all applicable access, accuracy and professional-review controls from the start.
After the MVP. After paid pilots establish value, automate the remaining modules: document user impact; prioritize fixes; retest remediations. Add one validated source integration, reusable customer configuration and recurring delivery. Expand to additional teams, document formats or languages only after testing the new scope.
What the build depends on. Evidence coordinates, versioned rules, reviewer decisions and a representative reference set. Measure misses as well as confirmed findings before scaling.
Investment
A planning range to start the conversation, not a quote. You pay per phase, so you can stop after the MVP.
- Phase 1
MVP
One buyer segment, one recurring use case; first modules: run automated checks; inspect keyboard flows. Manual review in the loop.
- Phase 2
Paid pilot
Accounts, roles, review states, audit trail and the first integration, hardened for two to three paying pilot customers.
- Phase 3
Full product
Remaining modules: document user impact; prioritize fixes; retest remediations. Self-serve onboarding, billing, monitoring and the wider integration set.
Indicative total, MVP to full product$33,000about 4 weeks of creation time · start with the MVP from $8,500
Running costs per month
A rough indication of monthly hosting and AI model costs once it is live, not tested. Real costs depend on usage, file sizes and the models chosen.
| Stage | Hosting and infrastructure | AI usage | Total per month |
|---|---|---|---|
| MVP and paid pilotabout 3 customers | $30–$60 | $80–$160 | $110–$220 |
| Full productabout 50 customers | $110–$210 | $880–$1,750 | $990–$1,960 |
Run it or resell it
For your own team
Web agencies delivering customer sites run it inside the business: authorized sites, user journeys and agreed testing criteria in, accessibility findings and retest evidence out, reviewed by your people.
As part of your offer
Agencies, consultancies and software companies can offer it to their own clients under their brand. We build and maintain it; you sell and deliver it.
Your brand, or this one
Run it under your own brand, or start from this concept style.
- primary
#277f91 - accent
#c97454 - surface
#e4eff1 - ink
#22201e
- Headings
- Archivo
- Text
- Lora
- Voice
- Technical, direct, no hype
Selling it to your own clients: the go-to-market playbook
Pricing to test
Test USD 500-2,000 for a defined audit sample and report. Offer recurring review priced by reviewed items and specialist hours. Software-only access can follow a reliable reviewed service. All prices require validation.
Message to test
Accessibility testing service for web agencies delivering customer sites. Combines journey-based manual review with reproducible automated findings. Demonstrate the claim through an annotated review of a checkout journey.
Where to find buyers
Web agency partnerships
Lead magnet
An annotated review of a checkout journey
The first 30 days
- Week 1: interview five prospective buyers in this segment: web agencies delivering customer sites. Ask to see a recent example of the problem and their current process.
- Week 2: prepare this demonstration using authorized or synthetic material: an annotated review of a checkout journey.
- Week 3: present it through web agency partnerships and seek one narrowly scoped paid pilot.
- Week 4: review verified issues resolved, false alarms, total delivery effort and a concrete renewal decision before increasing scope.
Paid pilot
Have a qualified reviewer independently assess the same sample. Compare confirmed findings, false alarms and omissions. Repeat on unseen material before agreeing recurring volume. For this solution, use authorized sites, user journeys and agreed testing criteria and evaluate accessibility findings and retest evidence. Agree success thresholds with the buyer before starting; collect a baseline for verified issues resolved, false alarms. A positive signal is payment and repeat use with acceptable quality and delivery cost, not a favorable demo reaction alone.
Success metrics
Verified issues resolved, false alarms
Retention and expansion
Offer recurring reviews and rechecks of previously confirmed issues. Expand document or case types after validating the new rubric with qualified reviewers.
Why clients would pick it
A domain-specific review rubric and rights-cleared examples of confirmed defects, false alarms and reviewer reasoning. For this solution, build around combines journey-based manual review with reproducible automated findings. This advantage requires execution and accumulated customer trust; the base model alone is not a defensible asset.
Alternatives and positioning
Manual reviewers, checklists, generic scanning tools and specialist audit services. Differentiate on this specific proposed advantage: combines journey-based manual review with reproducible automated findings. Test it against the buyer's current method on the same task. Competitor coverage and uniqueness have not been established.
Main delivery costs
Document or media processing, model evaluation, expert review, false-positive handling, rechecks and customer-specific rubric calibration.
Safeguards
Protect secrets, customer data and source code. Use controlled environments, technical review and a recoverable deployment process. Validate source access and reviewer availability during the pilot. Maintain customer-level access, data deletion controls and a record of final approvals.