TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Jeanne A. E. DeVoto wrote:
>One ironic note: the original poster, katav -at- YAHOO -dot- COM, suggested that
><noFrame> support was needed for Lynx users. However, current versions of
>Lynx do support frames. ;-)
One thing I've seen mentioned only in passing in this thread is the fact
many people with various disabilities rely on assistive technology and
various "non-standard" web browsers to get around.
While current versions of Lynx do "support" frames, that is, they can
display the pages after a fashion, the following framed page (the source
of which shall remain nameless) does not help the browser figure out
where to go to get information (this is actual text from an actual web
page).
FRAME: xy
FRAME: z
Wow! That's helpful! And the really sinful thing is that the addition
of a handful of ALT= and TITLE= tags (maybe a few minutes work at
worst) could have made this a much more useful site without changing
the look even a little.
HTML authors really should check out some of the fairly simple things
that they can do to increase the accessibility of their pages. Many
of them can be done without changing the look of the page at all.
