Hi, Am Dienstag, 24. Juli 2018, 20:10:32 CEST schrieb Majid Hussain:
hmmm, what is YaST written in? qt, gtk?
YUI, which can make use of ncurses, Qt and previously also GTK.
if it is possable to have a copy of all the rpms for your installer I could test the accessibility of the app i'm running a system that deels with rpms presently,
I don't think it's possible to install YaST on any other distro properly.
wish it was opensuse, a note, when i need accessibility of root apps such as gparted, I run sudo -E gparted. the importent flag is -E I think it coppys enviroment settings or uses them note sure, would this info be of some use? i'm so glad you got back to me, was getting worried that this would have been abandend it's happend in the past with other things.
I just tried some more and I was able to get it to work, but only with quite some hacks. 1. The default speech-dispatcher configuration is broken. The "sd_espeak-ng" module has the wrong filename set. 2. The dbus session bus is not accessible from root (the policy disallows it), which means that YaST can't talk to speech-dispatcher. I worked around both of those by editing the configuration and then logging in as root manually, starting pulseaudio manually and setting up orca manually... Then I could start YaST and it says what each currently active element is ("Frame Frame Keyboard Layout Combo Box", for example). It doesn't seem to read out dialog window text though. I can open a bug report for 1., but I don't know what to do for 2. I think that the issues with YaST itself are severe enough that I would recommend using textmode instead. I don't know how to set it up for speaking though. It should be relatively straightforward to enable that in the installation system as an additional option though, once a working configuration is available. Cheers, Fabian
thanks, Majid Hussain
On 24/07/2018, Fabian Vogt <fvogt@suse.de> wrote:
Hi,
Am Dienstag, 24. Juli 2018, 15:04:15 CEST schrieb Majid Hussain:
hi there, who setts iso file size limitations?
It's at 1 GiB, a compromise between CDs and USB sticks.
brltty would be used for braille, orca for the speech along with espeak. I assumed having orca installed to the gnome live enviroment would gain speech when booted and you were to press alt plus f2 and type orca? ?
I assume so, yes.
without speech I am not able to install opensuse. or would it be possable to get your net install images talking? you would require espeakup and espeak to provide speech via the consol.
You can boot the net install (or the dvd) with "textmode=1 Y2_BRAILLE=1" to get a braille-compatible installation wizard. I'm not sure which state it is in though. No support for speech output I'm afraid.
I'm also not sure how well orca works together with YaST, especially if YaST is running as root in an otherwise regular session. I just wanted to give it a try in a live session but was actually unable to get speech-dispatcher working properly, it refused to load the espeak(-ng) module. Every button and tooltip resulted in "It seems that speech-dispatcher is working", which is a bit ironic.
If YaST works together with orca in a live session, it should be fairly easy to produce a special live media with tools for accessibility as a quick workaround. Hopefully temporary, but I don't see a solution yet. Additionally, the installed system might not have orca enabled on the first boot, that might require some additional work.
Cheers, Fabian
thanks, Majid Hussain
On 24/07/2018, Fabian Vogt <fvogt@suse.de> wrote:
Hi,
Am Dienstag, 24. Juli 2018, 13:12:06 CEST schrieb Frederic Crozat:
Le lundi 23 juillet 2018 à 18:39 +0100, Majid Hussain a écrit :
hi there, i'm very sorry if this is not the list to ask this, I am blind and require a screen reader to navigate around the screen. would it be possable to have gnome orca function from when the boot screen is ran?
It is unfortunately not possible right now:
Orca is only started if a gsetting key is set on the system (org.gnome.desktop.a11y.applications to the value screen-reader-enabled )
Some development would be needed to: - when enabling screen reading in boot menu, add a command line to kernel, to inform the system screen reader capability should be started
I just checked - it actually adds "braille=1" to the cmdline.
- once the system is started, automatically set the gsetting key I mentioned earlier, system-wide (so it would apply to gdm and logged user), so orca would be started automatically.
That sounds like something which shouldn't be specific to the live cd, but rather get included in gnome startup scripts.
Unfortunately there's another issue: The gnome live cd does not have enough free space for orca, brltty and co. left.
Now, somebody has to pick the ball and do the work..
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org