There is some confusion about terminology for making software accessible in the U.S.
There are receurring references to the Americans with Disabilities Act (ADA),
and making software ADA-compliant.
As best I can tell, "ADA-compliance" has no meaning because
the relevant law is not from the ADA but from Section 508 of the
Rehabillitation Act.
Regardless, people ask questions about the "level" of compliance to the ADA,
which as best I can tell, also has no meaning.
The ADA law is divided into "Titles":
- 2.2 Ensure that foreground and background color combinations
provide sufficient contrast when viewed by someone having color
deficits or when viewed on a black and white screen. [Priority 2
for images, Priority 3 for text].
YES: combinations printed in black and white and checked
- 3.1 When an appropriate markup language exists, use markup
rather than images to convey information.
NA: no special markup other than sub/superscript is used
- 3.2 Create documents that validate to published formal
grammars.
NO: to make the best use of the capabilities of our users' browsers,
we do not validate against a formal grammar.
For example, we use the unofficial, but widely supported
NOBR tags to keep items together on the same line.
It is impractical and perhaps inadvisable to tailor HTML
for a particular browser
(using only certain constructs that would allow validation
for a grammar version recognized by that browser)
because users save and/or email
HTML for use on possibly different browsers.
Instead, we deliver HTML that is effectively viewed on all browsers.
- 3.3 Use style sheets to control layout and presentation.
YES: we use these to the extent that they do not harm.
Widely used Netscape browsers have limited support for
style sheets, making them
- 3.4 Use relative rather than absolute units in markup language
attribute values and style sheet property values.
YES: although we sometimes use the built-in size numbers
(e.g., size=2) instead of size="-1",,
these are not absolute sizes; just another code to for a relative change
when the user changes the font size.
Example: size=2 size=-1
NO? In some data displays, we use absolute pixel width
to make sure cells in different tables line up.
There are no cases where this formatting is critical;
it is purely aesthetic.
- 3.5 Use header elements to convey document structure and use
them according to specification.
YES: in cases where we present documents such as full text and help,
header elements are used.
- 3.6 Mark up lists and list items properly.
YES: only simple one-level lists are used
- 3.7 Mark up quotations. Do not use quotation markup for
formatting effects such as indentation.
NA: quotations are not used
- 6.5 Ensure that dynamic content is accessible or provide an
alternative presentation or page.
YES: to the extent that dynamic content is used,
it is accessible or if not supported,
something functionally equivalent is provided
- 7.2 Until user agents allow users to control blinking, avoid
causing content to blink (i.e., change presentation at a regular
rate, such as turning on and off).
NA: we do not use blinking
- 7.4 Until user agents provide the ability to stop the refresh,
do not create periodically auto-refreshing pages.
NA: we do not periodically update the page
(JavaScript is used to display a countdown timer
for framed display of external information,
but this is not a refresh and it can be turned off)
- 7.5 Until user agents provide the ability to stop
auto-redirect, do not use markup to redirect pages automatically.
Instead, configure the server to perform redirects.
NA: we do not redirect the user automatically
NOTE: a possible exception is for JavaScript detection
at the start of a session; if JavaScript is enabled,
the user accessing the system via IP recognition
may be forwarded to a JavaScript-enabled page,
but that can be circumvented
- 10.1 Until user agents allow users to turn off spawned
windows, do not cause pop-ups or other windows to appear and do
not change the current window without informing the user.
NO: JavaScript help opens a new window
and sets the focus on that window; non-JavaScript help
opens a new window (target=help).
When the JavaScript help window is closed,
the focus is returned to the spawning window.
This is a difficult area because we want help
to be available while users are working on their tasks.
It might be useful to add an option to not-spawn new windows,
but the only request we have received was to set the
focus on the parent window when closing the spawned window.
- 11.1 Use W3C technologies when they are available and
appropriate for a task and use the latest versions when supported.
YES/NA: unfortunately, these new technologies are not
well supported across a large base of browsers in common use
- 11.2 Avoid deprecated features of W3C technologies.
NO: until there is widespread support for
replacements for depricated technologies,
those must be used (e.g., font).
- 12.3 Divide large blocks of information into more manageable
groups where natural and appropriate.
YES: but only as widely supported.
NOTE: some grouping mechanisms produce unwanted format changes
to the display (e.g., FIELDSET causes MSIE to show boxes on the screen)
- 13.1 Clearly identify the target of each link.
YES: labels are chosen to be interpretable alone,
or are augmented with title attributes
- 13.2 Provide metadata to add semantic information to pages and
sites.
YES: each page has a meaningful title
- 13.3 Provide information about the general layout of a site
(e.g., a site map or table of contents).
YES: the site is small and the left-navigation menu
can serve as a site map, showing what major areas are available
- 13.4 Use navigation mechanisms in a consistent manner.
YES: pages are generated using software
that ensures consistent navigation
And if you use tables (Priority 2)
- 4.2 Specify the expansion of each abbreviation or acronym in a
document where it first occurs.
NO: we do this for database names on the database selection screens,
but it is not done for pulldown menus,
and not enforced extensively
- 4.3 Identify the primary natural language of a document.
YES
- 9.4 Create a logical tab order through links, form controls,
and objects.
NO: this was found to not work for Netscape browsers
and was not used
- 9.5 Provide keyboard shortcuts to important links (including
those in client-side image maps), form controls, and groups of
form controls.
YES: accesskeys for Search (s) and Clear (c) are used
- 10.5 Until user agents (including assistive technologies)
render adjacent links distinctly, include non-link, printable
characters (surrounded by spaces) between adjacent links.
YES: adjacent links should be separated by printable non-link characters
- 11.3 Provide information so that users may receive documents
according to their preferences (e.g., language, content type,
etc.)
YES: language switching is available, printable formats, Lynx interface, etc.
- 13.5 Provide navigation bars to highlight and give access to
the navigation mechanism.
YES: the left navigation menu consistent provides global navigation
- 13.6 Group related links, identify the group (for user
agents), and, until user agents do so, provide a way to bypass the
group.
NO: this was attempted in the Lynx screens,
but added an obstacle to every screen
- 13.7 If search functions are provided, enable different types
of searches for different skill levels and preferences.
YES: home, basic, advanced, and expert search modes
- 13.8 Place distinguishing information at the beginning of
headings, paragraphs, lists, etc.
YES: all our objects begin with (or are) short distinct terms
- 13.9 Provide information about document collections (i.e.,
documents comprising multiple pages.).
NA
- 13.10 Provide a means to skip over multi-line ASCII art.
NA
- 14.2 Supplement text with graphic or auditory presentations
where they will facilitate comprehension of the page.
YES: extensive review by professional communicators
- 14.3 Create a style of presentation that is consistent across
pages.
YES: pages are generated from templates
And if you use images and image maps (Priority 3)