E-mail List Archives
Thread: Frame Avoidance
Number of posts in this thread: 4 (In chronological order)
From: Tim Harshbarger
Date: Wed, Apr 09 2003 1:21PM
Subject: Frame Avoidance
No previous message | Next message →
Hi,
We have a web site for our team that we are doing maintenance on. We don't use frames and prefer to avoid them because of accessibility and usability issues.
On every page, we have a set of navigational links that always appear. Once in a while, we make changes to those links. However, the way the site was originally designed, this requires making alterations to every page on the site. That is definitely a maintenance nightmare.
Is there some method, which is accessible, that would allow us to store the information in a single place but also show up on every web page? Any information and details would be very helpful.
Thanks,
Tim
From: Holly Marie
Date: Wed, Apr 09 2003 11:40AM
Subject: Re: Frame Avoidance
← Previous message | Next message →
From: "Tim Harshbarger"
> Is there some method, which is accessible, that would allow us to
store the
> information in a single place but also show up on every web page? Any
> information and details would be very helpful.
Server side includes or PHP ?
This may be an answer?
holly
----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/
From: Kynn Bartlett
Date: Wed, Apr 09 2003 12:02PM
Subject: Re: Frame Avoidance
← Previous message | Next message →
Hi Tim,
What you have here is a failure of your Web publishing process
that leads to potential inaccessibility problems.
Your difficulty is this: You need a way to build your navigation
links once, and have them appear site-wide.
There are a number of solutions to this.
(1) Frames are, as many people have found, one of the worst
solutions. You are correct for discarding these for usability
and accessibility reasons.
(2) Server-side includes (SSI), mentioned already on this list,
are a very good solution. A server-side include is a tag which
is parsed by the server before the content is sent to the
browser; they can be set to run commands on the site or
simply include a portion of text from elsewhere.
(3) Server-side programming languages such as PHP can be
used much as SSI, to insert content where appropriate.
(4) Ultimately what you are going to need will be a better
process for Web publishing than simply serving up flat
pages. That is the Web publishing paradigm of the last
century, and we are in the 21st Century now. Acceptable
Web publishing strategies for 2003 MUST include some
kind of content management system (CMS) rather than
relying on static HTML files.
The simplest CMS can be assembled together using server side
includes or PHP, with flat "content" files and autogenerated HTML
output. This can be delivered on the fly, or can be generated as
HTML output documents whenever the site is updated.
A more advanced solution uses a database and/or XML documents
for content storage, but this is also very much doable on a
homegrown basis.
You can get pre-built content management systems, anything from
Movable Type (free for non-commercial use) to Vignette (thousands
of dollars). I recommend the open source or free versions for
most uses.
An existing site will need to be converted to use a content management
system, but this typically only has to be done once! There are a
number of benefits, including ease of maintenance, and also
increased accessibility options such as alternate interfaces
which become near-trivial to generate (harder to perfect, but the
actual creation is simple).
This was one of the topics in my recent talk at the CSUN conference
on 21st century Web accessibility, which you can find linked from
the Maccessibility.com blog:
http://www.maccessibility.com/archive/000254.php
--Kynn
On Wednesday, April 9, 2003, at 11:21 AM, Tim Harshbarger wrote:
> Hi,
>
> We have a web site for our team that we are doing maintenance on.
From: Tim Harshbarger
Date: Wed, Apr 09 2003 2:04PM
Subject: RE: Frame Avoidance
← Previous message | No next message
Holly, Jules, and Lori,
You will make my good colleague, Chris, extremely happy with this information! We knew there had to be some way, but he was becoming quite exasperated about finding an answer.
Thanks!!
Tim
-----Original Message-----
From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ]
Sent: Wednesday, April 09, 2003 1:28 PM
To: = EMAIL ADDRESS REMOVED =
Subject: Re: Frame Avoidance
Tim --
Meet the best thing since sliced bread, the server-side include:
I insert repeating menus into my pages thusly:
<!-- Include statement for inside top nav bar -->
<!--#include virtual="insidetopnav.html"-->
where the file called 'insidetopnav.html' is a snippet of HTML that I
use all over the site. (it's a good idea to code all hrefs and images
as absolute references in your include files, by the way.) This way
you can simplify maintenance radically but still write nice flat HTML
pages. Server Side Includes changed my life. :-)
You can learn how to configure Apache and use them here:
http://httpd.apache.org/docs/howto/ssi.html
I don't know how to do them in a non-Apache environment. Do other web
servers support something similar? I don't know.
Lori Kay Brown
User Interface Engineer
SiteScape, Inc.
E-mail: = EMAIL ADDRESS REMOVED =
-------- Original Message --------
==> From: Tim Harshbarger < = EMAIL ADDRESS REMOVED = >
==> Date: Wed, 9 Apr 2003 13:21:03 -0500
Hi,
We have a web site for our team that we are doing maintenance on. We
don't use frames and prefer to avoid them because of accessibility
and
usability issues.
On every page, we have a set of navigational links that always
appear.
Once in a while, we make changes to those links. However, the way
the site was originally designed, this requires making alterations to
every page on the site. That is definitely a maintenance nightmare.
Is there some method, which is accessible, that would allow us to
store the information in a single place but also show up on every web
page? Any information and details would be very helpful.
Thanks, Tim