Home | Issues | Users | Motives | Tools | Resources | Validators
A screen-reader is used to allow navigation of the screen presented by the operating system, using speech or Braille output, and should therefore enable use of any mainstream application. In the context of browsing this usually means that they are used in conjunction with Netscape, Microsoft Internet Explorer, or, less often, with one of the other non-disability-specific browsers such as LYNX and Opera.
JAWS for Windows, "the world's premier screen reader software
application. JAWS for Windows may be authorized for Windows NT, Windows 2000
Professional or Windows 95/98/ME." (free timed evaluation version available)
http://www.hj.com/JAWS/JAWS.html
Home Page Reader by IBM can speak text, frames, image and text links,
alternate text for images and image maps, form elements, graphics descriptions,
text in column format, and data input fields. It even includes special table
navigation features that allow users to understand even the most complex tables,
such as television listings.(free timed evaluation version available)
http://www-3.ibm.com/able/hprtrial25.htm
W3C provides a list of the home pages of all the major developers of
screen-readers for different versions of Windows, and including one for Macintosh.
(all provide demonstation versions)
http://www.w3.org/WAI/References/Browsing#2
Opera is a more recent browser that is gaining in notoriety
and popularity. It is designed to be "accessibility friendly" and
is preferred by many with disabilities, especially motor. The web site says
it is the "fastest browser on earth." (trial version available)
http://www.opera.com/
Lynx is a text mode web browser. Lynx is possibly the most widely used
text mode browser on the Internet. It runs on a wide variety of platforms, including
Unix, VMS, Macintosh and Windows. Lynx is a full-featured browser. (free)
http://www.delaware.net/support/downloads/lynx/index.html
Amaya- W3C's Editor/Browser
Amaya is a browser/authoring tool that allows you to publish documents
on the Web. It is used to demonstrate and test many of the new developments
in Web protocols and data formats. Given the very fast moving nature of Web
technology, Amaya has a central role to play. It is versatile and extensible
and is available on both Unix and Windows '95/NT platforms. (free)
http://www.w3.org/Amaya/
W3C Alternate Web Browsing
W3C brings forth a fascinating discussion and listing of many of the "other"
browsers available. The web site introduces the topic, "This is a collection
of pointers to information, and where possible, to demonstration versions of
alternative browsing methods. People with disabilities, whether temporary --
such as a slow connection or eyes "disabled" by having to watch traffic -- or
permanent -- such as hearing, visual, physical or cognitive impairment -- use
a wide range of alternative approaches, different from traditional mouse-and-screen-based
browsers."
http://www.w3.org/WAI/References/Browsing
Web Browser List
A list of browsers with information about them is made available by some
college students. The say, "the point of this site is to show what sort
of browsers are out there so people are aware of what options they have.
Yes, there is a choice of browser for your computer! From PC running Windows,
to Unix machines to Amigas and beyond, there are always options, we hope to
show you what some of those are so you can make an informed decision when you
go to pick your browser(s)."
http://www.browserlist.browser.org/browser_list.shtml#Disabilities
There are three sets of guidelines offered by W3C; for 1) web authors/designers, software authors-for 2) authoring tools and for 3) browsers:
Web Content Accessibility Guidelines
WCAG are the to-do's and the to-dont's for web site authors/designers, these
guidelines point to the best practices for usability. The W3C web site explains
their guidelines:
"These guidelines explain how to make Web content accessible to people
with disabilities. The guidelines are intended for all Web content developers
(page authors and site designers) and for developers of authoring tools. The
primary goal of these guidelines is to promote accessibility."
http://www.w3.org/TR/WAI-WEBCONTENT/
Techniques for Authoring Tool Accessibility
Authoring tools are software programs such as Dreamweaver, Front Page, HotMetal,
Home Site, Go Live, etc. which are used to create web sites in a WYSIWYG environment.
Guidelines are provided for those that write the software.
The W3C web site explains their guidelines:
"This document provides information to authoring tool developers who wish
to satisfy the checkpoints of "Authoring Tool Accessibility Guidelines 1.0"
[ATAG10]. It includes suggested techniques, sample strategies in deployed tools,
and references to other accessibility resources (such as platform-specific software
accessibility guidelines) that provide additional information on how a tool
may satisfy each checkpoint."
http://www.w3.org/TR/WAI-AUTOOLS-TECHS/
User Agent Accessibility Guidelines 1.0
User agents are web "browsers" such as Internet Explorer, Netscape,
Opera, Lynx, etc. The browsers should render web pages in ways that allow for
accessibility. The W3C web site explains their guidelines:
"This document provides guidelines for designing user agents that lower
barriers to Web accessibility for people with disabilities. User agents include
HTML browsers and other software that retrieves and renders Web content. A user
agent that conforms to these guidelines will promote accessibility through its
own user interface and through other internal facilities, including its ability
to communicate with other technologies (especially assistive technologies).
By following these guidelines, developers will create more usable software for
all Web users."
http://www.w3.org/TR/UAAG/
Disclaimer: the information relating from the US Govt below is publicly available information reported from the web sites referenced. This information is simply reported to you, the author's comments are added for your consideration and carry no authority.
"In 1998, Congress amended the Rehabilitation Act to require Federal agencies
to make their electronic and information technology accessible to people with
disabilities. Under Section 508 (29 U.S.C. § 794d), agencies must
give disabled employees and members of the public access to this
technology that is comparable to the access available to others. The law applies
to all Federal agencies when they develop, procure, maintain, or use electronic
and information technology."
http://www.section508.gov
[Authors note: the Section 508 Web Site offers training in several forms. It is a based on the W3C Initiative and Guidelines but is easy to use and worthwhile.]
However, at this point the US Government defers to the guidelines and work
of the World Wide Web Consortium concerning web sites and pages.The FITAI identifies
"13 Rules for Accessible Web Pages":
http://www.section508.gov/docs/webrules.htm
Top | Home | Issues | Users | Motives | Tools | Resources | Validators
Web Site Updated December 8, 2000
Web Site Created November 20, 2000
By Bill Teysko, teysko@home.com
For CIS213,
Cuyamaca College, El Cajon, CA
Url: http://www.oocities.org/webaccess2k
Credits page