When calling ObtainAuthorization(), a dialog is shown allowing the user to enter their password (at least in Ubuntu Hardy Heron). But when the wrong password is shown, the dialog is just re-shown, so all the user has as feedback is a flicker of the window rather than an explicit "The password was incorrect" message. Also, when the user cancels, there is no message saying that the system has not allowed the user to access the feature, so applications need to show (and translate) an (awkward) message to explain why they can't use the feature. Having that message in PolicyKit would probably lead to more consistency.
(In reply to comment #0) > But when the wrong password is shown, the dialog is just re-shown, so all the > user has as feedback is a flicker of the window rather than an explicit "The > password was incorrect" message. And how would this work? Show a message for about five seconds? I don't think that's any good nor accessible. Isn't it evident for the user that he didn't authenticate directly when he gets the same dialog? > Also, when the user cancels, there is no message saying that the system has not > allowed the user to access the feature, so applications need to show (and > translate) an (awkward) message to explain why they can't use the feature. > Having that message in PolicyKit would probably lead to more consistency. How do you propose we should explain this to the user? I think you really want application specific messages here; we can, at best, do only pretty generic stuff in PolicyKit. Besides, I'm not a big fan of putting up modal dialogs explaining things to the user. The UI, in the first place, should use subtle hints (such as greying out items or using padlock icons) to convey that some feature is not available. And that's exactly what PolicyKit-gnome is for; see PolKitGnomeAction http://hal.freedesktop.org/docs/PolicyKit-gnome/PolKitGnomeAction.html Scroll down a bit for the screenshot http://hal.freedesktop.org/docs/PolicyKit-gnome/polkit-gnome-example-screenshot.png
(In reply to comment #1) > (In reply to comment #0) > > But when the wrong password is shown, the dialog is just re-shown, so all the > > user has as feedback is a flicker of the window rather than an explicit "The > > password was incorrect" message. > > And how would this work? Show a message for about five seconds? I don't think > that's any good nor accessible. It could be an extra label on the dialog. Well, that's what web pages tend to do. But there should be plenty of similar things to look at. I'm not the best person to decided how to do it - I just know that it needs something. usability@gnome.org might be able to provide some advice. > Isn't it evident for the user that he didn't > authenticate directly when he gets the same dialog? No, I don't it's obvious. > > Also, when the user cancels, there is no message saying that the system has not > > allowed the user to access the feature, so applications need to show (and > > translate) an (awkward) message to explain why they can't use the feature. > > Having that message in PolicyKit would probably lead to more consistency. > > How do you propose we should explain this to the user? I think you really want > application specific messages here; we can, at best, do only pretty generic > stuff in PolicyKit. OK.
(In reply to comment #2) > (In reply to comment #1) > > (In reply to comment #0) > > > But when the wrong password is shown, the dialog is just re-shown, so all the > > > user has as feedback is a flicker of the window rather than an explicit "The > > > password was incorrect" message. > > > > And how would this work? Show a message for about five seconds? I don't think > > that's any good nor accessible. > > It could be an extra label on the dialog. Well, that's what web pages tend to > do. But there should be plenty of similar things to look at. I'm not the best > person to decided how to do it - I just know that it needs something. > usability@gnome.org might be able to provide some advice. > > > Isn't it evident for the user that he didn't > > authenticate directly when he gets the same dialog? > > No, I don't it's obvious. > Actually, I just remembered, we shake the dialog for half a second if there's an authentication error. So it's not true there is not feedback. But we might add an error message too in the future.
> Actually, I just remembered, we shake the dialog for half a second if there's > an authentication error. So it's not true there is not feedback. But we might > add an error message too in the future. Yes, I saw that shake but didn't realize that it was intended.
Hi, In response to http://blogs.sun.com/richb/entry/a_gnome_lock_screen_accessibility I tried to get a design proposal for this from the orca folks http://mail.gnome.org/archives/orca-list/2008-May/msg00868.html there weren't many suggestions, I think this message was the most helpful http://mail.gnome.org/archives/orca-list/2008-May/msg00877.html Thanks, James
This should be filed at b.g.o if it is still relevant. Thanks.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.