<div dir="ltr"><div class="gmail_extra"><div class="gmail_extra">Hi,</div><div class="gmail_extra"><br></div><div class="gmail_extra">I would like to revive this keyboard accessibility discussions started before here [1], more specifically about slowkeys, stickykeys and bouncekeys.</div><div class="gmail_extra"><br></div><div class="gmail_extra">We can choose to add support for those either client side or server side.</div><div class="gmail_extra"><br></div><div class="gmail_extra">The general consensus was it would better be server side (fwiw, I completely agree) with a mechanism for clients such as games to opt-out [2].</div><div class="gmail_extra"><br></div><div class="gmail_extra">Implementation would be in xkbcommon.</div><div class="gmail_extra"><br></div><div class="gmail_extra">So my questions are:</div><div class="gmail_extra"><br></div><div class="gmail_extra"> - Where do we stand with all these, has any work started on xkbcommon implementation? If not, any pointer where to start? (I don't know xkbcommon code much, so any hint might help)</div><div class="gmail_extra"><br></div><div class="gmail_extra"> - Regarding the Wayland protocol side of things, should we come up with a new specific protocol (e.g. a11y-keyboard) or amend existing protocol (wl_keyboard or input-method)?</div><div class="gmail_extra"><br></div><div class="gmail_extra">Cheers,</div><div class="gmail_extra">Olivier</div><div class="gmail_extra"><br></div><div class="gmail_extra">[1] <a href="https://lists.freedesktop.org/archives/wayland-devel/2016-March/027419.html">https://lists.freedesktop.org/archives/wayland-devel/2016-March/027419.html</a></div><div class="gmail_extra">[2] <a href="https://lists.freedesktop.org/archives/wayland-devel/2016-March/027473.html">https://lists.freedesktop.org/archives/wayland-devel/2016-March/027473.html</a></div><div><br></div></div></div>