Different people have different accessibility needs; it is impossible to make a single theme that everyone can use

Some accessibility needs are incompatible with others, so having only one or even two "accessibility" modes can't cut it (e.g. dark + high-contrast theme)

The "accessibility" themes are the least tested and most buggy ones; so preventing users from adding themes means we're stuck with the bugs

Anyway, that's why when people say this kind of bullshit: https://stopthemingmy.app/

What I hear is "If you don't have perfect eyesight or the normal kinds of vision problems, we want you to be excluded"

@lunarequest I've found them to be very hostile to it

Issues regarding accessibility on their issue tracker marked as wontfix within minutes

@researchfairy there's a reason why I made this post with vulpine labs https://furry.engineer/@vulpinelabs/115205683158621396

@disaster2life@pleroma.debian.social @Kuniti_shino@pounced-on.me @researchfairy@scholar.social imo it's not bad because it's custom theming, rather it's just not advertising it's unsupported (or, in better terms, who is providing support for what).

i think anyone making an accessibility-focused distro should recognize that part of their UX is being provided by their customization (and would in turn be responsible for giving users support for it) whereas ubuntu users are being shown an unsupported theme and being sent to the app's devs when anything unexpected happens.