mastodon.zunda.ninja is one of the many independent Mastodon servers you can use to participate in the fediverse.
Zundon is a single user instance as home of @zundan as well as a test bed for changes of the code.

Administered by:

Server stats:

1
active users

#accessibility

2 posts2 participants0 posts today

For the past week, I've been so angry and disappointed in the Linux community for being quiet in regards to any kind of celebration to advancing accessibility, but suddenly becoming vocal and supportive when privileged people start writing about how bad accessibility on Linux is while portraying contributors as the devils who don't care about anybody.

I'm so exhausted. I'm so demotivated. The Linux community really doesn't care about accessibility on Linux. No wonder accessibility on Linux sucks. No one wants to work on it because they keep getting bullied and pressured.

tesk.page/2025/06/18/its-true-

TheEvilSkeleton · It’s True, “We” Don’t Care About Accessibility on LinuxWhat do virtue-signalers and privileged people without disabilities sharing content about accessibility on Linux being trash have in common? They don’t actually really care about the group they’re defending; they just exploit these victims’ unfortunate situation to fuel hate against groups and projects actually trying to make the world a better place. I never thought I’d be this upset to a point I’d be writing an article about something this sensitive with a clickbait-y title. It’s simultaneously demotivating, unproductive, and infuriating. I’m here writing this post fully knowing that I could have been working on accessibility in GNOME, but really, I’m so tired of having my mood ruined because of privileged people spending at most 5 minutes to write erroneous posts and then pretending to be oblivious when confronted while it takes us 5 months of unpaid work to get a quarter of recognition, let alone acknowledgment, without accounting for the time “wasted” addressing these accusations.

During the @w3c meeting in April 2025, Shadi Abou-Zhara discussed the relationship between #accessibility standards and regulations, particularly focusing on W3C's Web Content Accessibility Guidelines (#WCAG).

He urged recognizing policymakers as key stakeholders and called for a more granular approach in standards to better guide regulations and reflect the needs of people with #disabilities.

🎬 Watch "Accessibility and regulations": youtu.be/M7-u2UUR-wI

I'm RealZero or "Bryan Greyson".

I'm a self-declared-nerd, #Furry, kinda-Brony, antifascist, socialist(?), leftist vegan working in IT. (are those all checkmarks I need for here?^^)

I'm a big fan of cartoons, animated movies, #videogames and also some #boardgames.

I highly value all my cartoon crushes. ❤️

I'm relationship-anarchist and atheist. (or better: ignostic)

I mostly listen to metal, rock and punk stuff, and in general everything socio-critical and anti-capitalistic.

Supporter of body-positivity, #environmentalism, #sustainability, #accessibility, #OpenSource / #FOSS.

Bite greedy corporations, bite fascists, bite everyone that abuses human and non-human animals.

Warning: talks about nudity, kink and (cartoon) porn (behind warnings)

Profiles, etc.: realzero.carrd.co/

Zero's GroundZero's GroundZero's Ground

I think first step of making websites accessible is to care about accessibility. If you're working with Web, I strongly encourage you to read through these user stories about "How People with Disabilities Use the Web" published on W3C website. I guarantee you your mindset will be different after reading these user stories.

w3.org/WAI/people-use-web/user

Web Accessibility Initiative (WAI)Stories of Web UsersBy W3C Web Accessibility Initiative (WAI)

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

fedify.devFedifyFedify is a TypeScript library for building federated server apps powered by ActivityPub and other standards, so-called fediverse.

Ever wanted to style HTML form controls with custom CSS? A new @w3c #CSS specification is underway: "CSS Form Control Styling Level 1" #FPWD #timetogiveinput
▶️ w3.org/TR/css-forms-1/

This spec. aims to standardize form styling, improving design consistency and #accessibility while giving web #designers more control.
Feedback welcome! github.com/w3c/csswg-drafts/la

Need a demo? Check this one by @argyleink! nerdy.dev/customize-a-select

#Blind users, users that rely heavily on #keyboardNavigation or anyone else with a preference on that matter (please indicate what applies in the comments):

Do you have a preference for or comments on the format of URLs? During user research, we have learned that URLs that are easy to handle are a good thing.

We are currently considering to introduce URLs that do not need more reserved usernames in #Forgejo, such as codeberg.org/-/something/ or codeberg.org/_something/.

Replied in thread

Imagine your local government sends this:

𝑇𝑠𝑢𝑛𝑎𝑚𝑖 𝑤𝑎𝑟𝑛𝑖𝑛𝑔: 𝗠𝗼𝘃𝗲 𝘁𝗼 𝗵𝗶𝗴𝗵𝗲𝗿 𝗴𝗿𝗼𝘂𝗻𝗱 𝗶𝗺𝗺𝗲𝗱𝗶𝗮𝘁𝗲𝗹𝘆. Updates to come in the next hour. Stay calm.

Now imagine the impact on screen reader users.

End of thread.