Hello Wayland developers, I wanted to share my perspective as a Linux user with motor disabilities regarding Wayland's architecture and its implications for accessibility.
PERSONAL BACKGROUND: I navigate computers using a Quha Zono 2 (gyroscopic air mouse) for cursor movement, dwell clicking software that detects when I pause my cursor, and an on-screen keyboard for text input. This combination is essential for me to use computers without traditional mouse buttons or physical keyboard. Growing up, I couldn't use Linux because the adaptive equipment and accessibility software I needed only supported Windows. As someone with motor disabilities, this was a significant barrier to Linux adoption. In college, I was finally introduced to Linux and became enthusiastic about its potential. However, I was disappointed to discover the gaps in Linux accessibility compared to commercial operating systems. ACCESSIBILITY CONCERNS: As Wayland becomes the default display server for major distributions, I've grown concerned about its implications for users with disabilities. From my research and experience, Wayland's security model appears to limit the functionality needed by many accessibility tools. Under X11, accessibility software can monitor input and inject events system-wide, which is essential for tools that need to work across applications. Wayland's stricter security boundaries seem to make this type of functionality much more difficult to implement. I'm worried that without proper consideration for accessibility needs within Wayland's architecture, Linux may become less accessible to users with disabilities rather than more. This would be a step backward for inclusivity in open source. I'd appreciate any insights about how Wayland plans to address accessibility requirements for users who need assistive technologies that work across application boundaries. Thank you for your consideration, Nick
