It's very convenient to write people who criticize you as "privileged white guys" while ignoring all of the non-white, non-guys that are simply fed up with your bullshit.
Instead of ranting for days and insinuating that multiple open source communities don't care about accessibility - in response to a post where people are trying to build tools and connections to improve accessibility - you could do something productive.
This isn't a "patches welcome" response. But it is an "issues welcome" and a "promotion welcome" response. You have a massive platform. Use that platform to help make a change. You can start by helping people understand what actual issues exist. "$THING is broken" is not actionable feedback. Help break down what's missing from our accessibility stack for the use cases that matter to you or those you know. Then, use your massive platform to direct attention to those issues in a productive way. Call for volunteers, or try to direct funding to people who can work on the accessibility stack. File detailed issues that can help isolate bugs. These are all ways to contribute without writing a single line of code.
Also: why not promote the people who are trying to do better instead of admonishing people for past mistakes? People like [Lukáš Tyrychtr](https://news.itsfoss.com/red-hat-accessibility-gnome/ ) and [Matt Campbell](https://blogs.gnome.org/a11y/2023/10/27/a-new-accessibility-architecture-for-modern-free-desktops/ ) who are working to not just reach feature parity with old systems, but to go beyond by modernizing our accessibility infrastructure?
Chris 🌱 :verified_purple: /
npub1r9…dvwf3
2024-06-22 15:06:35
in reply to nevent1q…dajx
Author Public Key
npub1r9a05yqhjz074sc2fy0c0gjxpvkgtdv06j246v78m65g6wkv8f3sxdvwf3Published at
2024-06-22 15:06:35Event JSON
{
"id": "153557713560fa450f6219066343bb5c4bbd4287124b6277e73ef360f9977fc4",
"pubkey": "197afa1017909feac30a491f87a2460b2c85b58fd4955d33c7dea88d3acc3a63",
"created_at": 1719068795,
"kind": 1,
"tags": [
[
"e",
"aa95e8e57bd761b4d9a438f4b0cafa2029b662d7b6c7f078ac9b55ce90d191e1",
"",
"root"
],
[
"p",
"0bcb4fea58ca0749444278a4850b964fba08d7aee656cb583838bc703bec7759"
],
[
"proxy",
"https://crab.garden/@brainblasted/112660892581080961",
"web"
],
[
"proxy",
"https://crab.garden/users/brainblasted/statuses/112660892581080961",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://crab.garden/users/brainblasted/statuses/112660892581080961",
"pink.momostr"
],
[
"expiration",
"1721662730"
]
],
"content": "It's very convenient to write people who criticize you as \"privileged white guys\" while ignoring all of the non-white, non-guys that are simply fed up with your bullshit.\n\nInstead of ranting for days and insinuating that multiple open source communities don't care about accessibility - in response to a post where people are trying to build tools and connections to improve accessibility - you could do something productive.\n\nThis isn't a \"patches welcome\" response. But it is an \"issues welcome\" and a \"promotion welcome\" response. You have a massive platform. Use that platform to help make a change. You can start by helping people understand what actual issues exist. \"$THING is broken\" is not actionable feedback. Help break down what's missing from our accessibility stack for the use cases that matter to you or those you know. Then, use your massive platform to direct attention to those issues in a productive way. Call for volunteers, or try to direct funding to people who can work on the accessibility stack. File detailed issues that can help isolate bugs. These are all ways to contribute without writing a single line of code.\n\nAlso: why not promote the people who are trying to do better instead of admonishing people for past mistakes? People like [Lukáš Tyrychtr](https://news.itsfoss.com/red-hat-accessibility-gnome/ ) and [Matt Campbell](https://blogs.gnome.org/a11y/2023/10/27/a-new-accessibility-architecture-for-modern-free-desktops/ ) who are working to not just reach feature parity with old systems, but to go beyond by modernizing our accessibility infrastructure?",
"sig": "24571ec086c80b01ddd59186de32b5d01aa347893ff03c4a21e44b88aa48b1ab2efd4fb64d17d4b1731f8dfba589937a2b8c5db010a0f871ad59a94280b94df0"
}