How to Choose an Accessibility Tool: 10 Criteria

Opening answer

Pick the tool that changes your site code, shows its price plainly, and leaves a dated record you can show later. That test rules out most options fast.

A visitor menu alone does not change HTML, labels, or heading order in the source. A score with no record of fixes helps little when a client or a complainant asks what changed. Use the ten checks below in order, ask each vendor the same questions, and try the free step before you pay anything.

1. Fix method

Ask what changes in the source, and who approves it before it goes live. A menu that adjusts a page in the browser leaves the HTML as it was. A code fix changes labels, headings, alt text, or form names in the source itself.

What good looks like:

• Fixes land in code you can read, not only in a browser overlay.
• Each fix is tied to a page and a rule, so you can trace it.
• A person reviews changes before they go live.

2. Pricing clarity

Ask how the price is counted, and what moves it. Some tools price by site, some by page, some by monthly visits, and some by written quote.

What good looks like:

• The price unit is stated on the page, in plain words.
• The price for your site count is written down before you sign up.
• Charges for extra pages, sites, or traffic are named in advance.

3. Dated records

Ask what record you will hold in six months. A dated list of scans and fixes shows what was found, what changed, and when it changed.

What good looks like:

• Every scan and fix carries a date you can point to.
• The record names the page and the issue for each fix.
• You can share the record without asking support to build it for you.

4. Monitoring

Ask how often the tool rechecks your site, and how it tells you about new issues. Sites change with every theme update, plugin update, and new page.

What good looks like:

• Rechecks run on a set schedule, such as weekly.
• New issues trigger a clear alert, not a silent dashboard change.
• The alert names the page, so you can act on it at once.

5. Reports

Ask what report you get, and who it is written for. A developer needs selectors and rules. A client needs plain words: what was found, what was fixed, and what still needs a human review.

What good looks like:

• Reports are readable without a technical background.
• Each report separates found, fixed, and still to review.
• Paid plans offer a PDF you can hand to a client.

6. Platform fit

Ask what the tool does on your platform, not on a demo site. WordPress, Shopify, and custom built sites need different routes.

What good looks like:

• The vendor states the route for your platform before you pay.
• The route fits your team, with a plugin, a pull request, or a checklist.
• Limits for your platform are stated, not found after signup.

7. Setup time

Ask how long it takes to get a first scan and a first fix. Ask what access the tool needs, such as a plugin install, a repo connection, or theme editor access.

What good looks like:

• A first scan runs in minutes, not days.
• The access it needs is listed in advance.
• You can try the free step before handing over any access.

8. Support

Ask who answers when you get stuck, and how fast. A checklist is only useful if you can ask a question about a step.

What good looks like:

• Support covers both the tool and the fix steps.
• Help is written in plain words, not only in rule codes.
• You can reach a person when a fix blocks a launch.

9. White label

Ask what your clients see, if you serve clients. Some agencies need reports, a portal, and a badge under their own name.

What good looks like:

• Client facing pages, reports, and badges carry your name.
• You can scan many client sites from one place.
• Each client gets a separate record and a separate score view.

10. Exit options

Ask what happens when you leave. Fixes that live in your code stay with you. Fixes that live in a script stop when the subscription stops.

What good looks like:

• Code fixes stay in your codebase after you cancel.
• Your scan history and reports can be exported.
• The vendor states, in writing, what stops working at cancel.

What this looks like with Axeazy

Axeazy scans with axe-core and fixes 14 categories at code level, so the work lands in the source rather than in a browser menu. For a site with a GitHub repo, fixes arrive as a real pull request with a visible diff for owner review. For WordPress, a free plugin applies exactly 3 instant fixes at render time: a skip navigation link, a page language attribute, and an alt text fallback, with no account needed.

For Shopify, the route is a scan plus a guided plain-English checklist the merchant follows in the theme editor. Other sites get computed fix values plus a guided checklist. Contrast issues are flagged with a WCAG-correct colour value for the owner to approve before any change.

Every scan and fix is dated, paid plans give PDF reports, and paid plans include weekly monitoring. The capabilities page lists Starter at $29 a month, Pro at $79 a month, and Agency at $199 a month, while the live pricing page shows paid prices only at checkout, with annual billing saving 20 to 25 percent, so confirm the checkout figure before you buy. The Agency tier adds a white label portal, reports and badge, bulk scanning, and per client risk scoring for up to 10 client sites. Start with Axeazy's free scan, which takes about 60 seconds with no signup and no card, and compare plans on Axeazy's pricing page.

How to choose, and mistakes to avoid

Shortlist two tools, then run the free step for each on your own site, on the same pages. Ask both vendors the ten questions above. The tool that answers in plain words is the safer pick.

Three mistakes show up often. First, buying on a score alone, with no record of what changed. Second, buying a visitor menu while expecting code changes.

Third, ignoring the price unit until a busy month moves you into a higher tier. A fourth mistake is skipping the exit question, then finding that fixes stop when the subscription stops. For a price and fit comparison with one well known vendor, see: Axeazy vs accessiBe: Price, Fixes and Fit.

FAQ

How much should an accessibility tool cost?

Axeazy lists Starter at $29 a month, Pro at $79 a month, and Agency at $199 a month on its capabilities page, while its live pricing page shows paid prices only at checkout with annual billing saving 20 to 25 percent. Ask every vendor for the price for your exact site count in writing, and check whether traffic, pages, or extra sites move that price.

Does a tool make my site safe from lawsuits?

No tool can promise that, and the FTC action in January 2025 shows why bold claims about legal outcomes draw scrutiny. Code level fixes plus a dated record of the work can reduce risk. This is general information, not legal advice. If you have received a demand letter or been sued, talk to a qualified attorney.

What is the difference between a menu and a code fix?

A menu adjusts a page in the visitor browser, for that visit only, and leaves the source as it was. A code fix changes the HTML, labels, or heading order in the source, so the fix stays for every visitor. If you want fixes that last after a subscription ends, ask for the code route and a checklist you can keep.

How do I pick between two close tools?

Run both free steps on the same pages, then compare the dated records side by side. Pick the tool with the clearer price unit, the clearer record, and the route that fits your platform.

Last checked: October 31, 2026.

Sources: ADA.gov guidance on web accessibility and the ADA, WCAG 2.2, FTC order requiring accessiBe to pay $1 million.

Read the scope on Axeazy's capabilities page, then run the free scan and work through the ten checks before you choose a plan.

Related reading

• Free Website Accessibility Scan in 60 Seconds