Accessibility testing and compliance

Know what every accessibility barrier costs.

limena tests your websites, apps and documents against WCAG and the accessibility laws where you operate. It prices every barrier in lost sales, sign-ups or support calls, routes the fix to the team that owns it, and verifies it at every release.

Book a demo

See a live sample report →Check one page free →

Checkout · shop.example.com

Payment step/checkout/paymentBlocks

Submit order button has no accessible name.

WCAG 4.1.2→ FrontendFound automated · manual test bookedSee the 5-step journey breakdown ↓

Standards applied per program

EU · European Accessibility Act (EAA)
US · ADA Title II & III
Canada · AODA & ACA
UK · PSBAR & Equality Act
WCAG 2.2 AA & EN 301 549

A list of 400 issues isn't a decision.

Most testing stops at the report, and a report rarely tells the budget-holder which findings cost customers. limena tests the whole journey, finds the step that stops people, and prices it from your traffic. Try your own numbers below.

CheckoutBlocked at Payment

shop.example.com · EAA & ADA (WCAG 2.1 AA)

Product
/products/canvas-tote
Passes
Cart
/cart
Passes
Sign in
/account/login
Non-blocking
Guest option skipped in tab order.
WCAG 2.4.3→ Frontend
Payment
/checkout/payment
Blocks
Submit order button has no accessible name.
WCAG 4.1.2→ Frontend
Confirmation
/checkout/complete
Not reached

Try your numbersweekly startsAOV× 52 weeks × 1.24% affected × 75% drop-offFound automated · manual test booked=$48,000a year at risk

The price gets the work funded. It isn't all the work does.

limena prices each barrier because a figure is what moves a budget. That figure only counts what comes back to the business. Here is what it leaves out.

Steps that earn nothing still have to work.
Resetting a password, cancelling a plan, reading a help article. None of them show up in revenue, and a blocked one still stops someone.
People finish on their own.
A step that works means someone completes the task without calling support or asking a family member for help.
Each fix reaches more people than it was priced for.
Clear errors and working keyboard paths help anyone on a small screen, with an injured hand, or reading in a second language.
It stays fixed.
limena retests the fix at every release, so the person it helped is not locked out again next quarter.

Start from the question you're asking.

Finance and leadership
What's it costing us?
Lost sales, sign-ups and support calls, priced from your own analytics with every assumption shown.
- GA4
- Matomo
- Your unit value
Calculate your journey risk →
Legal and compliance
Are we compliant?
See which laws apply where your users are, the standard each one sets, and the gaps against it.
- VPAT
- EAA
- AODA
View sample EAA & VPAT pack →
Product and engineering
What do we fix first?
Barriers ranked by the journey they break, each with an owner, a fix and a re-test at the next release.
- Jira
- Linear
- GitHub
See how fixes are ranked →

From finding to decision to done.

Checkout, Payment step

Blocks the journeyWCAG 4.1.2 / 1.3.1 · Missing accessible label

Screen reader users hear "edit text" with no clue what to type, so they cannot pay. It is the only payment path.

DevelopmentOwner under the W3C ARRM

Cost of this step · from the numbers above

$48,000a year at riskEstimate

Starts a year: 64,480; Your number
Affected group: 1.24%; Example
Drop-off at a blocked step: 75%; Example
AOV: $80; Your number

Change any input and the ranking updates. The 1.24% and 75% are examples for this page; in your workspace each is set by your team, with its source beside it.

Explained, owned and priced.

Each finding is explained in plain language, assigned to the role that owns it, and ranked against your critical journeys. The barrier on your checkout outranks a hundred cosmetic issues.

Connect your analytics and tell limena what a journey is worth, and each break on it is priced in dollars, with every assumption stated beside the figure.

Fixed where the work happens.

Each fix goes to the role that owns it under the W3C's ARRM, by Slack DM, and lands as a ticket in Jira, Linear or GitHub Issues. Status and reopens come back from the tracker. A closed ticket triggers a re-test, and the re-test decides whether it is fixed.

For developers: fix from the editor and check every pull request

Finding to fixed

Found at release 4.12
Payment step blocked on Checkout
Mon
Routed to Development
Slack DM to the owner, ticket in Jira
Mon
Pull request opened from the editor
Agent found the component, check passed
Tue
Re-tested at release 4.13
Payment passes. Checkout works end to end.
Thu

Closed when the re-test passes

Works with the tools your team already uses.

Always ready to show your work.

Procurement questionnaires, legal reviews and board updates all ask the same question. limena captures the evidence as the work happens, so the answer is already current.

A live VPAT

Generated from current test results. Criteria that automated testing cannot judge stay Not Evaluated until someone checks them by hand.

Preview a sample ACR / VPAT →

Proof each fix held

A closed ticket is not proof. Each fix is recorded with the re-test that verified it and the release it shipped in.

Preview the evidence record →

Maturity over time

Where the program sits and how it has moved, in one view leadership can read.

Preview the maturity view →

Executive summaries

A summary per program and per test run, and the full list as CSV, Excel, or Markdown.

Preview an executive summary →

Built on the standards your auditors already use.

Each of these can be checked before you buy. The links say where.

WCAG 2.2 AA

Every finding maps to a WCAG 2.2 success criterion. A program can be held to 2.1 or 2.0 instead if its obligation says so.

Criteria coverage

The law where you operate

ADA and Section 508 in the US, AODA, the Accessible Canada Act and Quebec SGQRI 008 in Canada, the European Accessibility Act (EN 301 549) in the EU, and PSBAR and the Equality Act in the UK, chosen per program.

How standards are applied

W3C roles and responsibilities

Ownership follows the W3C Accessibility Roles and Responsibilities Mapping, built in by task. Your team can change any owner.

The W3C mapping

Data held in Canada

Workspace data is stored and processed in Montreal. AI explanations go to a named model provider, and a workspace can turn them off.

Which services and regions

Sign in through your directory

Sign in with a Microsoft or Google work account, and people at your DNS-verified domain join your workspace automatically.

Security

Everyone who fixes, at no extra cost

Unlimited seats on every plan, from Monitor to Govern, so designers, content editors and engineers get findings directly.

Pricing

See what your barriers are costing you.

We'll run limena on one of your journeys and show you each barrier priced in lost sales, sign-ups or support calls, and who owns the fix.

Book a demo See a sample report →