Hello, Just some thoughts quickly put together: * I assume the gnome desktop will load automatically. When gnome starts it would be useful to have the start up sound enabled then a blind user knows the system is ready to start using. * Following from the above, people may say, why is the sound needed if orca starts automatically. My problem with that idea is that either all users have orca starting or a blind user has to navigate a boot menu to choose the blind boot process and normally these boot menus are inaccessible (you are relying on doing it right). * It might be nice to have a shortcut key to start orca, but this at the moment would be non-standard and should be documented. Admittedly the user could press alt+f2 and type orca but again that relies on doing multiple things correctly (eg. did the user start typing orca before the run dialog appears). * Braille displays, not sure, USB ones tend to be correctly detected by brltty but I think serial and bluetooth would need additional configuration before you are able to use it. * As for starting other tools, I guess that depends on the needs of those users. I don't see the need for all start up methods to apply to all ATs. As an example a keyboard shortcut to me sounds a bit pointless for starting an onscreen keyboard (I am logically working that through, a user who can't use the keyboard won't be able to press a keyboard shortcut, but you probably would be best to check). Like wise, an icon to start Braille seems a little pointless as how would a blind user visually find the icon (OK, may be a partially sighted Braille user, but if they knew of the shortcut would they just press the keys). I think that covers certain desktop integration issues, a quick glance at some of the specifics like evince, etc I don't notice anything I really want to comment on. Michael Whapples On 01/-10/-28163 08:59 PM, Mario wrote: Hello everybody, |