Skip Navigation
KDE @lemmy.kde.social
KDE @floss.social

"HOWTO help a KDE Goal" part 1: "We care about your Input"

"HOWTO help a KDE Goal" part 1: "We care about your Input"

"We care about your Input" plans to increase the number of supported input devices for Plasma and KDE apps. The aim is to offer the possibility to use assistive devices, gaming controllers of all kinds, and devices for specialised tasks.

You can help by funding developers with their research,

https://kde.org/fundraisers/yearend2024/

and by joining the team, giving feedback, and assisting with the development.

https://go.kde.org/matrix/#/#kde-input:kde.org

@kde@lemmy.kde.social

5 comments

  • @kde@floss.social @kde@lemmy.kde.social I seriously doubt this considering how neglected the accessibility situation has been for years now.

    • @Zvez @kde@floss.social @kde@lemmy.kde.social No one neglects accessibility on purpose, it's hard to implement on Wayland because unfortunately that wasn't build for it but the KDE community tries their best and the Gnome community is about to solve the biggest issue on Wayland which will help out all desktops. Accessibility used to be better because conpanies (I think mainly sun) invested millions in the stack for x11 many years ago and once that stopped we got stuck in the state they left it in.

      • To further expand on this, KDE made Accessibility a community-wide goal in 2022, and, although the goal is officially over, the ethos has permeated KDE's culture and devs always have accessibility at the forefront of their minds now.

        But accessibility is hard, especially if, as @gamey@chaos.social points out, the underlying platform is not prepared for it, and breaks all your prior efforts — which we now have to rebuild from scratch.

        That said, as we have problems with such in-demand features such as an on-screen keyboard, and the maliit project (not a KDE project) does not have the same priorities as KDE (they don't seem too interested in supporting Wayland, for example, and we have difficulty with upstream contributions), we are working on taking things into our own hands and are working on our own solutions, again built from scratch.

        In this case, building a brand new on-screen keyboard based on QVK — aka the "Qt Virtual Keyboard". Again, this is a project built from the ground (well, from the foundations of Qt) up, and will consumer a lot of resources. We do think it will be worthwhile, but if anybody feels like contributing and helping out, it would be much appreciated.