💾 Archived View for bbs.geminispace.org › s › Lagrange-Issues › 52 captured on 2023-11-04 at 14:06:52. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-09-28)
-=-=-=-=-=-=-
“ No speakable content could be found on the screen” is the message I get when I use the screen reader (TTS) with Lagrange.
I use it with every app that contains text and can say that it’s rare to get this message.
Could it be implemented in future?
Regardless, Lagrange is incredible; thank you so much.
🐞 Issue #52 in s/Lagrange-Issues
2023-09-10 · 8 weeks ago
Lagrange has no support for platform-specific accessibility APIs on any platform, unfortunately. This is a drawback of using a simple custom GUI toolkit.
The most feasible plan forward in this area is to create more GUI variants that are built on platform-specific UI toolkits, like UIKit or SwiftUI on iOS, and GTK+/Qt on Linux. This would solve a laundry list of other platform integration quirks as well.
However, a significant amount of work is required for this: first, you need to split the app into a headless core and the UI layer, and then actually write the UIKit/Qt/etc. variants of the UI layer. It would be worth it, though.
As to when this would be done, I have no fixed timelines. Likely after the 2.0 milestone.
That sounds like an awful amount of work. But, good that it’s worth it in other ways too. Thanks again.