Author: Ted Drake

  • Community Builds the Conditions for Accessibility

    Community Builds the Conditions for Accessibility

    At the Zero Project Conference in Vienna, one pattern kept repeating across very different sessions: lasting accessibility change rarely starts with a policy alone, a checklist alone, or a single expert. It grows when communities build shared knowledge, shared responsibility, and practical systems that other people can use. That is what makes the work stick.

    Lived experience becomes shared capability

    Sinéad Burke’s keynote framed this clearly. The challenge is not just to include disabled people as end users. It is to recognize lived experience as expertise and leadership. When that happens, accessibility stops being something reviewed at the end and becomes something shaped earlier, with better judgment and better priorities.

    That same idea showed up throughout the week. The strongest examples were not centered on one hero or one institution. They created ways for knowledge to move outward, so more people could make better decisions in their own settings.

    The best models spread because they are usable

    A strong example came from the Geodetic Institute of Slovenia. Their project on multimodal mobility used disability-led design to create tactile maps and detailed access information, then backed it with local workshops. What stood out was not just the quality of the work. It was that the model was standardized and simple enough to transfer to other places. That is how good accessibility practice grows.

    The NextGen Accessibility Initiative showed something similar in a different context. By working with Gen Z organizations inside existing frameworks, it helped 200,000 students get accommodations, support, and education. That is an example of building inside the flow of real systems instead of creating a side effort that never reaches scale.

    Community leadership keeps the work from staying symbolic

    One of the most useful discussions looked at disability awards and recognition lists. The takeaway was not that visibility is unhelpful. It was that visibility is only the start. Irene Mbari-Kirika noted that once the list is published, the harder question begins: who is building the support structure that helps ideas turn into durable change?

    That is where community-based organizations often lead. InABLE, for example, was highlighted for building knowledge and support systems for entrepreneurs in Africa. That is deeper than awareness. It is the kind of work that helps capability take root, especially in places where formal systems are not doing enough yet.

    Trust matters most when the stakes are high

    The crisis response sessions made this even clearer. In emergencies, accessible support cannot depend on last-minute improvisation. It depends on preparation, coordination, training, and trusted relationships long before something goes wrong.

    Projects like Purple Vest and GADRA showed why community-led work matters here. Purple Vest focuses on accessible evacuation and support for disabled people and older adults. GADRA made the larger structural point: only 1% of disaster relief funding goes to disability-led organizations. That gap explains a lot. When communities are excluded from leadership, support is often designed around assumptions instead of lived reality.

    The disaster database work in rural Vietnam was another strong example. The Hanoi Association of People with Disabilities helped develop a system that mapped households, gathered detailed infrastructure data, and trained government officials. Then that work was integrated into the national disaster monitoring system. This is what it looks like when community knowledge becomes operational infrastructure.

    Inclusion grows when it is built into everyday places

    The same pattern appeared in public space, culture, and daily life. The National Library of Singapore showed how physical access, defined routes, wider aisles, and support programs can be designed as part of the experience from the start. This is more than removing obstacles. It is creating environments people can actually use with confidence.

    The session on Europe Beyond Access made a similar point in the arts. The network has created career opportunities for disabled and Deaf artists across 11 cultural institutions and produced toolkits for inclusive events. This is not just about welcoming people into existing spaces. It is about changing the conditions so participation can continue and grow.

    What I took from it

    The clearest lesson from these sessions is that accessibility becomes stronger when it is distributed. Community-based organizations often lead because they stay close to lived experience, build trust over time, and create methods that other people can adopt. They do not just advocate for change. They create the conditions that allow change to travel.

    That is the kind of progress worth paying attention to. It is practical, repeatable, and built to last.

  • How Accessibility Actually Sticks

    How Accessibility Actually Sticks

    The Problem Isn’t Motivation. It’s Memory.

    Most accessibility work starts the same way. Someone asks a question. Someone knowledgeable answers it. The team moves on.

    That exchange feels productive. It is productive. But it has a hidden cost.

    If the answer only lives in a meeting, a Slack thread, or someone’s head, it disappears the moment priorities shift, people rotate, or the next new hire joins the team. Then the same question comes back. And back again. And eventually, people stop asking.

    This is how accessibility quietly erodes—not because people stopped caring, but because the organization never learned.

    When Knowledge Stays Personal, Progress Stalls

    I’ve seen teams with strong accessibility instincts still struggle because everything depended on informal help. Reviews caught issues late. Decisions were explained verbally but never recorded. Good intent was everywhere, but confidence was fragile.

    You can spot this pattern easily:

    • The same questions come up every quarter

    • Accessibility advice changes depending on who you ask

    • New team members hesitate because “I don’t want to get it wrong”

    That hesitation matters. When accessibility knowledge feels personal or fragile, people wait for permission instead of acting.

    Writing Things Down Is a Leadership Move

    Documentation gets a bad reputation because people imagine heavy process and stale guidelines. That’s not what makes accessibility stick.

    What works is much simpler.

    Write down why a decision was made. Capture what “good enough” looks like today. Share the tradeoffs you accepted so the next team doesn’t repeat the same debate.

    This kind of documentation does three important things:

    1. It makes decisions reusable

    2. It lowers the cost of participation

    3. It shifts accessibility from private expertise to shared context

    That shift is the difference between a team that depends on experts and one that can move independently.

    What This Looks Like in Practice

    This is not about creating perfect artifacts. It’s about leaving breadcrumbs.

    Some examples I’ve seen work:

    • A short design note explaining why a color contrast exception was approved

    • A checklist used during planning, not just at review time

    • A shared definition of “keyboard complete” that everyone agrees on

    None of these are impressive on their own. Together, they create continuity.

    Action You Can Take This Month

    If you want to make accessibility stick where you work, start small and concrete:

    • The next time you answer a question twice, write it down

    • Turn one recurring accessibility comment into a checklist item

    • Capture one decision and share it with the team that wasn’t in the room

    Do not wait for a documentation sprint. Do not aim for completeness. Aim for usefulness.

    This Is About Care, Not Control

    Repeating yourself is exhausting. Holding knowledge in your head is risky. Documentation is not bureaucracy—it’s a way of caring for the people doing the work now and the people who will join later.

    Accessibility lasts when it stops relying on memory and starts relying on shared understanding. That doesn’t happen all at once. It happens through small decisions made consistently.

    That’s how the work survives you. And that’s how it actually sticks.

    — This article was written with AI asssistance