- From: Ian Jacobs <ij@w3.org>
- Date: Tue, 30 Jan 2001 10:00:41 -0500
- To: "Hansen, Eric" <ehansen@ets.org>
- CC: "'Jon Gunderson '" <jongund@uiuc.edu>, "'UA List (E-mail) '" <w3c-wai-ua@w3.org>
"Hansen, Eric" wrote: > > One follow-up thought. > > Perhaps one way to think about this issue is that the User Agent should "by > default" not restrict access to any content. If some content uses the user > agent to restrict access to certain content (or even if the user agent makes > it easy for the content author to restrict access) to some content (e.g., > for security or other special purposes or applications) then that is okay. I think that amounts to saying: "conform to specifications". Otherwise, if a user agent haphazardly denies access to some content, it's probably just a bug. > It is not the responsibility of user agent developers to forbid such > activity, but rather to ensure that in the default situation, the user would > have access to all content. Obviously, the realization of full access will > be dependent on authors developing content that permits such access (e.g., > following WCAG 1.0, other accessibility conventions, etc.). > > Isn't this approach in keeping with our delineation of responsibilities? Do > we lose anything by taking this approach? What does 'taking this approach' mean exactly? - Ian > I suppose that such an approach > impinges on our UAAG 1.0 checkpoints insofar as user agents > product content (one checkpoint). -- Ian Jacobs (jacobs@w3.org) http://www.w3.org/People/Jacobs Tel: +1 831 457-2842 Cell: +1 917 450-8783
Received on Tuesday, 30 January 2001 10:00:46 UTC