Feature #14522: Make Tails usable for blind users
Orca reads neither Tor Browser nor Thunderbird if started after it
To reproduce on Tails 1.3.2:
1. Start Tails without networking.
2. Start Tor Browser.
3. Start Orca (Applications → Universal Access → Orca) and click Ok to enable default options.
4. Double-click on some text on the Tor Browser error page.
5. Nothing is read.
If you invert steps 2 and 3, the text in step 5 is read.
My understanding of the code in accessible/atk/Platform.cpp is: if this envvar
is not set, Firefox will check via D-Bus at startup if accessibility is enabled
in the Desktop, and if it's not it'll permanently disable accessibility,
which breaks use cases like starting the screen keyboard or screen reader
after Tor Browser.
I did not check the source, but the reasoning from
a3346a75d957d4dfdda91b5e79ed29baca4c92e7 probably applies here as well.
In any case, the symptoms are the same, and the same fix works.
#3 Updated by intrigeri over 4 years ago
I can reproduce this. I see no corresponding AppArmor log messages, so I think it's unrelated. Now, I'm inclined to flag this as low priority, if not rejected: a user who needs Orca will have it started first... otherwise they'll simply be unable to start Tor Browser.