The hidden but costliest blunder in budgeting for website and digital products
By Anne-Mieke Bovelett on June 4, 2026
Status: up to date
If you miss this, you create cost and loss of revenue!
If your CFO can’t tell you what your inaccessible website, digital products or your customer service are costing you right now, you have a serious management problem. It’s 2026, not 2016!
I know, I know, once you try to get clarity about this, it will probably get framed to you as a technical problem that is or was too expensive to resolve. Once you truly understand how this happened, you will understand how this is intelligence-insulting reasoning at its finest.
Every organization running a digital product is losing money to accessibility barriers. The conversion losses are real, the support escalations are real, and the customers who left without ever telling you why are real. The question is not whether this is happening to you. The question is whether anyone in your organization is measuring it. If the answer is no, you are just guessing at your digital product instead of managing it.
This article is about what those numbers actually look like, and why the conversation about accessibility belongs in the budget meeting, not just in the developer backlog.
You are losing customers who will never complain
Let me give you the figure that should end every argument about whether accessibility affects the bottom line.
The spending power you are not seeing
At the time of publishing this article, it’s seven years since the Click-Away Pound 2019 report was published, and according to that report, 69 percent of disabled online consumers simply leave a website they find difficult to use. That is 4.9 million active online shoppers in the UK alone, with a combined spending power of £17.1 billion per year, roughly 10 percent of total UK online spend, going to competitors with more accessible products. Three years before that, in 2016, the same research found the figure was £11.75 billion. So it grew by 45 percent in three years, because more people came online and found things exactly as broken as before.
Why it does not show up in your analytics
The reason most organizations do not see this in their data is equally alarming. Fewer than one in ten disabled customers who struggle with a website will contact the company to report it. The other nine leave without a word, find an accessible alternative, which 83 percent of disabled online shoppers actively seek out, and spend their money there instead. If your analytics show a drop-off at checkout, a spike in bounce rate on product pages, or flat conversion from a specific user segment, accessibility barriers are a structural candidate for what is driving it.
These customers are not waiting for a discount
The Click-Away Pound data also contains a finding that makes the commercial argument even harder to dismiss. 86 percent of disabled online shoppers have chosen to pay more for a product from an accessible website rather than buy the same product at a lower price from a website that was harder to use. These are not reluctant customers who need discounts to stay. They are customers actively trying to give you money, and being turned away by your own product.
What the numbers look like in e-commerce
The accessibility barrier is not a niche problem sitting at the edges of the customer base. It sits in the most commercially critical part of the journey. Every time you assume it does not apply to your business, you either walk away from revenue and you run into cost, and probably it’s both.
The most broken moment in the funnel
The Qualtrics XM Institute Consumer Journeys Needing Improvement report 2025, based on 10,000 US consumers across 354 organizations in 22 industries, found that finding and selecting the right product or service is the most broken customer journey in retail, grocery, hotels, insurance, car rental, and investment. Consumers who encounter a broken journey score NPS an average of 34 points lower than those who do not. For banks and TV or internet service providers, that gap rises to 43 to 48 points. An inaccessible product page creates exactly the kind of broken journey this research is describing, at the exact moment in the funnel where a customer was about to spend money.
The repurchase gap in Germany
The Qualtrics XM Institute ROI of Customer Experience report 2025, based on 23,730 consumers across 23 countries, adds a Germany-specific figure that is difficult to sit with. Just 19 percent of German consumers intend to purchase more from a company after a poor experience. That is the lowest repurchase intent of all 23 countries in the study. After an excellent experience, that figure rises to 56 percent. The difference is a factor of three. In online retail specifically, the contrast is even starker: 41 percent repurchase intent after a poor experience, 86 percent after an excellent one.
When accessibility barriers push a customer experience from excellent into poor, that factor-of-three applies directly to every repeat purchase that does not happen.
When a broken journey becomes a support call
And when a customer cannot complete a task through your digital product, they do not disappear quietly. They reach for a phone or open a live chat. Gartner benchmarks (Gartner subscription required) the median cost of a self-service contact at $1.84. The same contact handled through a live channel costs $13.50. That is a factor of more than seven. Every user who fails to find information, complete a form, or navigate a product page on an inaccessible site moves from the $1.84 channel to the $13.50 channel. At any meaningful transaction volume, this is a significant operational line item, sitting in the support budget, where nobody connects it back to the product decision that caused it.
The support cost that nobody is tracking
Digital support is already the weakest link in the customer journey, independent of accessibility. The Qualtrics XM Institute Consumer Trends Report 2024, based on 28,400 consumers across 26 countries, found that customer satisfaction during digital support is 22 percentage points lower than satisfaction at the point of purchase. That is a gap before you factor in what accessibility barriers add to it.
What fixing it is actually worth
The upside, for organizations that fix it, is proportionally large. Customers who have a positive digital support experience are 2.7 times more likely to return. That is the highest return multiplier of any channel and journey combination in the study. The financial logic is straightforward: accessible self-service works, customers complete what they came to do, they do not escalate to a human agent, and they come back.
The accessibility finding buried in a customer service report
A Deloitte study on customer service in Germany (in German) found that self-service via online channels frequently fails because the information provided is either insufficient or, in the original German phrasing, “schwer zugänglich,” which means difficult to access. That is an accessibility finding published in a customer service report. The research community is documenting accessibility failures without using the word accessibility, and the cost is landing in the support budget while the product team remains unaware.
What German consumers do when self-service fails
The Yext Kundenservice-Studie 2023 (in German) makes the behavior pattern concrete. 90 percent of German consumers want to solve problems independently before contacting anyone. But more than half of those who used a help page said they had been put off a purchase because the section did not provide what they needed. One in five ended up buying from a different company because the search function on the help page did not work. Among 18 to 34 year olds, that figure rises to 36 percent.
If these sound like fringe scenarios, they are not. This is the dominant consumer behavior, and inaccessible digital products are systematically failing it.
B2B carries the same costs with less visibility
The assumption that accessibility is a consumer market issue runs deep in B2B organizations, and it is wrong.
The most broken B2B journey is not the one you think
The Qualtrics XM Institute State of B2B Customer Experience Management Report 2025, based on 140 CX practitioners at organizations with more than 1,000 employees, found that 50 percent of B2B organizations identify service and support handling as their most broken customer journey. That places it above delivery performance, account relationship quality, and product quality. The client portal that nobody can navigate with a keyboard, the documentation platform that a screen reader cannot interpret, the procurement system that times out during form completion because it was never tested under assistive technology conditions: in B2B, these are operational reality, not edge cases.
Why nobody is connecting the dots
What compounds the problem is the measurement gap. Only 14 percent of B2B CX practitioners can point to a specific monetary benefit from their CX program that their budget holders recognize. 47 percent believe there is monetary benefit but cannot quantify it. When you cannot trace support volume, account churn, or renewal friction back to a specific barrier in the digital product, the problem gets misattributed to staffing, training, or account management. More often it is a product quality problem, and accessibility is a structural part of that.
B2B sales cycles are expensive to run and expensive to lose. A customer relationship that took 18 months to close and requires a digital product to maintain deserves the same product quality standard as any consumer product. The argument for protecting it through accessible digital infrastructure is at least as strong.
Non-profits cannot afford to ignore this either
Non-profit organizations tend to treat accessibility as something they should care about in principle while deprioritizing it in practice. Budget pressure is real, the technical team is small, and the mission understandably takes priority.
The mission is exactly the argument for accessibility
Non-profits depend on user action at every level: donations, volunteer registrations, grant applications, service access, event sign-ups, information campaigns. Every one of those journeys runs through a digital product. Every accessibility barrier in that product reduces completion rates. A donation form that fails for a screen reader user is a donation that does not happen. A volunteer sign-up that breaks on mobile with accessibility settings enabled is a person who wanted to help and could not.
When the organization exists to serve the people it is blocking
The Click-Away Pound data was collected from retail, but the mechanism is identical for non-profits. Disabled users who encounter barriers leave and find an alternative, or abandon the task entirely. And fewer than one in ten will tell the organization why. A charity running a fundraising campaign with an inaccessible donation page has no reliable way of knowing how much the inaccessibility is costing it in real time. That is a strategic problem, and it belongs in the leadership conversation.
Non-profits with public service mandates frequently serve populations that are more likely to use assistive technology, not less. Older adults, people with chronic illness, people with disabilities: these are often the populations a non-profit exists to serve. An inaccessible digital product in that context is a delivery failure at the core of the organization’s purpose, not simply a missed revenue opportunity.
The argument for starting before the build
The article so far has described the cost of inaccessibility. This section is about when the cost originates.
Where the problem was actually created
Most accessibility problems that reach a developer mid-sprint were not created in development! They were created in a planning meeting, a design brief, a component library selection, or a content strategy document where nobody asked the accessibility question. By the time a developer is fixing a form label or rebuilding a navigation structure, the organisation has already paid for the decision twice: once when the wrong choice was made, and again when it was undone.
The car recall you never saw coming
It’s the same situation that is probably a lot more familiar to you: when a car gets recalled.
The engineers assembled it correctly. They built what they were specced. But somewhere upstream, a procurement decision chose a cheaper component, a design approval signed off on something that had not been tested under real-world conditions, and by the time the problem became visible, the car was already in two hundred thousand driveways. The recall does not cost what the faulty part costs. It costs what it takes to reach every car that already left the factory.
Accessibility debt follows the same logic. Every page, every form, every navigation structure built on a flawed upstream decision is another car that left the factory. The longer the flaw stays in the design system, the component library, or the brief, the larger the recall. And the people running the recall are the developers, fixing decisions they had no part in making.
Why the cost of waiting compounds
Research on software development cost consistently shows that fixing a problem at the requirements stage costs roughly 15 times less than fixing the same problem after deployment. Accessibility problems are not different. A color palette chosen without contrast checking during brand development costs a design hour to fix. After launch, with brand guidelines published and the design system locked, fixing the same contrast issue costs a design sprint, a developer sprint, and a QA cycle.
A stakeholder who signs off on a component library, a design system, a CMS, or a development framework is making an accessibility decision at that moment, whether they know it or not. If accessibility criteria are not in the selection process, the cost of that decision gets deferred into the product, the support queue, and the customer churn data where nobody will connect it back to its origin.
The question that should be in every budget meeting
The budget meeting is where accessibility actually gets decided, even if nobody uses the word.
Every time an organization approves a platform without accessibility requirements in the RFP, sets a launch date without time for an accessibility review, or signs off on a content management workflow with no process for alt text, accessible video, or plain language review, it has made a decision. It just has not named it. Every one of those decisions moves cost downstream.
The organizations that handle this well tend to have clearer briefs, earlier decisions, and a shared understanding across teams that accessibility is a product quality standard, not a specialist niche. That understanding does not come from the development team. It comes from the people who set the brief, control the budget, and define what a finished product means.
If that conversation is not happening in your organization, the cost is already accumulating. You are simply not measuring it yet.
The first step to fixing that is deciding that it is a number worth knowing.