News

As we announced recently, we decided that we’d learned enough from the Odilia prototype to actually implement the real thing. The prototype code, while functional, prioritised experimentation over quality, and thus we’ll be throwing almost all of it out completely, but the code is far less important than the experience we gained from writing it.

As of afew days ago, we decided we played enough with the tools and components of the linux accessibility stack to be able to say that we aren’t so ignorant anymore, we know at least the basics about how it all fits together, how our screenreaders read information from a linux gui app, how the gui toolkit and atspi work together to provide the required context for such tools to operate.

Since I don’t want to bore you with code snippets, git logs, conversations from who knows how much time ago and so on, I will quickly give you a rundown of everything we learned during this long, laborious but nevertheless fun and educational journey

As of afew days ago, a minimal binding to speech-dispatcher (the TTS system for Linux) was created, which wraps the C functions provided by Nolan’s speech-dispatcher-sys crate in a safe Rust API.