Re: Issue 364: Request to review decision to add plug-ins to checkpoint 3.5

Hmmm. I am not sure that all plugins can be removed (like not all browsers
can be removed from a system). I think the issue is about ensuring that the
user can disable content of different types, and maybe the way to handle it
is to write the requirements (which also apply to graphics) in that way.

Implementation example is iCab, which allows for fairly complex filtering of
content-types...

cheers

Charles McCN

On Fri, 5 Jan 2001, Ian Jacobs wrote:

  Hello,

  At the AOL ftf meeting, we decided for issue 364 [1] to add
  "plug-in" to checkpoint 3.5. From the 29 Dec draft [2]:

      3.5 Allow the user to configure the user agent
      not to execute scripts or applets. In this
      configuration, provide an option to alert the user
      when scripts or applets are available.

  I am not sure about this.

  As I understand it, a plug-in is a software module that
  the user has chosen to install as part of the user agent
  (to provide some specific services).

  This differs from an applet or a script that is part of
  author-supplied content.

  If a plug-in causes accessibility problems,
  the user can always remove it. I think that checkpoint 3.5
  is about controlling programmatic content supplied by the
  author.

   - Ian


  [1] http://www.w3.org/WAI/UA/2000/11/minutes-20001116#issue-364
  [2] http://www.w3.org/WAI/UA/WD-UAAG10-20001229/


-- 
Charles McCathieNevile    mailto:charles@w3.org    phone: +61 (0) 409 134 136
W3C Web Accessibility Initiative                      http://www.w3.org/WAI
Location: I-cubed, 110 Victoria Street, Carlton VIC 3053, Australia
until 6 January 2001 at:
W3C INRIA, 2004 Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France

Received on Saturday, 6 January 2001 14:24:27 UTC