This is a fantastic discussion and many of my thoughts have been covered already. Perhaps it is worth getting a bit more abstract and thinking of a few scenarios so as to cover all uses.
1) Single user: They want their AT/a11y config(s) remembered at login and beyond. Arguably some may don't even want to login but I think that would not be a good idea. 2) multi user: Each user will need a unique AT/a11y config for login but don't know AT requirements until user is identified and at the moment this means logged in. 3) clinical/education/corporate: support staff will want to configure AT for individual users and ideally deploy remotely. Note here the user is not directly responsible for selecting their AT/a11y. Once better ways of identifying people arrive (biometrics, Near Field Computing, RFID etc. etc.). then the problem gets simplified as a users custom AT config could be automatically selected before authentication (login). 'Till then the solution has to be to provide sets of configs that can be easily selected before login, as discussed. Some predefined common cases and the ability add more should cover the scenarios. A simple list of named configs should be the simplest UI, with various gestures to access. As a bit of blueskying a 2 level system might work but it does seem more complex and may be unworkable. I'm thinking of a course selection for vis/mobil with simple gestures or selection by device used, that load ATs for selection of individual config using richer gestures. It occurs to me that we really want a extra layer of gesture abstraction where gestures on various devices (possibly more than one) get mapped to actions in the OS and applications. Failing that we have to map the gestures to standard input (key and pointer). The trouble is input and output are never quite so decoupled, as in the case of screen readers. -- Steve Lee -- Jambu - Alternative Access to Computers www.fullmeasure.co.uk _______________________________________________ gnome-accessibility-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
