3 ms·
Please prioritize to keep accessibility features working. This is really the main issue with wayland. Yes, it might be more stable these days and work fine for
by cardanome 10mo ago
Please prioritize to keep accessibility features working.
This is really the main issue with wayland. Yes, it might be more stable these days and work fine for you. We can talk how how it makes writing you own WM needlessly complicated and all that but the one thing that makes wayland unacceptable is its lacking accessibility story. After so many years.
Accessibility is not something you can worry about adding later. It is the first thing you should think about when designing new software.
- hambes 10mo agoAs someone who is not deep into linux desktop history: Can you please elaborate on the missing accessibility features in wayland or direct me to resources on that? I've been using wayland for a while now and am very happy with it, but my accessibility needs are pretty basic.
- cardanome 10mo agoSee this comment for example: https://news.ycombinator.com/item?id=46380075#46381858 https://news.ycombinator.com/item?id=46380075#46381858 Here is a slightly-hopeful article: https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-4-wayland-is-growing-up-and-now-we-dont-have-a-choice/ https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-d...
- hambes 10mo agothank you!
- bigyabai 10mo ago> Accessibility is not something you can worry about adding later. I don't think there's any concrete proof of this. Ideally I think people want accessibility handled by their WM/DE; you're not getting Windows or macOS-quality a11y "for free" unless your desktop embraces it. At which point you might as well make it a separate, aftermarket protocol and slap it into d-bus. If the Linux ecosystem is going to be fragmented and move past single-point-of-failure, polishing Xorg's accessibility works against the goal of standardized a11y.
- gsnedders 10mo agoNot just WM/DE, but also the toolkit too.