Having another look to that bug, is it specific to the install only mode
or also in the real session?
One issue is in that in install-only nothing starts orca, the indicator
is from gnome-shell but that's only settings a gsettings key. In a
normal session gnome-session is handling to activation/desactivation of
orca when the key is changing
I'm adding a patch that watches the gsetting key and active orca when
it's set to true. I didn't test it but it should work. Note that it
should probably be stopped when the key is to False then.
There might be other changes needed, calls like this used to be made
" subprocess.call(
['log-output', '-t', 'ubiquity', '--pass-stdout',
'casper-a11y-enable', 'onscreen-keyboard'],"
But they got deleted when the installed was transitioned by Luke to the
"a11y-profile-manager", which has been deprecated&removed since Luke
left, so there might be custom code that needs to be added back, see
http://bazaar.launchpad.net/~ubuntu-
installer/ubiquity/trunk/revision/6373
** Patch added: "not a real solution but an hint of what sort of change is
needed"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1719995/+attachment/4968980/+files/ubiquity-screen-reader.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719995
Title:
Screen reader does not read Ubiquity windows
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1719995/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
