Re: Accessible Login in 12.04?
Hy Luke, CTRL+S works correct, thank you the answer. I have got some question and experiences, sorri if my questions is trivial, but I now using first LightDM with accessible login feature. 1. How can possible choosing different user? If I press arrow keys, usual hear give my username password, or hear a button. Or this function is not full accessible yet? Need enabling a GDM style user list in LightDm configuration? Possible doing this? Oldest time in GDM login screen all awailable users present default a list, with possible choose required user to log in. If pressed ENTER key the selected user, possible write password, and switch session. 2. If I try using flat review in the Unity greeter, I think Orca is freezing. I unable to debug Orca level this situation yet. Possible changing local Orca execution command to generate Orca a debug.out file, or this is already known issue? 3. If I activate indicator menu in Unity greeter with F10 key, choosing some menu items and press ESCAPE key, the menue is doesn't leave, or Orca not refresh the screen content. My braille display this is absolute presenting. 4. What the difference with Unity Greeter and LightDm gtk greeter? LightDm Gtk greeter is possible using, this greeter more accessible? Attila -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
RFC, disable the HUD for accessible installs.
Hi all, With all the discussion recently about the hud, and how its not accessible, I've been looking at the hud code for Unity 2D, investigating why its not accessible. It turns out that the Unity 2D devs did indeed do their part in making sure the hud is accessible as possible, however the results, whilst being indicated as buttons, do not have any text spoken. This is because the Unity 2D devs decided to use a text string different to what visually gets shown, for various reasons. The problem is, that this text string coming from the hud service process is currently always an empty string. Setting about working out an alternative, I realized that at this late stage of precise development, this could not be properly solved without getting a fair number of exceptions in the form of feature freeze exceptions, UI freeze exceptions, as well as getting strings translated. In addition, I have not yet been able to come up with a way to audibly indicate hud search results. Sure I have an idea, but I am not sure if there should be more detail. So at this point, I think we'd be better off disabling the hud for screen reader installs, due to the above. I.e, since we don't have time to work out an audible representation of hud results, and get it implemented and tested, I think disabling the hud is a better course of action. I'd rather have the hud available when its fully accessible with results that Orca users can understand, than have a half-baked accessible implementation that could confuse users. I will start a discussion about how we could best represent hud results in another thread. Luke -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Accessible Login in 12.04?
On Thu, Mar 15, 2012 at 08:16:01PM EST, Hammer Attila wrote: > Hy, > > I see happened an upgrade with Casper package, to migrate LightDm > a11y settings with GSettings, because Unity Greeter using GSettings. > > When I try use an installed system in terminal the sudo -u lightdm > gsettings set com.canonical.unity-greeter screen-reader false > command, I get following error: > hammera@hammera-Satellite-L300:~$ sudo -u lightdm gsettings set > com.canonical.unity-greeter screen-reader false > > ** WARNING **: Command line `dbus-launch > --autolaunch=57457bea3de3d18c6e5b5034000d --binary-syntax > --close-stderr' exited with non-zero exit status 1: No protocol > specified\nNo protocol specified\nAutolaunch error: X11 > initialization failed.\n > > ** WARNING **: Command line `dbus-launch > --autolaunch=57457bea3de3d18c6e5b5034000d --binary-syntax > --close-stderr' exited with non-zero exit status 1: No protocol > specified\nNo protocol specified\nAutolaunch error: X11 > initialization failed.\n > hammera@hammera-Satellite-L300:~$ The reason why that doesn't work is due to the way gsettings works. Gsettings supports multiple backend data storage formats, one of which is dconf. Dconf is the default data storage format, which is a database stored at the system/user level. When gsettings wants to use dconf, it communicates via dbus to a dconf service process that runs as the user. This dconf service process makes the requested changes. So the above doesn't work, because there is no dconf service running as the lightdm user when you are logged into the system as another user. > Look what the result if I run sudo -u lightdm gsettings get > com.canonical.unity-greeter screen-reader command: > hammera@hammera-Satellite-L300:~$ sudo -u lightdm gsettings get > com.canonical.unity-greeter screen-reader > false I have seen this myself. I suspect either there is some caching going on somewhere, or the gsettings dconf backend can read the database itself, but cannot write. > During installation this GSettings key with LightDm are setting properly? Yes, when the screen reader profile is enabled, this key now gets set. That was one of the changes in the updated casper package. > How can possible enable an installed Ubuntu 12.04 system the screen > reader support in login screen if this error is present? Temporary > need sighted assistance? Control + S should work in the unity-greeter, however there are some weird focus issues when unity-greeter first loads, which for some reason prevent control + S from working. If you tab to the session selection box, and shift-tab back to the password prompt or login button, and then press Control + S, Orca should load. When you press Control + S, the screen reader will be active for every subsequent use of unity-greeter, until its turned off again. Luke -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[no subject]
http://pere.xprecords.net/themes/bartik/templates/eyt.html Terry Jones terryjones...@msn.com Veronica McKinney 3/15/2012 7:02:51 PM -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Possible some time gsettings-data-convert doing mistake with keybinding preferences?
Hy, Because I haven't got other ydea some time why stored invalid keybinding settings in .gconf/apps/metacity folder, I reported the prewious wrote problem with Metacity related: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/955876 If anybody known the right component, please change the report. For example now again forgotted Metacity the general keybindings, and the described error is present. I again removed the .gconf/apps/metacity folder, and next restart keybindings works again. Attila -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Accessible Login in 12.04?
Hy, I see happened an upgrade with Casper package, to migrate LightDm a11y settings with GSettings, because Unity Greeter using GSettings. When I try use an installed system in terminal the sudo -u lightdm gsettings set com.canonical.unity-greeter screen-reader false command, I get following error: hammera@hammera-Satellite-L300:~$ sudo -u lightdm gsettings set com.canonical.unity-greeter screen-reader false ** WARNING **: Command line `dbus-launch --autolaunch=57457bea3de3d18c6e5b5034000d --binary-syntax --close-stderr' exited with non-zero exit status 1: No protocol specified\nNo protocol specified\nAutolaunch error: X11 initialization failed.\n ** WARNING **: Command line `dbus-launch --autolaunch=57457bea3de3d18c6e5b5034000d --binary-syntax --close-stderr' exited with non-zero exit status 1: No protocol specified\nNo protocol specified\nAutolaunch error: X11 initialization failed.\n hammera@hammera-Satellite-L300:~$ Look what the result if I run sudo -u lightdm gsettings get com.canonical.unity-greeter screen-reader command: hammera@hammera-Satellite-L300:~$ sudo -u lightdm gsettings get com.canonical.unity-greeter screen-reader false During installation this GSettings key with LightDm are setting properly? How can possible enable an installed Ubuntu 12.04 system the screen reader support in login screen if this error is present? Temporary need sighted assistance? Alan, when you tested the accessible login with screen reader when you reported the proper bug, how can enabled this function? Attila -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
