Scott Lacey Swam 8.2 Miles Blind. The World Still Builds Walls.

For a sighted swimmer, the 8.2-mile perimeter of Mackinac Island is a navigation challenge — read the water, track the shoreline, adjust for current. For Scott Lacey, who lost his vision suddenly in 2009 when a failing shunt crushed his optic nerves, that same route required a specialized tether system, a carefully coordinated support team, and more than nine hours in open water. Same island. Same distance. Profoundly different infrastructure required to make it possible.

On August 9, 2026, Lacey became the first known visually impaired athlete to swim around Mackinac Island. He completed the Boston Marathon before that. Ironman triathlons too. But this particular achievement — and what he said afterward — cuts to something the accessibility field keeps circling without landing: the problem isn't disabled people's capacity. It's the world's failure to provide the right conditions.

The Expectation Shift: From "Can't" to "Can, With the Right Conditions"

"I'd like people to move in a direction where the expectation isn't that a person with a disability can't do it," Lacey told Disability Scoop. "The expectation is they can do it. They just might do it a little differently."

He's careful about the word "inspiration." Deliberately so. Lacey, 43, a Kalamazoo athlete who grew up playing varsity soccer and tennis at Holland West Ottawa, doesn't want his story filed under the category of disabled person overcomes odds for the benefit of nondisabled observers. He wants something harder: a structural shift in what we assume people with disabilities can and cannot do.

That's not a feel-good distinction. It has direct operational consequences for every organization that serves the public.

When the baseline assumption is can't, organizations build systems that exclude — and then retrofit accessibility as an afterthought, if at all. When the baseline assumption is can, with the right conditions, design changes. Forms get labeled. Counters get lowered. Tether systems get built. The difference between those two postures is exactly what Title III of the ADA (opens in new window) was written to enforce — the obligation to provide equal access, not charity.

What "Doing It Differently" Actually Requires

Lacey's swim required months of training at Bronson Athletic Club in Kalamazoo, building from half-hour intervals to five-hour sessions. It required a specialized tether system connecting him to a guide. It required Mackinac swim director Jon Vos — someone with a neighborhood connection to Lacey going back decades — to help coordinate the support structure.

Notice what that list contains: time, planning, relationships, and custom infrastructure. Not miracles. Not superhuman capacity. Logistics.

This is exactly the conversation accessibility practitioners need to be having with organizational leadership. The barrier to equal participation is almost never ability. It's almost always infrastructure — and infrastructure is buildable. The ADA's reasonable modification standard (opens in new window) exists precisely because Congress understood that "doing it differently" is legitimate, and that organizations have an obligation to make those modifications possible.

Once again, we see the same pattern: a disabled person invests enormous personal resources to compensate for gaps in public infrastructure, then gets celebrated for it, while the infrastructure question goes unexamined. Lacey himself seems aware of this dynamic. He wants the story to shift expectations, not generate applause.

Infrastructure Gaps Are Systemic, Not Individual

Lacey's biography is extreme by any measure — hydrocephalus at birth, a shunt implanted at age one, vision loss at 34 from a shunt failure, more than 20 subsequent brain surgeries, infections, hospital stays lasting up to six weeks. He also lost both parents at age 4 and his childhood home to fire. The adversity is staggering.

And yet his message is not about adversity. It's about possibility — specifically, the conditions that make possibility real.

"People with disabilities can do anything anybody else can do if they're provided the right opportunity," Lacey said. "We may do it slightly differently, but it doesn't mean a person can't do it."

That phrase — provided the right opportunity — is load-bearing. It places responsibility on systems, not individuals. For accessibility practitioners, it maps directly to the ADA's core mandate (opens in new window) and the WCAG 2.1 framework's (opens in new window) underlying principle: that barriers are design failures, not user failures.

This is also where the compliance conversation often breaks down. Organizations audit for technical violations. They fix the obvious items. But the structural assumption — that disabled users are edge cases, exceptions, or inspiration stories rather than regular participants — stays embedded in how products and services get built. That assumption is what Lacey is pushing against.

Two Compliance Gaps That Mirror Lacey's Point

The accessibility field has its own version of the "expectation problem." Two gaps in particular deserve attention here.

The language access gap. A website can pass WCAG 2.1 Level AA (opens in new window) and still exclude a significant portion of the community it serves — specifically, users who speak languages other than English. Title VI of the Civil Rights Act (opens in new window) requires language access for federally funded programs, but compliance teams rarely audit for both mandates together. The result: organizations invest heavily in screen reader compatibility while leaving form validation messages, ARIA labels, modal dialogs, and dynamically loaded content entirely untranslated. idioma.chat (opens in new window) addresses exactly this gap — it translates not just visible text but the full accessibility layer, including ARIA attributes, alt text, and dynamic content that traditional translation services miss entirely. A government site that passes WCAG AA but only functions in English has not actually provided equal access to the communities it serves. These two compliance mandates belong in the same audit, not separate silos.

The expectation gap in testing. Automated accessibility testing tools detect at most 37% of actual barriers, according to research we've published here. The other 63% requires human judgment — specifically, the judgment of people who use assistive technology in real conditions. When organizations rely exclusively on automated scans, they're building a compliance posture on the assumption that the tools see everything. They don't. The assumption that automation is sufficient mirrors the assumption that Lacey couldn't swim around Mackinac Island — both fail because they substitute a default for actual evidence.

What Lacey's Mantra Demands of Organizations

"Impossible doesn't exist," Lacey says. That's a personal mantra forged through extraordinary circumstances. But it has a structural corollary for organizations: inaccessible isn't inevitable.

The barriers that exclude blind swimmers, screen reader users, non-English speakers, and wheelchair users from full participation weren't handed down from nature. They were built. They can be rebuilt. The ADA's reasonable modification framework (opens in new window) and Section 508's technical requirements (opens in new window) exist because Congress agreed.

Organizations that are serious about this work — not just about avoiding litigation, but about actually providing equal access — should be asking Lacey's question: How can this be possible? Not is it required? Not what's the minimum? But: what does it take to make this work for the people we're supposed to serve?

As our analysis of compliance framework paralysis shows, organizations often get stuck navigating overlapping standards rather than asking the simpler, harder question: are the people we serve actually able to participate?

Lacey built a tether system. He trained for months. He found a swim director who knew the water. He did what it took.

The question for every organization with a website, a service counter, a parking lot, or a public program is simpler than an 8.2-mile open-water swim: what's your tether system? What infrastructure have you built so that people who do things differently can actually get there?

Compliance Area	Governing Standard	Common Gap	What to Inspect
Screen reader access	WCAG 2.1 SC 4.1.2 (opens in new window)	Unlabeled form fields, missing ARIA roles	Run real screen reader test (NVDA/JAWS), not just automated scan
Language access (disability layer)	Title VI + WCAG 2.1	ARIA labels and dynamic content untranslated	Audit translated pages for ARIA attribute translation, not just visible text
Dynamic content	WCAG 2.1 SC 4.1.3 (opens in new window)	Status messages, modals, form validation not announced	Test with assistive technology during actual user flows
Emergency notifications	ADA Title II / 28 CFR Part 35 (opens in new window)	Alerts not reaching users with disabilities in accessible format	Audit notification systems for deaf/hard-of-hearing and blind users separately
Physical access baseline	ADA Standards for Accessible Design (opens in new window)	Entrance, bathroom, parking, counter barriers	Physical inspection against 2010 ADA Standards