What Does Accessibility ROI Look Like in Real Numbers?

Quick Answer

Accessibility ROI compares what you spend on accessibility with what you gain, but no single number fits every organization. Some of the strongest public numbers come from government studies and research data. They show the shape of the return, not your own payback.

• The US Department of Justice (DOJ) estimated in 2024 that its web rule for state and local governments would bring annualized monetized benefits of about $5.0 billion to $5.2 billion, mostly to society. DOJ's April 2026 notice refers to an analysis of the longer compliance schedule that estimated 10-year average annualized net benefits of $1.3 billion at a 7 percent discount rate. These are public-sector estimates, not a forecast for a private business.
• The 2024 analysis estimated $16.9 billion in implementation costs over the first three years, followed by about $2.0 billion a year in operating and maintenance costs. DOJ estimated that costs would generally be below 1 percent of revenue for the public-entity categories it examined, with small independent community colleges as an exception.
• WebAIM found that 95.9 percent of home pages had detectable WCAG failures in February 2026, and six error types made up 96 percent of all errors.
• The World Health Organization estimates that 1.3 billion people experience significant disability.

Introduction

A common question in accessibility budget discussions is what the investment will deliver.

Some widely repeated accessibility figures are difficult to verify or are used without their original context. Others mix up the size of a market with the money one company can earn.

Real numbers do exist, though. Governments study costs and benefits before they write a rule. Health agencies estimate how many people live with disability. Testing studies count errors on websites today. Each answers a different question, and none tells you what your own company will earn.

This guide puts these numbers side by side and shows what each can and cannot prove. Then it shows you how to build a return figure from your own data.

What Counts as a Return on Accessibility?

A return on accessibility is any gain you can trace back to making your digital products easier to use for people with disabilities, compared with what you spent to get there. Revenue is only one part of it.

The W3C Web Accessibility Initiative groups the benefits into four areas in its business case for digital accessibility. They are driving innovation, enhancing your brand, extending your market reach, and minimizing legal risk.

To make the counting easier, it helps to sort returns into three simple buckets.

• Money earned. Removing an accessibility barrier may allow more people to complete tasks such as signing up, buying or booking.
• Money saved. Addressing accessibility during design can reduce later rework, although the actual savings depend on your product and your development process.
• Risk reduced. Barriers you remove can lower your exposure to complaints and legal action. Treat this as risk management. Count a money value only when you have a sound basis for estimating it.

Brand and trust matter too, but they are hard to price. Describe them in words and keep them out of your ROI formula.

What Do Government Accessibility ROI Numbers Actually Show?

One of the most detailed publicly available accessibility cost-benefit analyses comes from the DOJ. It supports the rule that tells US state and local governments to make their websites and mobile apps meet WCAG 2.1 Level AA. Every figure in this section concerns that public-sector rule. They are regulatory estimates, not forecasts for a private business.

Start with the 2024 analysis. On the cost side, it includes $16.9 billion in implementation costs during the first three years, before discounting. After that, it counts $2.0 billion a year in operating and maintenance costs over the next seven years. These are estimates under the original compliance schedule, not a cost benchmark for any other organization. DOJ estimated that the costs for each type and size of government entity would generally be below 1 percent of revenue. The one exception was small independent community colleges, at just over 1 percent.

On the benefit side, the 2024 analysis found annualized monetized benefits of about $5.2 billion at a 3 percent discount rate and $5.0 billion at a 7 percent rate. It put a dollar value on time savings for users and educational attainment. Gains like independence and privacy were described but not priced. DOJ concluded that the monetized benefits to society outweigh the costs, with net annualized benefits of $1.9 billion at 3 percent and $1.5 billion at 7 percent.

Now the 2026 update. In April 2026, DOJ extended the compliance dates by one year. Public entities with a total population of 50,000 or more now have until April 26, 2027. Public entities with a total population below 50,000, and any special district government, have until April 26, 2028. The technical standard remains WCAG 2.1 Level AA. The 2026 notice also refers to a regulatory analysis for the longer compliance schedule, which estimated 10-year average annualized net benefits of $1.3 billion at a 7 percent discount rate. DOJ said it could not quantify the effect of the extension itself on benefits or calculate its impact on net benefits. The two findings should not be confused.

Now the caution. The benefits go to everyone who uses these government sites, and the rule covers only state and local governments. The below 1 percent finding applies to the public-entity categories DOJ examined. It does not tell a private business what accessibility will cost or return.

What can you take from this? The method. DOJ separated implementation costs from ongoing costs, counted only benefits it could measure, and listed the rest in words.

How Much of the Disability Market Can Your Business Reach?

Market numbers tell you how many people you might serve, not how much you will earn.

The WHO estimates that 1.3 billion people experience significant disability, which is 1 in 6 of the world's population. That number describes people, not customers.

A second WHO figure describes the need for assistive technology. The WHO's assistive technology fact sheet says more than 2.5 billion people need one or more assistive products, and 3.5 billion will need assistive technology by 2050. The figures show the broad need for assistive technology, but they should not be treated as estimates of demand for digital accessibility tools. The people who visit a particular website, and the assistive technologies they use, depend on its audience and the tasks they need to complete.

The most important point is this. Market size is not revenue. Your real market is the part of that group who want what you sell, can find you, and can finish the task on your site.

To make a market estimate useful for your business, start with your own customers. Look at survey replies, support requests, and feedback that mention barriers. Run usability sessions with disabled users on your key pages. Do not guess who has a disability from browsing data.

What Does Inaccessible Content Cost an Organization?

Inaccessible content can cost money in four main ways.

• Lost customers. Someone who cannot finish checkout or a booking form may leave.
• Extra support load. People who get stuck may call, chat or email for help.
• Rework. Fixing a problem after launch can take more effort than preventing it during design.
• Legal and regulatory exposure. Rules in some regions require accessible products and services. This is a risk to manage, not a saving to count.

Here is a simple way to think about the first one. Let V be the number of people who start checkout each month. Let B be the share who get stuck because of an access barrier. Let A be your average order value. If every one of those people would otherwise have bought, the sales at risk each month would be V times B times A. That is an upper bound, not a measured loss. This is a made-up scenario, not a real result. To get a true figure, measure actual abandonment on the affected step and compare it after you fix the barrier.

The rules also come with dates. The European Accessibility Act requirements have applied since June 28, 2025, to covered products placed on the EU market and covered services provided to consumers, subject to transitional provisions and exemptions. The full legal text is in Directive (EU) 2019/882. The EU's Your Europe guidance lists online shops, ticketing platforms and banking services among the examples.

The Act exempts qualifying microenterprises that provide services. The Directive defines a microenterprise as one with fewer than 10 persons and either an annual turnover or an annual balance sheet total not exceeding 2 million euros. The exemption does not apply in the same way to every business or product category, so check the Directive and the rules for your own activity. Your Europe also says a business can claim that the rules are a disproportionate burden, and that claim needs evidence.

The rules differ by country, sector and company size, so ask your legal team which ones apply to you.

Which Accessibility Improvements Should You Measure First?

The WebAIM Million tests the home pages of one million websites with automated tools. The February 2026 results found an average of 56.1 errors per page. Six error types made up 96 percent of all errors.

A short list of repeating problems covers most of what tools detect. Fixing them lets you compare detectable error counts before and after the work. You still need user-focused testing to learn whether people can complete their tasks.

Be careful with what this data cannot do. It comes from automated testing, so it counts only the errors a tool can detect. It shows what is common, not what pays back, and a page can pass every automated check and still be hard to use. Use it as a place to start measuring, not as proof of return.

Alternative text is a good place to begin, since it is missing on more than half of the pages in the study. Our post on writing useful alt text shows what good descriptions look like. If you want to run your first checks, this guide on how to test your site for accessibility walks you through the steps.

How Do You Calculate Your Own Accessibility ROI?

You calculate your own accessibility ROI by adding up the benefits you can measure, subtracting your total investment, and dividing the result by that investment. Then you repeat it on a schedule.

Start with the formula

ROI (%) = (measured benefits minus total investment) divided by total investment, multiplied by 100.

The result means something only when you define a measurement period, such as the first 12 months, include every relevant cost, and attribute a benefit to your accessibility work only when you can reasonably show the link. Do not copy a percentage from a government study or a vendor page into this formula.

Split your benefits into two groups.

• Financial benefits you can measure. These include extra revenue you can attribute to the work, verified drops in support handling costs, documented staff time saved, and less rework.
• Benefits and risks that are hard to price. These include greater independence, better access, privacy, user trust, and lower exposure to complaints or legal action. They belong in your business case, but do not give them a money value without a sound method.

List the costs that belong in it

Like DOJ, split your costs into start-up parts (the first audit, design changes, training) and ongoing parts (regular testing, fixes for new releases).

Choose measures that show whether the fixes worked

Pick three to five measures and record them before you fix anything.

• The task completion rate on your key journeys, such as sign-up, checkout, or booking
• The number of automated errors on your main page templates
• The number of support contacts that mention access problems
• The time users need to finish a form
• The result of a manual test with a keyboard and a screen reader

External accessibility testing can give you an additional assessment of key journeys, alongside your own testing and feedback from users with disabilities.

One privacy note matters here. Do not try to detect assistive technology use in secret to count disabled visitors. It is invasive and can be wrong. Use opt-in surveys, usability sessions, and voluntary feedback instead.

Why Is Accessibility ROI Sometimes Hard to Prove?

There are four common reasons. First, you usually change many things at once. If sign-ups rise after a redesign, you cannot say how much came from accessibility. Second, results take time, and benefits arrive at different speeds. Third, avoided costs never show up on a ledger. A complaint that never arrives leaves no record. Fourth, market numbers are estimates built on choices about who to count.

The W3C says as much. Its business case guide notes that ROI is important but not the only way to measure the benefits of an accessibility commitment, and that a good case describes the cost and risk of doing nothing.

That advice helps when money gets tight and returns are hard to see. Our article on keeping your accessibility commitment during an economic slowdown offers practical ways to protect the work when budgets shrink.

The fix is not to hide the gaps. Show the numbers you can prove, label estimates as estimates, and describe the rest in words.

What Should You Do Next to Build a Credible Business Case?

Here is a simple plan you can start this month.

1. Pick the two or three journeys that matter most to your business, such as sign-up, checkout, or support.
2. Test those journeys with automated tools, manual checks, and real users with disabilities to set a baseline.
3. Write down your costs from the start, split into one-time and ongoing.
4. Choose three to five measures from the list above and record their starting values.
5. Fix the most common problems first, then measure again every quarter and report both the numbers and what real users told you.

Share the results with finance and legal together, using the same sources.

Conclusion

Accessibility can produce measurable returns, but their size and type vary by organization. Some important benefits are not easily expressed in money. One of the most detailed public studies, from the DOJ, estimated that monetized benefits to society outweigh costs for state and local governments under the rule's analysis. It does not predict the return for a private business. Your own return comes from your own costs and measures. Start with a baseline, count what you can, describe what you cannot, and check again every quarter.

Frequently Asked Questions

What is a good ROI for accessibility?

There is no standard figure that fits every organization. The result depends on your costs, your audience, and what you measure. Build your number from your own baseline and compare it with yourself over time.

Does accessibility really pay for itself?

It can, but it depends on your costs, your audience and what you can attribute to the work. DOJ's analysis found that monetized benefits to society outweigh the costs for the public sector, but it does not predict a private company's result. Only your own data can answer this.

How much does accessibility cost?

It depends on the size and condition of your site, the standard you must meet, and how much work you do in-house. DOJ estimated that costs would generally be below 1 percent of revenue for the public-entity categories it examined, but that finding does not tell a private business what to expect. Ask for an audit to get a number for your own site.

Which accessibility metrics should I track first?

Start with task completion on your key journeys, automated error counts on main templates, and support contacts that mention access problems. Add a manual test with a keyboard and a screen reader. Record all of them before you fix anything.

How long does it take to see a return?

It depends on what you measure. Detectable error counts can drop soon after a fix. A financial return can take longer, and it may not come from accessibility work alone. Review your measures every quarter and compare each result with your starting baseline.

Does the ADA Title II web rule apply to private companies?

The DOJ's Title II web accessibility rule applies to state and local government entities, not private companies. Private businesses may still have obligations under other parts of the ADA, including Title III, as well as other accessibility laws. The requirements depend on the organization, the service, the jurisdiction and the circumstances.

Further Reading

Digital Accessibility as a Competitive Advantage