Starter
I test before I show
$9 / month
- 30 tests per month
- ≈ $0.30 per test
- 1 user(s)
- Report, comparison with the previous run, PDF sign-off report
- “From your idea” is not included: it starts with the Pro plan.
- No commitment
Pricing
Prices in US dollars, taxes included. Stop whenever you want.
No sign-up: paste your app's address and get a read-only report. 3 tests a day.
I test before I show
$9 / month
I test every version
$19 / month
We ship as a team
$49 / month
14 days of the Pro plan, no credit card, 20 tests included.
Compare Avalyz with manual acceptance testing and testing tools
Yes, with no commitment. The subscription is monthly. A cancellation takes effect at the end of the period already paid: access stays open until then. During the trial no card is asked for: at the end of the 14 days, without a subscription, no more tests can be run and nothing is charged.
Prices are in US dollars, taxes included, paid monthly. Payment goes through a reference merchant that collects on Avalyz's behalf: Avalyz stores no bank details.
Hosting in the European Union, in Paris (France). The provider's name and the details are on the “Security and data” page.
By default, a test reads your pages read-only (signed-in pages only with the test account you give). The screenshots and HTML collected are used only to produce your reports. Retention periods are published on the “Security and data” page.
An automated test can be wrong: flag a defect that is not one, or miss one. If the report is wrong, tell us: we look into it and fix the tool. Avalyz proves what it saw, it does not guarantee the rest.
Avalyz tests your app read-only by default, links accessibility defects to the WCAG 2.2 and RGAA 4.1 criteria and produces a report and a sign-off report. It proves what it saw and does not guarantee the rest: it replaces neither an RGAA compliance audit nor legal advice, and includes no service carried out by a person.
Yes. It is not the same AI: it is independent from the one that wrote your app and it does not see your code. Avalyz judges the app from the outside, like a visitor, read-only by default. It is a second pair of eyes, not a substitute for your own judgement.
A run, read-only by default, on the address you give, in Quick mode (4 pages without an account, 6 with an account) or in Full mode (the whole site, up to your plan's cap). Every test started from the page, through the API or by scheduled monitoring counts in the account's monthly quota.
Give a test account (optional): Avalyz signs in with it, signing in is the only form submitted, then it explores the signed-in pages (read-only by default) and records the journeys by role. Without a test account, it judges what a visitor sees without signing in.
By default, no: the test opens your pages read-only, it creates and changes no content, and the only form submitted is the sign-in form, with the test account you give. Write mode, only at your request, fills in and submits forms with test data: it requires proof that the site is yours (production) or your attestation that you have the right to test it (test environment), and never makes a real payment or deletes anything. Only public addresses are accepted.
A summary in plain language, the findings ranked by severity with annotated screenshots, a comparison with the previous run of the same app and a PDF sign-off report. The report is shared through a link that can be password-protected and set to expire.
You can run an instant test without signing up, 3 times a day. You can also open a 14-day trial of the Pro plan, no credit card, with 20 tests. One trial per work email domain; with a public mailbox (Gmail, Outlook…), one trial per address.
Yes: by hand, through the API, with a CI script or right after a deployment. You can also schedule monitoring (15 minutes at the shortest): Avalyz flags a regression compared with the previous run and sends a weekly report.
No. Avalyz is self-service software: there is no audit, acceptance testing or advice carried out by a person. You stay in charge of the decision to show, deliver or sell your app.
No. The automated accessibility checks link each defect found to the WCAG 2.2 and RGAA 4.1 criteria it affects. It helps you spot and track defects; an RGAA conformity audit remains human work that Avalyz does not replace.
Comparison
Three common ways to run a website's acceptance testing, and what Avalyz does or does not add alongside them. Every statement about a third-party technology points to its official source, listed at the bottom of the page.
A person follows a checklist and records the results in a spreadsheet.
A team writes automated tests with an open source project, for example:
An online service monitors websites or runs scenarios; features and prices vary by vendor.
Online software that tests your web app from the outside: in-browser tests, a clear report and a PDF sign-off report.
| Criterion | Manual acceptance in a spreadsheet | Code-it-yourself test framework | Generic SaaS monitoring or testing platform | Avalyz |
|---|---|---|---|---|
| Setup time | Immediate: a spreadsheet template and a checklist are enough. | Install the tool and its environment (for example Node.js for Playwright), then write the tests. [1] | Create an account, then configure the checks or scenarios the platform offers. | Paste a website address: nothing to install. An instant test without sign-up is available, 3 times a day. |
| Skills required | Rigour and knowledge of the site; no programming. | Programming: TypeScript or JavaScript, Python, .NET or Java for Playwright; Java, Python, C#, Ruby, JavaScript or Kotlin for Selenium. [1] [2] [8] | They vary from one platform to another, from entering addresses to writing scripts: check its documentation. | No programming for a test. User journeys are written as plain sentences (French or English) or imported from Gherkin or CSV. |
| Sign-off report for the client | To be written by hand from the spreadsheet. | The tools produce test reports for the team (Playwright opens an HTML report); a sign-off report for the client still has to be written. [1] | Depends on the platform: check its documentation. | PDF sign-off report and a report in plain language, shared through a protected, expiring link; white label possible. |
| Accessibility | Possible if the person knows the criteria. Human judgement remains essential for part of the checks. [10] [11] | Possible by adding a checking engine. Automated tests detect some common problems; many can only be found through manual testing. [4] | Depends on the platform. No tool can automatically check every aspect of accessibility. [10] | Partial automated checks: each defect found is linked to the WCAG 2.2 and RGAA 4.1 criteria it affects. It is not an RGAA audit. |
| Cost | No licence: the cost is the time spent, on every acceptance round. | Free, open source projects (Apache-2.0 licence for Playwright and Selenium, MIT for Cypress); the cost is development time and running the tests. [3] [5] [6] [9] | Subscription, according to each vendor's pricing model. | $9 per month (Starter), $19 (Pro) or $49 (Team), no commitment; 14-day trial with no credit card. |
| Maintenance | Keep the list up to date when the site changes, and redo every check by hand. | The test code follows the site's changes and is maintained like any code. | The platform is maintained by its vendor; your scenarios still need to be kept up to date. | The software is maintained by Avalyz. When a selector in a user journey no longer finds its element, a repair is proposed and applied only if you confirm it. |