Pricing

Accessibility Testing Pricing

Alana is an accessibility testing marketplace where companies and consultancies pay per engagement and vetted testers are paid per job. Pricing is based on practical scope rather than generic package labels: the user journeys under test, assistive technology combinations required, turnaround expectations, and reporting depth. Teams can begin with a smaller paid intro engagement, then scale into standard per-engagement delivery or custom partnership plans as demand grows. This model keeps costs aligned to real work delivered and ensures lived experience remains central to how accessibility quality is measured.

Marketplace economics

  • Companies pay per engagement

    Budget maps to defined testing outcomes and not to open-ended consultant hours.

  • Testers get paid per job

    Compensation reflects scope and complexity of assigned testing work.

  • Transparent progression

    Most teams start with an intro engagement, validate value, then scale into standard or custom work.

Paid fixed-scope engagement

Intro

A focused starting engagement with clear deliverables and timeline. Includes targeted flows, core assistive technology coverage, and structured findings.

Per engagement

Standard

Fixed-scope accessibility testing engagements priced by complexity, number of flows, platforms, and assistive technology combinations required.

Program partnership

Custom

Designed for larger product portfolios, consultancies, or recurring testing programs requiring broader coverage, timeline planning, and custom delivery cadence.

How to choose the right tier

The Intro tier is best for teams that need a low-risk starting point while keeping incentives aligned. It is intentionally narrow: one or a few core journeys, a limited set of assistive technology scenarios, and a clearly bounded delivery window. Intro engagements are designed to prove value quickly and help teams understand how lived experience findings differ from automated reports alone.

Standard engagements are the most common path once a team has validated the process. In this model, the scope expands to include multiple key journeys, broader assistive technology coverage, and repeatable reporting expectations. Pricing remains engagement-based, so teams can plan accessibility work around release cycles and roadmap milestones without committing to unnecessary overhead.

Custom pricing is used when organizations need ongoing capacity or special coordination. This includes multi-product programs, enterprises with strict timelines, and consultancies that need overflow staffing while retaining client ownership. Custom engagements can include phased planning, scheduled retesting, and cross-team reporting rhythms that fit existing governance.

Across all tiers, Alana prioritizes clarity. Before work begins, both sides align on what is in scope, what tools and environments are relevant, and what deliverables are expected. This reduces uncertainty and ensures pricing aligns with outcomes. The aim is straightforward: make it easier for teams to buy meaningful accessibility testing and easier for testers with lived experience to participate in paid, structured work.

Pricing FAQ

How does Alana pricing work?

Alana uses a marketplace model. Companies pay per accessibility testing engagement, and vetted testers get paid per job. Pricing reflects scope, timeline, and assistive technology coverage.

Is there a free pilot?

No. Alana runs paid engagements from day one. Teams can start with a smaller intro scope to validate fit before expanding.

Do testers pay to join Alana?

No. Testers do not pay platform fees to apply. Alana evaluates profiles, matches suitable projects, and testers are compensated for completed work.

What affects standard engagement pricing?

Pricing is influenced by number of user journeys, platform types, depth of review, turnaround requirements, and required assistive technology combinations.

Can consultancies use custom pricing?

Yes. Accessibility consultancies can use custom partnership pricing when they need ongoing overflow capacity while maintaining their own client relationships.

What is included in delivered findings?

Findings include structured issue descriptions, reproduction details, severity context, and WCAG mapping so teams can prioritize fixes efficiently.