GNOME Bugzilla – Bug 420051
[a11y] gnome-screensaver does not work with AT programs
Last modified: 2009-11-18 13:59:33 UTC
The a11y infrastructure uses the LoginHelper interface so that AT programs like GOK or the magnifier which need to run in front of the screen can be displayed. Information is here: http://www.gnome.org/~billh/at-spi-idl/html/classAccessibility_1_1LoginHelper.html I don't believe gnome-screensaver supports this yet. Not sure if this is helpful, but at Sun we build xscreensaver and hack it to have a GTK+ dialog for a11y. This code implements this interface and you can look at it for an example of how LoginHelper is coded. http://src.opensolaris.org/source/xref/jds/test-specs/trunk/patches/xscreensaver-05-gtk-dialog.diff
Hi Brian. Is this related to bug #350716 at all?
I don't think they are related, aside from both being accessibility related. To me it sounds like bug #350716 is an issue that the entry field and labels aren't matched up with LABELLED_FOR and LABEL_TO, so that the entry field doesn't announce what exactly it is expecting. You should test this by running gnome-screensaver with orca and see how well it announces the entry field. You might refer to gdm bugs 355005 and 412576 for more information about this and how we fixed it in GDM. Note in GDM I couldn't figure out how to get LABELLED_FOR and LABEL_TO to work, I think because in gdmgreeter the text label fields aren't real GTK Label fields, but instead GnomeCanvasText. So in GDM I hacked it by just setting the label for the GTK Entry. A little more ugly, but at least the entry field will announce. This bug is that without implementing LoginHelper, programs like magnifier and GOK won't be able to appear in front of the lock screen program, so users who need them can't use them. Obviously, you could avoid using LoginHelper if you wanted if you implemented magnifier and on-screen-keyboard functionality directly into the screensaver. This might arguably be more secure, but would be more work. Since ORCA text-to-speech doesn't run with a GUI, it can run without LoginHelper support. You also might be able to use something like the technique GDM uses with the gesture listeners to launch AT programs. This might not work so well since the user may already be running the same AT programs, but might be something to look into if you wanted to look into alternative approaches to using LoginHelper. Perhaps you could use a similar mechanism to make gnome-screensaver pop specific programs over the lockscreen program. Is this more clear?
This might be a duplicate of #308533.
*** This bug has been marked as a duplicate of bug 308533 ***