- From: Al Gilman <asgilman@iamdigex.net>
- Date: Tue, 21 Aug 2001 10:52:57 -0400
- To: tina@elfi.org, w3c-wai-ig@w3.org
At 10:34 AM 2001-08-21 , Tina Marie Holmboe wrote: >On Tue, Aug 21, 2001 at 09:13:52AM -0400, David Poehlman wrote: > > [ Could you quote according to standard, please ? It really messes > up my mail-handling. Thankyou. ] > >> yes, we still have a problem. the less "special" requirements on the >> user end to make a product usable, the more likely the product will be > > Hm. It seems to me that what you are suggesting, here, is that > any built-in method for changing the behaviour of a system falls > into the 'special requirement' cathegory ? > AG:: No, no, no. But command-line switches are a 'special requirement' for a Windows user, by gum! You have to create a scriptlet that invokes with the command line switch and then create a shortcut to the scriptlet. Not equivalent facilitation to your basic install and personalization assistance. It is precisely to avoid burdening user with this kind of requirement that the makeUserProfile wizard was introduced in the first place. The wizard is a mode-specific implementation of something that optimizes getting going for GUI capable users and makes it worse for those not GUI capable because now the other way of doing it is there but inadequately documented and supported and all that. Search the UA list archives for 'rosmaita' for discourses on the documentation requirements of the UAAG. This is a chronic sore point, that because initial configuration functions are infrequently performed the publishers forget to make them accessible. Thereby defeating the access to all the accessibility mods they put into the in-use mode. Al > I would have no difficulty understanding the problem IF the dialog > you speak of was a) impossible to get around, and b) always necessary. > > The profile dialogue of Mozilla is needed only in the event of a > multi-user system, and in such a case can be configured to start > with the profile matching the user currently logged in. > > Should the dialogue be useable with JAWS, it still requires the user > to select a profile before proceeding. Specifying it directly seems > a much more flexible and useable method; as well as leaving the > profile handling to the system administrator instead of the user. > > Could you describe in more detail the problem you see here ? I am > quite sure I've not understood it properly. From my point of view > it seems that any system you can set up to automatically remove > unnecessary bits and pieces of 'fluff' is *more* accessible, not less. > > It certainly does remove complexity that way. > > > Thankyou. > >-- > - Tina Holmboe >
Received on Tuesday, 21 August 2001 10:33:54 UTC