> I'd say it's at points 3 & 4: if the screensaver does require the > usual key touch or mouse move, but doesn't understand any other > type of input (e.g. voice). Yes, there's no info on the screensaver, > but if a user without mouse and keyboard can't make it go away,then > it is seriously blocking access to information. > So a section 508 compliant screensaver does not watch for mouse and > keyboard but user input in general. thx - I *knew* I was missing something. That (an app for sniffing all user input) would obviously be well outside a web developers scope then. * * Please support the community that supports you. * * http://evolt.org/help_support_evolt/ For unsubscribe and other options, including the Tip Harvester and archives of thelist go to: http://lists.evolt.org Workers of the Web, evolt !