Change Management in digital Accessibility - AI-generated

00:00:00: Imagine for a second, right?

00:00:01: That we just funded the most ambitious construction project in human history.

00:00:06: Okay I'm picturing it!

00:00:07: Yeah so we built this sprawling breathtaking metropolis...I mean We laid down fiber optic grids poured millions of miles of concrete and engineered these like massive skyscrapers that touch the clouds.

00:00:21: Sounds pretty incredible Right

00:00:23: but then right as were about to cut the ribbon we realized something completely horrifying For about One in six people trying to enter this city.

00:00:31: We just completely forgot to build the doors.

00:00:33: Yeah, I mean it is a staggering oversight when you frame it physically like that.

00:00:38: But you know In The Digital Realm That Is Exactly What we Have Done.

00:00:41: It Really Is.

00:00:42: And Well Welcome To A New Deep Dive.

00:00:44: Today We Are Looking At A Stack Of Consulting Materials Research Papers and Case Studies That All Zero In On One Massive Bottleneck

00:00:53: Change Management For Digital Accessibility.

00:00:55: Its Exactly Our mission today for you listening is to figure out why in an era where we can I mean beam high-definition video from Mars We still build websites that millions of people literally cannot use and we are going specifically effort the hidden deeply human roadblocks.

00:01:15: That caused this

00:01:16: Because the very first premise we have to accept from this research, and this is crucial... ...is that digital accessibility is almost never an actual technical problem.

00:01:25: Okay

00:01:26: let's unpack this because I am immediately skeptical of that!

00:01:29: I mean i hear The Technical excuse all-the time for engineering change.

00:01:32: Right

00:01:32: constantly

00:01:33: yeah right they say things like well our technology stack as a monolith.

00:01:36: or uh We're dealing with twenty years of legacy code?

00:01:39: We simply cannot rewrite Our entire platform To support screen readers.

00:01:43: Yeah it sounds Like A totally valid defense on the surface.

00:01:46: But if you look at the mechanics of modern software development, it is largely an illusion.

00:01:49: Really?

00:01:50: How so

00:01:50: Well ten or fifteen years ago sure You had these tightly coupled monolithic systems where changing a button could literally crash database.

00:01:58: Right The spaghetti code era.

00:02:00: Exactly Yeah.

00:02:01: but today I mean we operate on microservices.

00:02:05: We have decoupled front-ends Headless content management system APIs that just talk to each other seamlessly.

00:02:11: Technology is inherently modular now.

00:02:13: It's constantly evolving

00:02:14: so the tech Is actually very capable of adapting extremely

00:02:17: capable.

00:02:18: So if an organization points to their tech stack as The reason they can't implement accessibility what They are Actually revealing, it's a deeply ingrained inflexibility in Their culture.

00:02:27: wow yeah If they cannot cope with the minor technological Shifts required to say add semantic HTML or basic keyboard navigation I guarantee they're likely struggling with basic security updates and feature staling as well.

00:02:40: So the technology is really just the scapegoat for bad organizational habits

00:02:44: precisely.

00:02:45: I see okay, so if The code itself isn't the real blocker then the problem rests squarely on the shoulders of the people making the decisions about that Code.

00:02:53: let's look at the first major human roadblock detailed in our stack of research.

00:02:57: it's this pervasive myth the invisible customer.

00:03:01: Yes,

00:03:02: this is

00:03:02: a fascinating cognitive blind spot particularly prevalent in the e-commerce sector.

00:03:07: The specific example and the case studies is well.

00:03:09: It's almost comical if it wasn't so damaging.

00:03:12: There is this persistent assumption among high level decision makers that Blind people simply do not use computers right?

00:03:20: And then the secondary assumption Is that even if they somehow did They certainly wouldn't be browsing the internet to buy like brand name running shoes

00:03:28: which just demonstrates a profound misunderstanding of how modern assistive technology works.

00:03:34: I mean, people who are blind or individuals with severe motor impairments.

00:03:39: They use smartphones and computers constantly.

00:03:42: Yeah, it's not the nineties anymore exactly.

00:03:44: a screen reader doesn't just read text out loud It interacts with the document object model The underlying structure of web page which allows a user to navigate complex interfaces fillout forms And yes by running shoes completely independently.

00:03:58: So assuming this demographic doesn't exist Just because you don't personally see them in your daily life is A massive failure market analysis?

00:04:06: Let me play devil's advocate for a second.

00:04:07: For you, the listener who might be running a purely data-driven business You are looking at your conversion funnels right?

00:04:14: Your daily active users.

00:04:16: sure you might be thinking look I am running a business here not a charity.

00:04:21: Why should i dedicate entire engineering sprints to what my analytics perceive as A tiny niche demographic?

00:04:29: isn't this just in numbers game?

00:04:31: What's fascinating here is how quickly that pure numbers game argument actually collapses under scrutiny.

00:04:37: Let's start with just the regulatory environment, okay?

00:04:39: We are seeing a massive global tightening of digital compliance.

00:04:43: you have the GDPR setting up precedent for Digital Rights and now The European Accessibility Act.

00:04:49: in Germany For example That was implemented as the BFSG the Barry Freyheitz-Starkings adzex.

00:04:54: Wow Okay quite the mouthful there but what does it do when practice?

00:04:58: In short, it mandates that by twenty-twenty five every day digital products and services provided directly to consumers.

00:05:03: So we're talking e-commerce sites banking apps books.

00:05:07: they must be accessible period.

00:05:08: this

00:05:08: is for the private sector

00:05:10: yes And that's The Big Shift.

00:05:12: unlike previous guidelines That really only targeted government websites This targets private companies.

00:05:18: It brings the threat of genuine financial penalties and literal market exclusion.

00:05:23: so the legal stick Is very Very Real.

00:05:26: Okay, so there's this tech.

00:05:27: But the research also points to a massive demographic.

00:05:30: caret too

00:05:30: precisely.

00:05:31: let's talk about The Numbers game from a demographic perspective.

00:05:34: global populations are aging rapidly and you know aging brings A whole host of physiological changes that impact digital interaction.

00:05:42: like.

00:05:42: what kind Of Changes?

00:05:44: Well, we are talking about macular degeneration reducing contrast sensitivity which makes that trendy light gray text completely invisible.

00:05:51: We're talking about mild tremors.

00:05:53: That make clicking a tiny two pixel wide checkbox basically impossible on the phone.

00:05:58: Oh right so this isn't just about someone who is completely blind?

00:06:02: not at all.

00:06:02: there Are millions of older adults?

00:06:04: Who would never ever classify themselves as disabled, but they're finding complex low contrast online shops completely overwhelming to use.

00:06:13: Yeah that makes sense.

00:06:14: and This is an incredibly lucrative growing target audience with significant purchasing power.

00:06:21: When a company builds in inaccessible site They are actively locking out a massive segment of their own market.

00:06:28: Wow leaving money on the table.

00:06:29: So how do you break through?

00:06:31: To say A product manager who was still dragging their feet on this, materials give us this tactical pivot which is basically stop bringing spreadsheets to the meeting and start bringing empathy.

00:06:43: Yeah it hands down the most effective way to shatter that cognitive blind spot.

00:06:48: The strategy outlined in the text is just brilliant.

00:06:50: you take that thirty-something able bodied manager.

00:06:53: You turn on the voiceover or talk back feature On your very own smartphone And ask them to navigate Their own checkout process blindfolded.

00:07:00: It's a real wake up call

00:07:01: Oh, I bet.

00:07:02: While they are swiping endlessly and getting completely lost you just ask them hey do You want your own grandparents to be able use this?

00:07:08: or?

00:07:08: Do you not

00:07:08: care?".

00:07:09: And that completely shifts the conversation.

00:07:11: it moves It from this abstract compliance issue To a feeling of visceral frustration.

00:07:16: when a developer Or manager physically experiences The friction Of their own interface like When They hear A screen reader Just say button-button link with absolutely no context because their code is sloppy, it sparks a fundamental shift in ambition.

00:07:31: Suddenly they actually want to fix

00:07:33: it.".

00:07:34: That's powerful but we do have to make a sharp distinction here based on the industry because the consulting materials highlight that while this empathy pitch works wonders and e-commerce...it hits.

00:07:48: Yes.

00:07:49: If you transition into the financial sector, so online banking insurance portals things like that empathy is rarely.

00:07:58: The culture is just built entirely differently.

00:08:00: Because banking has already so heavily regulated?

00:08:02: Exactly!

00:08:03: In banking, literally everything about risk mitigation and audit trails.

00:08:07: A product manager in finance might personally feel terrible that an older user can't navigate their mortgage portal But they cannot allocate a quarter million dollars of engineering resources based on feelings.

00:08:18: Yeah...that's not going to fly with the board

00:08:20: Right..in this environment you have to lean heavily onto strict statutory requirements or regulatory action is what actually unlocks the budget.

00:08:30: You really have to speak the language of their

00:08:32: room.".

00:08:33: Okay, here's where it gets really interesting!

00:08:35: Let's assume you've spoken the language—you made The Empathy Pitch in retail —or you cited the BFSG and banking— leadership is fully on board...the budget is approved….

00:08:45: Why then do we still see these projects launch six months later with absolutely terrible accessibility scores?

00:08:53: because organizations overwhelmingly treat accessibility as an overlay.

00:08:57: They fall right into the end of project trap.

00:08:59: I was trying to give a good analogy for this while reading and it reminds me of the company trying to implement like, end-to-end security encryption after they've already built the database launched the app And populated with a million users.

00:09:11: That is a highly accurate comparison.

00:09:13: It's complete architectural nightmare.

00:09:16: What happens is the product team goes through the entire design and development life cycle.

00:09:21: They build out all of the shiny new features, they launch a schedule for next Thursday... And then at the very end….

00:09:27: ...they run an automated accessibility stand or hire a consulting firm to do quick

00:09:32: check!

00:09:32: Just checking in a box?

00:09:33: Oh!

00:09:33: Then the scan comes back completely glowing red.

00:09:36: Exactly It spits-out hundreds of foundational errors.

00:09:41: The contrast ratios are wrong across the color palette Interactive elements are completely hidden from the keyboard and fixing these fundamental structural issues at the eleventh hour.

00:09:51: It basically requires tearing down the entire code base, it completely blows up the launch schedule... And then on fairly Accessibility gets blamed as the bottleneck when in reality, the flawed process was the bottlenecked.

00:10:03: It's like painting a house before you pour the foundation.

00:10:06: so how do we restructure the process?

00:10:08: So that doesn't happen.

00:10:09: yeah phrase using the research is structural embedding.

00:10:11: yes

00:10:12: Structural embedding.

00:10:13: it means accessibility must become a non-negotiable criteria at every single stage of the pipeline.

00:10:19: it starts way Before A Single Line Of Code Is Written

00:10:23: in the design phase.

00:10:24: Exactly!

00:10:25: Designers need to have accessibility criteria like minimum color contrast ratios and scalable font sizes hard-coded directly into their design systems.

00:10:34: Okay,

00:10:34: what about for the engineering side?

00:10:36: For

00:10:36: developers it has to be baked into the CICD pipeline.

00:10:40: Let me pause you there just because not everyone listening lives In The DevOps World.

00:10:44: How does that pipeline mechanism actually work To prevent these errors?

00:10:48: Sure.

00:10:49: So CICD stands for Continuous Integration and Continuous Deployment.

00:10:54: Think of it as a highly automated conveyor belt for code.

00:10:57: Okay When a developer writes new piece of code, tries to merge into the main application That code has passed through a series of automated checkpoints on the conveyor belts

00:11:06: Like automated testing scripts checking for bugs

00:11:09: Exactly.

00:11:09: And we can inject tools like XCore or other headless browser testing suites directly into that exact pipeline.

00:11:16: Oh, that's smart!

00:11:16: Yeah.

00:11:17: so if a developer forgets to add an ARIA label to a button... ...or they create a form field without a structural label the pipeline literally physically rejects the code.

00:11:27: it fails the build

00:11:28: So they can't even push it live?

00:11:29: Nope

00:11:30: The developer gets immediate feedback within seconds.

00:11:33: They fix the tiny error right then and there And the code base stays clean from day one.

00:11:38: But there is a massive hidden vulnerability mentioned in the case studies that can bypass that entire beautiful automated pipeline, third-party integrations.

00:11:47: Ah yes this where even really well intentioned companies stumble hard.

00:11:53: Yeah because marketing or sales will decide hey we need dynamic customer service chatbot Or we need to embed new payment processing gateway immediately.

00:12:02: Right, so they go and buy an off-the-shelf solution from an external vendor And just embed it onto the site usually via an iFrame.

00:12:11: An iframe is essentially Just cutting a hole in your website to show another server's website right?

00:12:15: That's

00:12:16: the perfect way to visualize It!

00:12:18: Because it belongs To Another Server...it Is A Complete Black Box to Your Engineering Team.

00:12:23: You Cannot Inject Your Own CSS or JavaScript To Fix Its underlying Code Due To Basic Cross Origin Security Restrictions.

00:12:30: So you're stuck with Whatever They Built

00:12:32: Exactly!

00:12:33: If that third-party vendor built an inaccessible chatbot and you drop it onto your perfectly accessible website, Your site is now inaccessable.

00:12:42: A keyboard user will tab into the Chatbot and get completely trapped unable to navigate out of it.

00:12:48: So what's the defense mechanism against this?

00:12:50: How do we stop it?

00:12:51: The organization must establish absolute quality gate in procurement.

00:12:56: Before a contract is signed for any external tool It must pass an accessibility audit.

00:13:01: If the vendor cannot prove compliance, you simply do not buy a tool.

00:13:05: Man that requires some serious organizational discipline to tell marketing they can't have their shiny new toy He really

00:13:10: does.

00:13:11: But let's say hold your pipeline and procurement quality gates.

00:13:15: What happens if an internal engineering team just keeps failing automated tests every single day?

00:13:20: Which brings us into the competence gap.

00:13:22: Right.

00:13:22: Setting up a pipeline to catch errors is useless if the people writing code don't understand how to actually pass that test!

00:13:29: Right now, lack of role-specific competence is monumental roadblock in this industry...

00:13:35: Because they just aren't taught it?

00:13:37: Exactly!

00:13:37: Designers are not taught inclusive interaction design at art school and developers aren't teach assistive technologies past the DOM and computer science programs.

00:13:46: But wait….

00:13:47: If an engineer gets a Jira ticket saying bug User profile image violates WCAG one point four point three contrast minimum.

00:13:58: Shouldn't they just be able to look up the documentation and fix it?

00:14:01: I mean, They are professional problem solvers.

00:14:04: if we connect this To The bigger picture of cognitive load We see exactly why that approach fails miserably.

00:14:09: the web content accessibility guidelines or wCag Are incredibly dense highly technical legal frameworks.

00:14:16: they read like a tax manual.

00:14:17: Basically, yeah.

00:14:18: So if you just throw a citation code at a developer You generate immense frustration.

00:14:22: it feels like arbitrary bureaucracy.

00:14:24: to actually change behavior Stakeholders need to understand the mechanism of the failure.

00:14:28: They really need to know why

00:14:30: and the consulting materials offer A brilliant incredibly subtle psychological tweak for writing bug reports And Jira tickets To solve this.

00:14:37: yes It's about shifting The focus from that technical violation to the human effect

00:14:43: Right.

00:14:43: So instead of writing, fix the generic div tags on the checkout button to comply with four.

00:14:49: point one-point two you explain The mechanism of the failure exactly right.

00:14:54: something like because this button is coded as a generic text container rather than interactive element A blind user screen reader just says blank Instead of submit payment and Because they don't know what the but does They are abandoning their shopping cart.

00:15:08: That transforms the ticket entirely.

00:15:10: The developer isn't just satisfying a legal requirement anymore, right?

00:15:14: They are solving a logical user experience problem

00:15:17: Which is what they like doing

00:15:18: Exactly.

00:15:19: Once an engineer understands how a screen reader misinterprets their code... ...the abstract rule suddenly makes perfect mechanical sense!

00:15:26: They learn the underlying principle which means that won't make exact same architectural mistake on next feature.

00:15:32: It bridges empathy gap but translates it into engineering terms.

00:15:37: However There's one final human roadblock.

00:15:41: Even when developers know how to build accessible components and they understand why it matters, the research shows that they still push back... They

00:15:47: do!

00:15:48: ...and

00:15:48: all stems from a massive ego blocker

00:15:51: The creativity myth.

00:15:52: Yes

00:15:53: there is this pervasive idea That accessibility inherently limits design freedom.

00:16:00: literally quote, developers complaining that native accessible HTML components are boring and then accessibility ruins their ability to build customized flashy interfaces.

00:16:11: It's a very common complaint.

00:16:12: now I want to defend the developers for a second here.

00:16:15: if you're building a modern web application Native HTML out of box looks like a document from nineteen.

00:16:20: ninety five

00:16:21: true

00:16:22: Developers use massive front-end frameworks like react libraries or a bootstrap because they allow you to pull pre design highly interactive Gorgeous components and build a slick app in a fraction of the time.

00:16:33: Are we really telling them just abandon their tools?

00:16:35: This raises an important question about what those tools are actually doing.

00:16:38: under the hood The real culprit slowing teams down isn't the accessibility requirement.

00:16:43: It is the blind reliance on those overloaded bloated frameworks.

00:16:47: Okay, how?

00:16:47: so What does the mechanism there?

00:16:49: Let's

00:16:49: take a highly stylized, customized toggle switch from massive third-party library.

00:16:55: Visually it looks amazing!

00:16:57: But under the hood, to make it look that way.

00:17:00: The framework didn't use a native HTML input tag.

00:17:03: It used a cluster of generic div and span tags styled heavily with CSS

00:17:08: And we know from our earlier point That screen readers have absolutely no idea what a generic Div is supposed To do

00:17:14: Exactly!

00:17:14: It has no semantic meaning Doesn't natively accept keyboard focus.

00:17:18: It doesn't inherently trigger when A user hits space bar or enter key.

00:17:22: So its basically just pretty picture Of button.

00:17:24: Yes.

00:17:25: So the developer uses a Sifast component from our framework, realizes it's completely inaccessible and then has to spend hours writing custom JavaScript.

00:17:32: event listeners managing ARRA states an artificially injecting keyboard focus.

00:17:38: just reverse engineer of basic functionality.

00:17:40: that native HTML checkbox does out-of-the box for free.

00:17:43: They build beautiful sports car with no engine and complain its exhausting manually push up hell.

00:17:49: precisely That is a perfect analogy.

00:17:52: The research strongly advocates that relying on clean native HTML five elements, is objectively faster and significantly more sustainable.

00:18:02: you let the browser handle the complex keyboard routing in screen reader announcements natively And You just use CSS to make it look exactly as beautiful and creative As you want.

00:18:10: but the pushback Is always that styling native html from scratch every single time?

00:18:18: And the research counters this with a concept of component libraries.

00:18:21: The compound interest of accessibility.

00:18:24: It is

00:18:24: ultimate solution to efficiency problem.

00:18:27: Large, mature organizations do not build software page by page.

00:18:30: They built a centralized design system Basically library approved digital Lego blocks.

00:18:35: Right.

00:18:36: so senior engineering team takes time building native perfectly accessible highly styled custom drop down menu.

00:18:42: they test it screen readers ensure keyboard navigation flawless.

00:18:45: all hard work exactly once

00:18:47: Just once.

00:18:48: They add it to the centralized component library, and from that day forward any time a developer anywhere in the company needs a drop-down menu they just pull that specific component...

00:18:58: And It just works!

00:18:59: Right?

00:19:00: The effort required to ensure accessibility drops to zero for that developer.

00:19:05: They aren't wrestling with bloated external frameworks that require constant security patching and they aren't reinventing the wheel—it scales infinitely.

00:19:13: So what does this all mean?

00:19:15: we started This Deep Dive exploring what looked like a massive technological failing.

00:19:20: The fact that the digital world is full of broken doors and missing ramps, but the sources we've unpacked reveal a totally different reality.

00:19:28: Yeah...the limitations are rarely in servers or code.

00:19:31: It's entirely human!

00:19:33: I mean it's about overcoming the cognitive blind spot.

00:19:36: Older or disabled demographics aren't using our platforms.

00:19:39: It's about shifting our process.

00:19:40: So we stop trying to bolt security and accessibility on the day before launch And start embedding them directly into this CI CD pipelines.

00:19:47: it's About taking the time to explain The mechanical why behind a Jira ticket rather than just demanding blind compliance To illegal code,

00:19:55: and it's about checking your own egos at the door realizing that true digital craftsmanship lies in writing clean, sustainable native code that works for everyone rather than relying on blooded shortcuts.

00:20:09: So if you're listening whether your are leading a massive engineering division designing the local restaurant menu or just organizing teens internal wiki?

00:20:18: You have to decide of.

00:20:19: inclusion is going be foundation Or Just A Last Minute Code Of Paint.

00:20:22: And it leaves us with one highly provocative thought to mull over, which I think is really important.

00:20:28: Yeah We've established that the technology exists to make the digital world accessible To everyone and that failure to do so Is a symptom of deep organizational inflexibility.

00:20:37: So if a company's internal culture is so rigid?

00:20:40: So stubbornly attached to their assumptions That they continuously lock out millions Of aging in disabled users What other massive world changing market innovations is that exact same inflexibility blinding them to right now?

00:20:51: Wow.

00:20:52: If they can't adapt a build the front doors, what else are they completely missing exactly?

00:20:57: we have the blueprints The materials or there.

00:21:00: it's time We start building the internet for everyone.

00:21:03: Thanks for joining us on this deep dive.