Less screen. More signal: How AI is changing what accessibility looks like in the enterprise.

[E-Illingworth]

There’s a pattern that shows up over and over in the history of assistive technology: A feature gets built for people at the edge of a use case — folks who can’t use a keyboard, can’t read small text, can’t navigate a complex interface the way it was intended to be navigated. It gets quietly shipped.

And then?  a few years later...everyone is using it.

Closed captions were built for the Deaf and hard-of-hearing (HoH). Now ,they’re on by default in virtually every meeting platform because ambient noise, second-language comprehension, and the simple preference for reading while listening turned out to be a universal use case.

Dark mode was an accommodation before it was a preference.

Predictive text was a disability feature before it was a productivity feature.

Zoom was access to theatre and city council meetings and cocktail hours during COVID before it was just a Tuesday.

Design for the edge, improve the center. This is the curb cut effect — and AI is accelerating it faster than any technology before it.

The new accessibility frontier isn’t a ramp. It’s an interface.

The accessibility challenges in enterprise software today aren’t primarily about physical space — they’re about cognitive load, information density, and the gap between how software was designed and how the full diversity of human workers actually operates.

Consider what it means to navigate a complex enterprise platform under pressure. A service desk agent managing a high-volume queue. A field technician updating records on a mobile device. A knowledge worker whose first language isn’t the one the UI was built for. A colleague with a processing difference who needs information presented differently to retain it. These are not edge cases. These are your workforce.

The organizations getting ahead of this aren’t treating it as a remediation problem — patching accessibility after-the-fact, chasing WCAG compliance scores, filing the VPAT and moving on.

They’re treating it as a design philosophy: build for the full range of how humans work, and you build something better for everyone.

 

What “accessibility as infrastructure” actually looks like

The shift happening in enterprise software right now is from accessibility as feature to accessibility as platform capability. That distinction matters.

A feature gets shipped, maintained, and occasionally deprecated. An infrastructure investment compounds. It shows up across every workflow, every user type, every deployment — not as a separate accommodation, but as the default experience. A few concrete examples of what this looks like in practice:

• AI-powered summarization reduces the cognitive overhead of dense, information-heavy interfaces by surfacing what matters in the moment. For someone with a processing difference, this removes a real barrier. For an agent managing 50 open tickets, it removes friction. The outcome is the same: less time navigating the screen, more time doing the work.
• Voice-first interaction removes the keyboard as a prerequisite for enterprise AI. When a platform can understand natural language and act on it, it opens the door for workers who can’t type quickly, can’t type comfortably, or simply work better by speaking. The feature built for accessibility becomes the feature preferred by everyone on a mobile device,, folks working hands-free, people simply tired of typing.
• Multilingual capability extends the curb cut effect globally. When enterprise software ships natively in a user’s language — not through a workaround, not through a third-party translation layer, but as a platform default — it removes language as a barrier to productivity and to AI. Accessibility and globalization dovetail into the same problem viewed at different angles.

The business case that moves budgets

None of this lands as a priority without a business case. Here’s the version that works.

• Market access. The global disability community represents over a billion people and trillions in economic activity. Inaccessible products don’t just exclude users — they exclude revenue. Accessible platforms expand reach, reduce support overhead, and improve retention across the board.
• Regulatory exposure. The European Accessibility Act (EAA), ADA and Section 508, and a growing body of procurement requirements mean accessibility is increasingly a legal floor, not a ceiling. In federal, regulated, and large enterprise sales cycles, a VPAT or ACR is now a deal qualifier. Accessibility is table stakes for keeping and winning contracts.
• AI ROI. Accessible AI is more usable AI. An enterprise AI investment that only works well for a subset of your workforce is an AI investment with a built-in adoption ceiling. Organizations that design for the full range of how humans work get more from their AI investments — because more of their people actually use them.

Everyone is doing AI. We’re doing AI for people. No exceptions.

 

The scaling question

The organizations that build lasting accessibility programs aren’t the ones with the biggest budgets. They’re the ones that treat it as ongoing, not episodic — embedded into how products get built, how content gets made, how workflows get designed.

That means owners, not just advocates. Champions networks, not just policy documents. Accessibility baked into the definition of done, not bolted on at the end of a sprint.

It also means making the wins visible. Real user impact stories. Features demonstrated in context. Data that connects accessibility investment to business outcomes. That’s what turns a program into a culture.

Ready to build a scalable accessibility program?

Download the Scaling A11y Playbook PDF  — a practical guide for moving from isolated efforts to a repeatable, org-wide strategy. Or reach out directly at Accessibility_Support@servicenow.com.

Questions about ServiceNow’s accessibility products and programs?

Visit the Accessibility at ServiceNow web page or contact our team at accessibility_support@servicenow.com.