Paper Boat Media / Accessibility software buying guide

03 / 05

The tool needs
a job to do.

What an accessibility plug-in can contribute, what it cannot prove, and how to evaluate the difference.

01Understand the claim
02Inspect the scope
03Test the integration
04Own the remaining work

01

The invoice is easy to understand. The promise needs a closer look.

A business owner asks for help making a website accessible. Someone recommends a plug-in, quotes an annual fee and explains that installation takes only a few minutes. Compared with a technical audit and a list of repairs, that sounds wonderfully manageable.

The attraction is understandable. Most owners have no reason to know how keyboard focus, accessible names or document reading order work. They want customers to use the site, want the business to meet its obligations and would prefer not to acquire a second profession in the process.

An accessibility plug-in can contribute to an accessibility program, but purchasing or installing one does not establish that the website conforms to WCAG or satisfies every applicable legal obligation. The product has to be evaluated in the context of the actual website, and the work still needs a defined scope and verification.

I would begin with the claim being made. Does the product offer user preferences? Does it detect potential issues? Does it change the rendered page? Does the subscription include a human evaluation? Those are different services, and they should be described separately.

This guide is about buying and integrating accessibility software responsibly. For the standards themselves, see my WCAG 2.2 versus 2.1 explanation. For planning the repairs, use the remediation prioritization guide.

02

Four things that often get sold under one label

The word accessibility appears on products with very different functions. Before comparing prices, establish which job each product actually performs.

Product or service Typical purpose What it does not establish by itself
Visitor adjustment widget Offers controls such as text or presentation preferences That the original interface and every process are accessible
Automated remediation tool Attempts to change certain aspects of the rendered page That every change is correct or every barrier is resolved
Scanner or monitoring service Detects testable issues and tracks findings over time That all interactions work for people using assistive technology
Manual evaluation Investigates defined pages and processes against a stated scope That untested content or future changes are automatically covered

Some vendors combine these functions. Others sell them separately. The relevant question is not whether a company has a long feature list. It is whether the package includes the work your site needs and whether the provider can explain its limits.

A scanner can be useful even if your team does not buy a widget. A widget may offer a preference that some visitors appreciate even after the website’s underlying code is repaired. A manual evaluation can reveal an issue that no additional software subscription will fix until a developer or content owner changes something.

03

What UserWay costs, and what that number means

At the time this guide was reviewed, UserWay’s public Pro widget pricing was based on monthly page views. The figures below are annual subscription prices in U.S. dollars, not a quote for a complete website remediation project.

UserWay Pro traffic tier Listed annual price Budget implication
Up to 100,000 page views per month $490 Confirm the site fits the tier and what the subscription includes.
Up to one million page views per month $1,490 Higher traffic changes the software cost, not just the implementation estimate.
More than one million page views per month Custom Obtain a written quote for the actual deployment.

Check UserWay’s current pricing before purchasing. Monitoring, advanced plans and manual services may have separate charges. The vendor’s definitions, domain rules and contract terms control the subscription.

For an owner, the arithmetic should be transparent. If a proposal includes software and professional work, ask for those amounts separately. If the owner buys the subscription directly, explain how access will be granted for setup. If the consultant manages it, explain account ownership, renewal responsibility and what happens when the relationship ends.

A business should be able to retain access to its own accessibility records and understand which service will stop if a subscription is canceled. That is a routine operational question, not an accusation against the vendor.

04

Page views are not restaurant covers or company size.

Software tiers can create an easy budgeting mistake. A prominent company is assumed to have enormous website traffic, or a small company is assumed to be safely below a threshold. Neither is a reliable measurement.

Use analytics and ask the vendor how it measures the tier. Page views, visits and users are different metrics. Confirm whether traffic is combined across domains or subdomains, whether a seasonal peak matters and how the provider handles a threshold being exceeded.

Consider an illustrative restaurant. It may serve many guests while receiving bookings through several outside channels. Another business may have a modest customer base but publish a large library that attracts significant research traffic. The size of the business does not resolve the software question.

I would record the metric used, the period reviewed and the plan selected. That gives the owner something concrete to revisit at renewal rather than relying on a conversation everyone remembers differently.

05

Integration is more than pasting a script.

A script can be easy to install and still require careful testing. It may interact with navigation, pop-ups, cookie controls, embedded forms and other software that also changes the page.

Start by recording the site’s current behavior and the specific improvements expected from the tool. Install in a suitable test environment where possible. Configure the product deliberately rather than enabling every available feature because it exists.

Then compare important journeys with the software enabled and disabled. The comparison helps establish which behavior comes from the underlying site, which comes from the tool and whether an apparent improvement creates another problem elsewhere.

Check keyboard order, visible focus, dialog behavior, menu operation and form errors. Inspect the widget on a narrow screen. Does it cover a booking button or cookie control? Can its own controls be reached and dismissed? Does the chosen location remain sensible when another banner appears?

The test should also include timing. If the original page renders before a later script modifies it, review whether the initial state or transition introduces a practical barrier. If a script fails to load, the site should still have the strongest underlying accessibility the team can provide.

Document the installation location and settings. The next developer should not have to search several tag managers, theme fields and plug-ins to discover why the same widget appears twice.

06

Fix the source when you can.

Suppose a form field has no meaningful label. A tool might attempt to infer the label from nearby text. The more durable repair may be to correct the form configuration so its purpose is properly expressed from the start.

Suppose a link says only “click here” in a long list of resources. A content editor can often make the link name descriptive without adding software. Suppose a template hides keyboard focus. The appropriate change may belong in the template’s styles rather than a separate layer that tries to compensate after rendering.

These examples are illustrative. A real finding needs to be assessed against the applicable criterion and its context. The broader point is about ownership: repairs are easier to maintain when the people who publish or build the component understand how it should work.

I would ask a vendor which issues its product detects, which it attempts to address automatically and which require a person. An honest boundary is useful. It lets the project team assign the remaining work instead of discovering later that everyone assumed somebody else was doing it.

07

What automation cannot decide for you

Some questions require interpretation. Does an image description communicate the information the image contributes? Does an error explanation help the person correct the problem? Is the reading order sensible? Can somebody complete a complicated process without losing context?

The W3C guidance on evaluation tools explains that some accessibility checks require manual intervention. That is a reason to combine methods, not to discard automation entirely.

Use automated tools for the problems they can reliably help identify and for repeatable regression checks. Use human evaluation for interaction, meaning and the conditions the software cannot judge adequately. Where appropriate, include people with disabilities using their own assistive technology and established methods.

The evidence should name the scope and conditions. “Passed our test” is much more useful when the record explains which process was tested, which environment was used and what the evaluator observed. A broad claim without that information is difficult for an owner to assess.

08

Read compliance and legal-support claims carefully.

There is a meaningful difference between a vendor offering support if a complaint arrives and a vendor proving that a website meets every relevant requirement. Read the actual terms of any legal-support, warranty or reimbursement program, including eligibility, exclusions, limits and the owner’s continuing obligations.

In April 2025, the FTC approved a final order requiring accessiBe to pay $1 million. The action concerned allegedly false, misleading or unsubstantiated claims about its automated product’s ability to make websites WCAG-compliant. The order restricts such claims without supporting evidence.

That was a specific enforcement action involving accessiBe. It is not a finding about every vendor or a reason to attribute the same conduct to UserWay. It is a clear reason for buyers to distinguish a marketing statement from evidence about their own implementation.

If a proposal promises a certificate, ask who issues it, what was evaluated, when it was evaluated and what the document actually represents. If the business needs legal advice, use qualified counsel. The technical provider should be able to supply an accurate record of the work without turning it into a legal guarantee.

09

Questions I would ask before buying

The following questions can turn a sales demonstration into a useful purchasing conversation. Ask for answers that apply to your actual product tier and deployment.

  1. What is included? Identify the widget, automated repairs, monitoring, human review and support separately.
  2. What remains our responsibility? Ask about content, PDFs, video, custom forms and third-party platforms.
  3. How will we test the result? Request a method for verifying important tasks, not simply a dashboard score.
  4. What does the script change? Understand its effect on the rendered page and any configuration or integration constraints.
  5. How is usage measured? Confirm traffic tiers, domains, staging environments and renewal terms.
  6. What happens when something fails? Establish issue reporting, escalation and the information support needs.
  7. How do we leave? Confirm data access, account ownership, cancellation and what will happen to the site when the product is removed.

For sites handling sensitive information, include the organization’s privacy and security review. Determine what data the service receives and what agreements or configurations are needed. Accessibility software should go through the same appropriate vendor review as other software introduced into the environment.

10

Build a budget around the work.

The software fee is usually the easiest number to obtain. The professional effort depends on what the site contains and what the engagement promises.

Budget component What can change the effort What to agree before work begins
Assessment Unique layouts, interactions, documents and test depth The review scope and expected evidence
Direct repairs Theme limitations, custom components and content quality The implementation responsibilities and exclusions
Software integration Existing scripts, dialogs, mobile layout and vendor settings The supported deployment and verification plan
Third-party coordination Vendor access, release schedules and contractual leverage Who raises issues and follows them through
Ongoing care Publishing frequency, platform changes and monitoring needs Review triggers, response expectations and renewal ownership

I would avoid an unlimited fixed-price promise before inspecting a complex site. That is not a reason to make the sales process difficult. A useful initial range can help an owner decide whether to proceed, followed by a clear scope and fixed price for the agreed work.

If a later finding changes the assignment materially, explain it before doing additional billable work. A small business should not discover halfway through that its important reservation process was never included. A consultant should not discover that “the website” quietly meant three applications and a decade of PDFs.

11

A practical purchase and verification sequence

Begin with an inventory and a few essential journeys. Decide what success means for the review. Assess the existing barriers, including those that will require direct code or content work.

If software appears useful, compare it against those needs. Review terms, account ownership and traffic. Trial it in a suitable environment and record the effect on the selected journeys. Keep the evaluation focused enough to finish and specific enough to reveal meaningful problems.

After configuration and repairs, retest. Include adjacent behavior and error states. Document open findings and vendor dependencies. Make the release decision from that evidence, not from the fact that a subscription has already been paid for.

Finally, give the owner a maintenance routine. Identify which changes need another review, who receives monitoring alerts and who can alter the configuration. Revisit the product if it no longer contributes useful value or if it begins conflicting with the site.

The principle is simple: buy the tool for a defined job, verify that it performs that job and keep responsibility for the rest of the experience visible.

Questions & answers

Questions about accessibility plug-ins

Does UserWay make a website ADA compliant automatically?

Installation alone does not prove that result. Evaluate the site’s actual behavior, identify what the product addresses and complete the remaining work. Legal compliance cannot be established from a subscription purchase or a vendor’s general marketing statement.

Is a free widget enough for a small business?

Price does not determine whether the important tasks work. A free widget may provide selected visitor controls, but the site still needs an appropriate assessment and repairs. A small site can contain a serious barrier in its only inquiry form.

Should I use a widget or fix the underlying code?

Prioritize correct content and implementation where you control them. Consider a widget for a clearly understood supporting purpose, then test it. These decisions should follow the findings rather than an assumption that one product replaces all other work.

Can a widget repair an external booking system or PDF?

Do not assume it can. A script on your website may not control a separately hosted application, embedded content or a document’s internal structure. Ask the vendor what is covered and verify those boundaries in the actual deployment.

Does a high accessibility score prove compliance?

No. A score reflects the checks and scoring method used. It does not necessarily include manual interaction testing, all pages or all states. Ask what the score measures and what evidence exists beyond it.

Will the software improve SEO or AI search visibility?

Do not buy it on that assumption. Clear, accessible content can support a better website, but a widget is not a ranking guarantee. Search and structured-data work should have its own evidence and purpose.

Who should own the subscription?

The business should understand and control the arrangement. Direct ownership can simplify continuity, while a managed arrangement can be convenient if access, renewals, records and termination are clear. Avoid a setup in which nobody knows how to recover the account.

Sources & scope

Sources and further reading

Reviewed October 20, 2026. Pricing and product terms may change. This is purchasing and implementation guidance, not legal advice.

Work with Rob

Buy a tool with a job to do.

If you are comparing accessibility products or have already installed one and are unsure what remains, I can help examine the website, the claims and the work needed around the software.

Explore website accessibility consulting or contact Rob Urban at 407-227-0741.

Scroll to Top