I mean, I can see that it is kind of hard to program your own accessibility tools esp. when you’re disabled. But in this case it literally is “Pay money to be spied upon by a ruthless company in bed with the Trump administration” vs. “use this free software that is not spying on you”
I mean if you rely on accessibility apis you’re not going to use it because it’s not there… You literally cannot use the OS because you require accessibility tools to use your computer effectively.
And implying that someone should just make it their own is kind of asinine. This is a big shift in the Linux Desktop ecosystem that one person cannot affect when decisions have already been made and contributions that go against project decisions are not necessarily welcome.
Developers of large accessibility projects slowly dropping Linux support because of Wayland Is a Wayland problem, not a “devs of accessibility tools problem”.
They are already vocal about it, to frustratingly no effect.
I mean, I can see that it is kind of hard to program your own accessibility tools esp. when you’re disabled. But in this case it literally is “Pay money to be spied upon by a ruthless company in bed with the Trump administration” vs. “use this free software that is not spying on you”
(and accessibility on linux is not that bad)
I mean if you rely on accessibility apis you’re not going to use it because it’s not there… You literally cannot use the OS because you require accessibility tools to use your computer effectively.
And implying that someone should just make it their own is kind of asinine. This is a big shift in the Linux Desktop ecosystem that one person cannot affect when decisions have already been made and contributions that go against project decisions are not necessarily welcome.
Developers of large accessibility projects slowly dropping Linux support because of Wayland Is a Wayland problem, not a “devs of accessibility tools problem”.
They are already vocal about it, to frustratingly no effect.