We discussed gestures that could launch AT login support in response to my first post on this thread, but I don't recall anyone addressing the other topic--the one in the Subject: line. -- What is the plan for SoundOnLogin=true ? Is it coming back? Should I just be patient? And, what's the thought on providing audio device support at this stage? Under the default pulseaudio, configuration the audio device isn't available until after the login succeeds. Clearly, this is a problem for the eyes-free user who requires a sonic cue to know when to proceed with the login ritual. Consider if the screen never painted the login dialog. How would that work for users waiting for that screen to display? That's very much the situation we screen reader users now find ourselves in. Lastly, let me note that there's a security dimension here that can only be solved by clearing up a11y login. Without appropriate At support, it's not all that hard to get out of sync with the GDM dialog and put one's password where the login ID belongs. I could show you my logs, but I wouldn't want to share my password. Unfortunately, it's there--in my logs. Janina Sajka, Phone: +1.202.595.7777; sip:janina@xxxxxxxx Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility janina@xxxxxxxx Linux Foundation http://a11y.org -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
