The place where it makes a big difference is with Image Maps.  In a
server side image map, the regions that form links, and the links
themselves, reside on the server, and are not visible to the browser at
the user's end.  Hence, there is no way to detect the links available
and display them in a tabular form, for example.  These are really bad
from an accessibility point of view.

Denis Anson, MS, OTR
Computer Access Specialist
College Misericordia
301 Lake St.
Dallas, PA 18612
email: [log in to unmask]
Phone: 570-674-6413


> -----Original Message-----
> From: * EASI: Equal Access to Software & Information
> [mailto:[log in to unmask]] On Behalf Of Rosemary Ernst
> Sent: Monday, October 29, 2001 11:02 AM
> To: [log in to unmask]
> Subject: Re: HTML, Server Side Includes, Frames
>
> Okay, here goes. A server side include usually puts out specific code
for
> specific users. Once that code is produced for the user, it doesn't
matter
> where it came from. The trick is to be sure the server is detecting
what
> it
> needs to detect, in order to put the proper code out to the user.
Unless,
> I
> misunderstand your question, it seems you would benefit from learning
more
> about the difference between server side and user side. This forum
does
> not
> usually respond to questions regarding code.