How and why to stay in Touch with the Disability Community as Accessibility Consultant

As an accessibility consultant, it's not just about staying informed about technical developments. Exchange with the disabled community is also important, or at least it should be. Thw why and how is the topic of this article.

The accessibility community is not the disability community

The accessibility community and the disability community must be distinguished from one another, as the first group primarily consists of people who are professionally, politically or socially committed to the implementation of accessibility, while the second group includes people who are affected by disabilities and should benefit from these measures.

There are certainly overlaps between the two groups. But it is difficult when able-bodied A11Y consultants start to speak for disabled people. Personally, I am rather critical of the allyship concept, at least as many A11y consultants are Living it. A paternalistic attitude is very common.

PThe communities do not always agree when it comes to digital accessibility or specific requirements. That does not mean that the disabled person is always right in their assessment. As is often the case in life, it is more complicated than that.

Understanding needs and perspectives

The community of disabled people knows best what challenges and needs really exist in the digital space. Through direct exchange, solutions can be developed that not only sound good in theory, but also work in everyday life. This makes it clear how diverse the needs are - whether physical, sensory or cognitive impairments. The exchange helps to better understand these differences and to create offers that really suit everyone.

To really implement digital accessibility, you need a design that is based on the real user experiences of the people it affects. If you talk to those affected right from the start, weak points in the design can be identified early on and avoided. At the same time, the community plays an important role when it comes to testing solutions. Their feedback on designs and prototypes can ensure that the results are actually barrier-free and usable for everyone.

Empowerment and collaboration

Joint commitment brings developers and users closer together. When those affected are actively involved and realize that their voices are really being heard, the willingness to contribute their experiences and knowledge increases. Through co-creation, disabled people can work directly on development and contribute their valuable ideas. This creates solutions that really work and better take everyone's needs into account.

Raising awareness

Direct contact with those affected helps to develop a better understanding of barriers that are often not visible at first glance. Without this exchange, there is a risk that obstacles or needs will only be judged from one's own perspective. This can quickly lead to solutions being developed that do not really fit or even have an unintentionally discriminatory effect.

Improving legal and ethical standards

Guidelines such as the WCAG (Web Content Accessibility Guidelines) or the European Accessibility Act (EAA) often seem quite abstract. The community can help to make these standards more tangible and more practical. At the same time, accessibility is not just about regulations - it is also a question of ethical responsibility, because in the end the idea of participation and justice is at the heart of it.

The community offers a valuable opportunity to expand one's own expertise by providing access to networks, resources and best practices that would otherwise be difficult to find. Regular exchange also ensures that one always stays up to date with developments and needs.6.

How to exchange ideas

The easiest way is certainly social media: platforms such as BlueSky, Reddit, Facebook or specialized forums offer the opportunity to join online communities and enter into direct dialogue with activists and other members of the community.

If you don't want to participate so actively, you can find blogs, YouTube channels and other ways to at least keep yourself informed.

There is also the option of taking part in events, especially in larger cities:

Community events: Take part in events organized by or for disabled people (e.g. inclusion days, protests or cultural events).
Hackathons or design jams: Some initiatives organize collaborative events where barrier-free solutions are developed together.

Enable participation

There is also the option of actively involving disabled people in the process.

Conduct interviews with those affected.
User research with the community: Invite people with disabilities to take part in usability tests or focus groups. Reward their time and input appropriately.
Promote co-creation: Work together with affected people on the development and design of digital products.

How should a non-disabled person get involved

Many non-disabled people are afraid to get involved wih disabled because they are afraid of making mistakes. Here are a few tips:

Choose language carefully: Use respectful and inclusive language that emphasizes people's dignity.
Don't make assumptions: Avoid speaking for the community or generalizing their needs.
Be open: Be prepared to accept criticism and learn from it.
Respect roles: The community should be seen as an expert in its own field. Don't work "for" them, but "with" them.
Express appreciation: Recognize the expertise and contribution of disabled people in projects and processes.

Maintain a critical balance

It's about building relationships on an equal footing, listening and creating a space in which disabled people are actively involved. Engaging with the community should be long-term and sustainable - not just as a one-off action, but as a continuous exchange characterized by mutual respect.

As I wrote elsewhere, it's not about every statement made by a disabled person being right. It's true that all perspectives must be respected. In practice, however, it's not possible to fulfill all wishes. Digital accessibility has certain requirements and best practices. It becomes difficult when it goes beyond that or when it comes to individual preferences.

This is because the requirements of one group - for example the visually impaired - can contradict each other. This also applies to requirements from two different groups such as the visually impaired and the neurodiverse. What is interesting in this context is that the only viable solution in this area, namely personalized adaptations as proposed by Jakob Nielsen , was rejected by large parts of the accessibility community. Of course, without having any useful ideas on how to solve the problem differently. I would say that a large part of the disabled community would see it differently if you asked them. But they don't. Because they believe that they have all the answers in the WCAG.