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.