Here it is. Post 2 in my series on #Linux #accessibility. This time, I'm digitally screaming about the audio stack.
As always, feedback is encouraged and welcomed, and subscribe via rss or email to receive plane-text versions of what I write, the day after publishing at 10 am UTC
fireborn.mataroa.blog/blog/i-w…
#a11y #linuxAudio #linuxAccessibility
This entry was edited (4 days ago)
in reply to Luca Ruggeri

@lcruggeri @danirabbit @talksina pipewire and pulse are userspace daemons that sit on top of whatever you have underlying (alsa/oss/jack), they don't replace it, they're for mixing and control. As for OPs post while I can't say I've run into any of the issues listed (audio's just kinda always worked for me, though part of that is likely just because I'm picky about manufacturer) I do have a solution for the root problem, both pipe and pulse can run in systemwide mode from boot 1/2
in reply to Raptor

@raptor85 @lcruggeri @danirabbit @talksina I maybe should have been clearer. I know pipe wire and pulse are built on top of not instead of alsa. I thought I wrote that in the post but maybe I need to be clearer about it.
I also know that they *can* be started in system mode from boot, but it never comes configured that way, and unless you know how to do it, or find a script to do it for you, it won't be. That was my point. I can configure that, because I know about the feature, and how ot set it up. A new linux user might have no idea. I talked about that a bit more in post 1.
in reply to aaron

@lcruggeri @danirabbit @talksina oh, I'm talking like 10-15 years ago, it was definitely a thing in distros for a while (likely as much from there just not being a well understood standard yet). Seems about right on par, It's a huge issue I have with many distros and desktops (and wayland) myself is that every version seems to strip options in the name of making a more "unified" experience, wayland in particular is a HUGE pain...
in reply to aaron

I’m really looking forward to hearing how we can continue to improve our experience for blind folks 🩷

GitHub Sponsors or LiberaPay are the best ways. Thank you so much!

github.com/sponsors/elementary

liberapay.com/elementary/

in reply to Luca Ruggeri

@lcruggeri Seems like it would be good to encourage and normalize a trend towards sharing about what FOSS we've donated to most recently. Make it a part of FOSS social culture. If we're openly sharing every time we donate it might encourage or remind others.

My most recent donations were to the Linux Mint folks, Thunderbird, Wikipedia. My donations are always small due to my budget but repeated throughout the year as often as I'm able.

#Linux #FOSS

This entry was edited (4 days ago)
in reply to Beardy Star Stuff

@dennyhenke @lcruggeri This would be nice. There is the concern around that though that is people might feel guilted into donating, those who really don't have the income for it. It's true, though, that one person calling out what they donate to can encourage others to do the same. Thank you for raising this idea–some food for thought for sure.
in reply to Luca Ruggeri

@lcruggeri @dennyhenke
How is that supposed to work?
The majority of users don't need accessibility features.
Projects already prioritize features themselves, and apparently accessibility is low on the list for most of them.
So if donations are supposed to make a difference, they need to be tied to accessibility - otherwise 99% of your donation will be used for more widely used features
in reply to aaron

Thanks for this, since I haven't really understood Linux audio since ALSA other than being vaguely aware of Pulse.

I'm thinking about how situations like this happen in "Linux" vs how things in Windows or other (newer) systems feel like they're better, even though just like your article points out, many of the older APIs for sound are still there on Windows as well!

I think I've identified three things, but I'd love your thoughts.

1. There's no centralized body dictating changes

We have FreeDesktop, but there's no one officially saying "This is now deprecated. Stop using it"

2. Linux itself inherited the idea of being compatible with older Unixes and an OS legacy going back to the 70s.

3. Developers aren't given a lot of guidance when knowing what to implement. At best they are just using SDKs from the desktop environment.

With that, how do you see a way forward to improve the situation?

in reply to Serge from Babka

@serge it's software 101 to have to deal with the constraints of software that exists, if the plan is to re-write everything every time somebody decides that there's a new hotness well... that's how you get wayland where the entire ecosystem is broken. the approach of pipewire where they try to maintain backwards compatibility is good, it's just hard to execute on.
in reply to aaron

Huh, somehow this has me feeling optimistic... I guess it sounds like there's a lot of low-hanging fruit. You mentioned not having a audio mixer with good accessibility, which sounds like could be improved with a couple weekends of getting acquainted with the accessibility stack (or I haven't fully comprehended how bad it is yet). I've been meaning to learn how the screen readers and such work, and that seems like a good jumping-off point.

1/3