Back to Silas S. Brown's home page
[Mailing list and bugs]
Web Access Gateway home page
The Web access gateway was an online ``browser within a browser'', giving you more control over how websites are displayed, regardless of which browser you have to use. The gateway had two main purposes:
- To make the Web easier to access for print-disabled users (such as users with low vision or dyslexia);
- To allow speakers of other languages to view Web pages written
in them, when the encodings were not supported by their browsers.
(This used non-optimal GIFs to work around the GIF patent problem.)
suitable for modern "Web application" sites.
- If you have a recent desktop browser, you might be better off using my stylesheets for low vision (although some web applications manage to break even on those).
The remainder of this page is now mostly for historical interest.
The gateway works by intercepting your Web browsing in such a way that the gateway computer can sort out the Web pages before you see them. It works with all browsers and operating systems as long as the browser supports
forms . You
can adjust it to work the way you want to.
The gateway can also (sometimes) be used as a rudimentary
viewer of such things as Flash and WAP, if you have no other
means of displaying them. In the case of WAP, the
intention is that print-disabled users can use WAP sites on
their normal desktop browsers.
Sites that have run the gateway publically in the
past include ACCU.org,
the American National Oceanic and Atmospheric Administration (NOAA),
the UK Japanese Embassy (Japan 2001 project), and
the Japanese Viewer Service at Monash University in Australia,
as well as a few machines in Cambridge.
These shut down for various reasons. Monash remained up the
longest---until December 2015---but ultimately had to close
because too much of their traffic quota was being used up by people
treating the gateway as a proxy to bypass Internet filtering at
work, and by badly-behaved "web robots" trying to discover email
addresses or Web forms for underhanded marketting activities.
(Yes, the fact that those spoilsports brought down an innocent public service does bring to mind Ps.58:6a, but let's not take it personally: the above-mentioned Web Adjuster installations are usually more suitable nowadays anyway.)
The Monash gateway is in fact still available, but at a private
address that we'll give out only to someone who convinces us
they really need it (explaining why Web Adjuster
is not a good enough replacement for them), plus promises never to
link to it.
Clark Lu in Cambridge is still running his public gateway on kangzhuang.ucam.org but on a personal machine with limited bandwidth. This server is currently experiencing problems due to inode exhaustion. It has images for Chinese, Japanese, Korean, Greek and Cyrillic. If you are using the gateway to read a language, please select the ``Disable all sight-related access options'' box and then the ``Characters'' button. Alternatively you can try presets for Chinese or Japanese (I couldn't write a Korean welcome page, but none of the Koreans I met wanted one anyway).
To install the access gateway on your Web server, you need
a shell account with sufficient privileges. FTP access is
NOT sufficient. If you do not have Unix then you have to
install various Unix tools; this has been done but it would
be simpler just to get a Unix shell account. Some degree of
Unix competence is assumed.
You will need to download access.tar.gz.
Create a directory for the access gateway to go in
(different from the cgi-bin directory), change into that
directory, unpack the .tgz file (using tar -zxf)
and run ./install.sh. This script should work on most Unix
systems. It will ask some questions, configure the gateway,
compile it and install it.
If compiling the image server on 64-bit, you may have to replace #ifdef NameCompareType with #if 0
The source is distributed under the terms of the
GNU General Public
License. There is absolutely no warranty.
The gateway has an extensions mechanism, which is
documented in extenlib.h.
The online help gives detailed information
about its use, and many users will be able
to start without having to read the help.
Some people expressed an interest in using the gateway
to preprocess their pages (ie. put up pages that have
already been processed). This can be used, for
example, on sites that teach a language where character
substitution is required. I've added a hack that lets
you do this:
You may wish to bookmark the long URL with the
&AP=1, for when you update the page. If you have
several pages that you want the gateway to process, you may
wish to write yourself an update script that does all this for
each page, for example, one containing commands like:
- Go to the page in the gateway and adjust the options to
- Append &AP=1 (case is important) to the
long URL and press Enter. You should now get a
version of the page that is suitable for saving as a
- Save it.
lynx -source "http://long-URL-goes-here&AP=1" >
Wildcards are also possible (using for).
Mailing list and bugs
The access-gateway-users mailing list at ACCU.org has now closed.
An incomplete bug list is available.
These bugs will not be fixed: I stopped maintaining Web
Access Gateway when I started writing stylesheets for low vision and
Disclaimer: The author is not responsible for, and has no authority
over, the websites that host the Access Gateway. There is no
warranty, either express or implied. It is the user,
not the author, that chooses which pages to process, and the
author does not endorse (and is not responsible for) any
illegal viewing or modification of data, whether the program
is functioning properly or not.
Silas S Brown & Peter Robinson. A World Wide Web Mediator for Users with Low Vision. CHI 2001 Workshop No. 14 (Seattle, USA). PDF format
 Technical footnote:
If you do not have a browser that supports forms, or you are
browsing the web via an email gateway, you can still use the
access gateway if you know how to read HTML forms and
generate CGI 'GET' URLs. In fact, you can use the
gateway to submit a 'POST' form using a 'GET' URL - the
gateway itself really doesn't care which method is used, and
will pass on the request as a 'POST' if you set the right
All material © Silas S. Brown unless otherwise stated.