Accessibility Starts Before Code: A Design Imperative

For more than a decade, I’ve worked in accessibility for products and the platform. And if there’s one thing I’ve learned along the way, it’s this: accessibility doesn’t fail because it’s technically complex. It fails because it’s treated as optional, postponed, or misunderstood as a compliance exercise rather than a design responsibility.

When we talk about accessibility in EdTech today, conversations are still dominated by regulations: WCAG, ADA, and Title II deadlines. Those are important, but they’re not the starting point. Accessibility, at its core, is about ensuring that every learner has the same opportunity to engage, participate, and succeed. Laws exist because inclusion was overlooked for far too long.

Accessibility is not something to validate at the end of development. It is a design mindset that should guide decisions from the earliest stages of product conception, long before compliance becomes a concern. When accessibility is embedded early, outcomes improve for all learners.

The Accessibility Problem No One Wants to Admit Is a Design Failure

Products celebrated as “innovative” consistently fail the same way: not through complex technical barriers, but through basic design decisions that exclude users from the start. Poor color contrast, unclear content hierarchy, broken reading order, and inaccessible navigation are not advanced accessibility challenges. They are signals of a deeper problem.

Accessibility is breaking down long before development begins.

When these failures surface, teams often look to engineering for answers. But the root cause is rarely technical. It is a design process built around assumptions; assumptions about how users see, move, process information, and interact with technology.

When accessibility is introduced after design decisions are locked, teams are forced into costly remediation. Timelines slip. Budgets grow. And accessibility becomes framed as friction rather than value.

This is why a shift-left approach is not a best practice. It is a necessity. Embedding accessibility at the earliest stages of design reframes inclusion from a compliance obligation to a product advantage.

When designers intentionally plan for users with visual, motor, cognitive, and auditory disabilities from day one, accessibility issues don’t need to be “fixed.” They simply never occur.

“Shift Left” Isn’t a Buzzword. It’s a Responsibility. Shift Left or Ship Exclusion

Accessibility should never be an afterthought added once a product is “done.” It deserves the same priority as functional QA, performance, and security.

Shifting left means:

1. Designing with accessibility in mind from day one

2. Treating accessibility as a core requirement, not a remediation task

3. Creating content and interfaces that are born accessible, not retrofitted later

When accessibility is embedded this early, inclusion becomes the default. And when inclusion is the default, compliance is not something teams chase; it is something that naturally follows.

Title II Deadlines Expose Years of Accessibility Debt

As we approach upcoming ADA Title II deadlines, especially in the U.S., many institutions are only just beginning to think about accessibility. In my conversations with universities, colleges, and districts, most are still at the initiation stage.

That’s concerning, but it’s also an opportunity.

For institutions wondering where to start, I often recommend three foundational steps:

1. Appoint an Accessibility Owner

Someone internally must be accountable for driving accessibility strategy and outcomes.

2. Partner with Accessibility Experts

Audits, remediation, training, and process standardization require specialized experience.

3. Audit, Assess, and Build a Roadmap

Understand where you stand today, then create a realistic, phased plan forward, while training teams to build everything new with a “born accessible” mindset.

Accessibility is not a one-time initiative designed to meet a deadline. It is an ongoing institutional commitment, and now Title II is making it impossible to ignore.

AI Can Accelerate Accessibility, but It Can’t Replace Accountability

AI has undeniably changed the accessibility landscape. From automated captioning to color-contrast evaluation, audio descriptions, and transcript generation, AI tools are helping teams move faster and scale efforts more efficiently.

But AI also has limitations.

Many AI systems are trained on incomplete datasets that don’t fully represent people with disabilities. If we rely entirely on automation without oversight, we risk reinforcing the very gaps we’re trying to close. That’s why it’s necessary to keep humans in the loop.

AI should accelerate accessibility, not define it. The most effective approach blends AI efficiency with subject-matter expertise and lived experience.

Stop Pricing Accessibility like an Add-On

Accessibility is not an “extra dollar.” It’s not a regulatory burden. And it’s certainly not optional.

There are billions of people worldwide with disabilities. Designing inclusive digital learning experiences ensures that no one is left behind—and that learning truly works for everyone.

If there’s one message I’d leave with EdTech leaders, designers, and institutions, it’s this:
Think of accessibility early. Build it intentionally. And treat it as a strategic advantage rather than a compliance task.

Organizations that do this are not simply meeting standards. They are defining them.