[Accessibility] Accessibility features in Wayland - feedback request

Samuel Thibault samuel.thibault at ens-lyon.org
Mon Feb 11 00:57:16 UTC 2019


Peter Hutterer, le lun. 11 févr. 2019 10:39:27 +1000, a ecrit:
> On Sat, Feb 09, 2019 at 12:05:06PM +0100, Samuel Thibault wrote:
> >   Another instance is using a given touchpad as a positioning device,
> >   which requires consuming all input events from it, and getting
> >   absolute coordinates.
> 
> can you expand on this bit please? 

In the Hypra company (hypra.fr) we are working on a project of using
just a couple of braille cells to be read by one hand, and to use the
other hand to point with a touchpad which part of the screen should be
shown on the cells. To be able to find one's way, that positioning needs
to be absolute, just like with tablets (but much more widely available
than a tablet). Put another way, moving the finger at the top left
corner of the touchpad would make the cells show the first menu of the
window, which is at the top left part of the screen.

> > - synthesize input events.
> > 
> >   As mentioned above for Orca, but also for various kinds of Assistive
> >   Technologies which provide alternative ways of typing on the keyboard,
> >   of moving the mouse etc.
> > 
> > Implementing these kinds of features within libinput itself could make
> > sense, but in practice I don't think people will manage to do it (I
> > guess libinput is C only? Most AT tools nowadays are pythonic), while an
> > interface to steal/inject events would allow to development them on the
> > side.
> 
> libinput is written in C, correct. However, the primary reason for libinput
> is as a hw abstraction for compositors and in Wayland the compositor has
> full control over input events. So any injection interface is IMO better
> implemented as some standardised DBus interface that the compositor exposes.
> this gives the compositor control over the interfaces allowed (and the
> context), etc. Much better than trying to figure out a back channel through
> libinput.

But then it'd need to be implemented by all compositors, right?

Samuel


More information about the accessibility mailing list