Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How Enterprise RFPs Now Assess Vendor Accessibility Compliance
Transcript
- Lucas: So there's a new section creeping into enterprise RFPs that's catching a lot of SaaS vendors off guard. It's not about security, not about data residency, not about AI governance—it's about accessibility. And I don't mean the old checkbox where you paste a VPAT and move on. Luna: You mean the Voluntary Product Accessibility Template? I've seen those get treated like a formality. Is that changing? Lucas: Completely. I was talking to a procurement contact at a large manufacturing firm, and she showed me their latest software evaluation criteria. Accessibility now has its own scoring category, weighted at about fifteen percent of the total. That's on par with data security. And the questions are far from generic. Luna: What kind of questions are we talking about? Lucas: They're asking for an accessibility audit trail. Not just 'Do you conform to WCAG 2.1 AA?' but 'Show us your last audit, what did you find, and how did you remediate?' They want to see the dates, the specific issues, the follow-up. Luna: So they're treating accessibility like a living process, not a static document. That makes sense, because accessibility is never really done—it's like security, it evolves with the product. Lucas: Exactly. And that's where a lot of vendors stumble. They have a VPAT from two years ago, they've made some fixes, but there's no documented cycle. The procurement team sees that as a red flag. They can't verify whether the product is actually accessible today. Luna: But is that fair? Smaller SaaS companies might not have the resources to run continuous accessibility audits. Lucas: It's a fair challenge, but the market is moving that way regardless. I saw a study estimating the global accessibility market will hit twenty billion by 2027. And the legal pressure is mounting. The European Accessibility Act is already in force, and by June 2025, most software sold in the EU needs to comply. That's not far off. Luna: June 2025 is less than a year away. So if you're a SaaS vendor selling into Europe, this is urgent. Lucas: It's not just Europe either. The Americans with Disabilities Act lawsuits are climbing every year. I remember a case where a major retail chain got sued because their online checkout wasn't accessible. The settlement ran into eight figures. That's the kind of risk enterprises are trying to avoid. Luna: So the RFP questions are almost like a risk assessment. They're checking whether the vendor is going to be a liability. Lucas: Right. And they're getting granular. A few weeks ago, I saw an RFP from a healthcare software buyer. They asked for the vendor's incident response plan for accessibility bugs. They wanted to know: if a screen reader user reports a problem, what's the SLA for fixing it? Who owns it? How do you test the fix? Luna: That's a level of detail I haven't seen before. It's like they're treating accessibility issues as product defects, not feature requests. Lucas: And that's exactly the right mindset. Leading vendors are embedding accessibility into their design systems, so it's not an afterthought. They have automated testing in their CI/CD pipeline, and they do manual testing with assistive technology on every release. Luna: But isn't that expensive? I mean, hiring accessibility specialists, running audits, the tooling—it adds up. Lucas: It does, but the cost of losing a deal is higher. Let me give you a concrete example. I heard of a mid-size SaaS vendor, they were chasing a thirty-million-dollar contract with a European bank. They got to the final round, and the bank's accessibility team ran their own audit. The vendor failed on fourteen specific WCAG criteria, including some critical ones like keyboard navigation and color contrast. Luna: Ouch. And the deal? Lucas: Gone. The bank walked away, citing accessibility compliance as a risk. The vendor had a VPAT, but it didn't match reality. They hadn't tested with the latest screen readers or done the manual checks. That thirty million went to a competitor who had a more credible accessibility program. Luna: That's brutal. It's not just about checking a box anymore—it's about trust. Lucas: And it's about governance. Some RFPs now ask about the vendor's accessibility governance structure. Do you have a chief accessibility officer? Is there an accessibility council? How often does the board review accessibility metrics? This mirrors the AI governance questions we've seen in other episodes. Luna: So it's becoming a C-level issue. That raises the stakes for the whole company, not just the product team. Lucas: Exactly. And there's another angle: the CSRD. The Corporate Sustainability Reporting Directive now requires many companies to report on their digital accessibility efforts. So accessibility is part of the sustainability story. That's bringing it into the ESG conversation. Luna: I hadn't thought about that. So if you're a vendor selling to a European company that's subject to CSRD, your accessibility performance could directly affect their reporting. Lucas: You've got it. So vendors need to treat accessibility as a strategic differentiator, not just a compliance requirement. When a buyer sees a mature accessibility program, it signals quality, attention to detail, and lower risk across the board. Luna: Speaking of signals, I've noticed that some of the most forward-thinking vendors are publishing their accessibility statements publicly, with real data—like their average response time to accessibility issues. Lucas: That's a great point. Transparency builds trust. If everyone can see how well you're actually doing, that's a powerful differentiator. And it forces the internal teams to keep improving. It's a virtuous cycle. Luna: But what about the smaller vendor with limited resources? How can they realistically compete? Lucas: The good news is that accessibility doesn't have to be perfect overnight. It's about showing a credible trajectory. You can start with a baseline audit, fix the critical issues, and then implement processes to keep improving. Even a roadmap with milestones is better than a stale VPAT. Luna: So it's about progress, not perfection. That's a message that many vendors can rally around. Lucas: And here's the thing—this isn't just about avoiding risk. It's about opening markets. There are over a billion people worldwide with disabilities, many of them in the enterprise workforce. If your software is genuinely accessible, you're not just checking a box—you're expanding your addressable market. Luna: That's a compelling business case. And it's one that resonates with the mission of this podcast. Actually, you know, these conversations take time to research and produce, and they're only possible thanks to listener support. If you're getting value from these episodes, a couple of dollars a month at buy me a coffee dot com slash fexingo genuinely helps keep them going. Lucas: Yeah, it's a small way to keep this ad-free and sustainable. We appreciate everyone who does that. Now, back to the practical side—what should a vendor do this quarter to start building that credibility? Luna: I'd say first, get a baseline. Run a proper WCAG audit, not just a quick scan. Identify the critical issues and fix them within ninety days. Lucas: Absolutely. And then embed accessibility into your development process. Add automated checks to your CI/CD pipeline, and schedule manual testing with screen readers at least once per quarter. The key is to show that you have a repeatable process. Luna: And don't forget to document everything. The RFP evaluators will want to see the evidence. Lucas: Right. Keep an accessibility log with dates, issues found, and resolutions. That's going to be your gold mine when you're responding to RFPs. And consider publishing an annual accessibility report—it's a strong signal of maturity. Luna: What about the governance piece? Should every vendor have a chief accessibility officer? Lucas: Not necessarily a full-time CAO, but you need a designated owner with executive sponsorship. That person can be the head of product or engineering, but they need visible authority. In RFPs, they're looking for accountability, not a title. Luna: And for the buyer side, what should they be asking beyond the standard questions? Lucas: Ask for a live demonstration of accessibility features. Have the vendor walk you through the product using a screen reader. That's the most convincing evidence. And ask for their last two accessibility audit reports—if they're hesitant to share, that's a red flag. Luna: It sounds like accessibility is becoming a differentiator, not just a checkmark. And the vendors who embrace it early will have an advantage. Lucas: Exactly. The next year is going to be pivotal. With the European Accessibility Act deadline looming, we're likely to see a lot of vendors scrambling. But the smart ones are already building this into their DNA. And that's going to pay off in the long run. Luna: So if you're a builder or an operator, the takeaway is clear: start treating accessibility like you treat security—as a core part of your product's quality. Not just because it's the right thing to do, but because the market is demanding it. Lucas: And it's a great way to stand out in a crowded RFP process. When every vendor has a VPAT, the one with a real accessibility program will get the attention. That's the edge you want.