Home Misokinesia The Neglect of Accessibility in Tech: When Developers Are Dismissive and Rude

The Neglect of Accessibility in Tech: When Developers Are Dismissive and Rude

by Shaylynn Hayes-Raymond
A focused female software engineer coding on dual monitors in a modern office.

In an age where technology touches nearly every aspect of our lives, the issue of accessibility has never been more important. Yet, despite ongoing advocacy and growing awareness, many tech companies and developers continue to demonstrate a disturbing lack of concern for users with disabilities. Often, rather than addressing accessibility concerns with respect or a sense of urgency, these companies are rude, dismissive, and fail to understand that disabilities aren’t “preferences” to be disregarded.

As someone who works in a field that strives for inclusivity, I’ve encountered far too many situations where companies refuse to acknowledge or take seriously the needs of users with sensory disorders, mobility challenges, or other disabilities. My frustration isn’t just with poorly designed products—it’s with the dismissive attitudes of the developers themselves.

The All-Too-Common Dismissal of Accessibility Requests

When users with disabilities ask for features that would make their experience more comfortable, the responses are often shocking. Instead of working toward solutions, developers typically tell users to “just use something else” or “submit a feature request.” This shows a lack of empathy and understanding for the challenges faced by those with disabilities. The notion that accessibility is a “preference” undermines the very real, life-altering impacts that inaccessible design can have on users.

Two major companies come to mind when thinking about this behavior: Nintendo and Discord.

Nintendo: Accessibility “Doesn’t Matter”

Nintendo has long been celebrated for its innovative games, but when it comes to accessibility, the company’s approach has been less than accommodating. I’ve had personal experiences trying to engage with their products, only to find that critical features—like adjustable color contrasts, control remapping, or visual cues—are sorely lacking in many of their most popular titles.

When users reach out to Nintendo with accessibility requests, they’re often met with the same response: “Submit a feature request.” This response implies that accessibility is optional—something that can be requested, but not necessarily prioritized. It’s as if Nintendo’s team believes that those with disabilities should either adapt to their products or simply go without. In an industry that has embraced inclusive design in so many other areas, Nintendo’s reluctance to address accessibility is particularly frustrating.

Discord: “We’re Not Making That a Priority”

Discord, a widely used communication app, has also been a point of contention for many users with disabilities. The platform’s design and functionality don’t always account for sensory sensitivities, mobility challenges, or visual impairments. In fact, when users reach out to the Discord team for help with accessibility, the response is often far from helpful.

Rather than providing real solutions or even offering to look into the issue, users are typically told to “submit a feature request.” This form of dismissiveness is especially concerning when it comes from a company that prides itself on creating an inclusive space for users to communicate and interact. When accessibility is treated as a low priority, or when users are essentially told that their needs aren’t important enough to address, it sends a message that people with disabilities are not welcome.

The Rude Reality: Accessibility Is Not a “Nice-to-Have”

The problem isn’t just with the lack of features or thoughtfulness in design—it’s the refusal to acknowledge that disabilities are real and affect millions of people. Accessibility is not a “preference” like a color scheme or a fun feature; it’s a necessity. For many, it is the difference between using a product or not. Telling someone to simply “use something else” is not only inconsiderate—it’s exclusionary.

When developers respond with indifference or outright rudeness, they are sending a message that the needs of people with disabilities don’t matter. They are dismissing the reality that accessible design is not about luxury—it’s about ensuring that everyone has the same access to digital spaces and tools.

The Consequences of Ignoring Accessibility

When companies like Nintendo, Discord, and others fail to prioritize accessibility, they are actively excluding people from engaging with their platforms. This lack of inclusion leads to:

  • Frustration and Isolation: Users with disabilities are left feeling ignored and alienated.
  • Barriers to Participation: Individuals may feel that their only option is to avoid certain platforms altogether, limiting their access to entertainment, communication, or even work opportunities.
  • Lost Business: By not prioritizing accessibility, companies alienate a huge and growing segment of the market. The disability community represents billions of dollars in untapped potential, and ignoring them is a business misstep.

Moving Toward Inclusive Design: A Call for Change

As consumers and users, we have the power to demand better. We must continue to advocate for accessibility in all aspects of digital design, not as a “feature request,” but as a fundamental right. Companies that care about their users and their bottom line should prioritize accessibility as a core principle of their development process—not as an afterthought.

Developers and programmers need to understand that accessibility isn’t just about meeting legal requirements or ticking a box on a checklist. It’s about treating every user with dignity and respect, ensuring that technology is available to everyone, regardless of their abilities.

It’s time for companies like Nintendo, Discord, and others to take real action, to stop making excuses, and to understand that accessibility is not a “nice-to-have” feature—it’s a necessity. Until then, the tech industry will continue to alienate a significant portion of the population, creating unnecessary barriers for millions of users. The onus is on us to keep pushing for change, demanding better, and holding developers accountable for their actions—or inactions.

Skip to content