AXSLIB-L Archives

Liberation Throough IT Accessibility (an EASI member list)

AXSLIB-L@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Alan Bern <[log in to unmask]>
Reply To:
Library Access -- http://www.rit.edu/~easi
Date:
Thu, 3 Apr 2003 15:44:33 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (58 lines)
FYI information on ALA's redesigned website below; I can forward questions to appropriate ALA people.

Alan Bern, Berkeley Public Library

***

The main elements of ALA's redesigned Web site will be compliant with
the W3C's Level 2 Web Accessibility Guidelines listed below. It is
important to understand that compliance with these standards is largely
dependent on the content developers understanding of the guidelines as
well as their ability to create content that complies with the
guidelines. Therefore, some components of the redesigned site may not be
consistent with these guidelines. We are working with all of our
internal and external content developers to ensure that the entire site
meets these guidelines. We appreciate any guidance offered by visitors
to the new site.  A new email address has been created to receive online
feedback at [log in to unmask]


Compliance with W3C's Web Content Accessibility Guidelines includes the
following tasks:
1.      Providing content that, when presented to the user, conveys
essentially the same function or purpose as auditory or visual content.

2.      Ensuring that text and graphics are understandable when viewed
without color.
3.      Mark up documents with the proper structural elements. Control
presentation with style sheets rather than with presentation elements
and attributes.
4.      Using markup that facilitates pronunciation or interpretation of
abbreviated or foreign text.
5.      Ensuring that tables have necessary markup to be transformed by
accessible browsers and other user agents.
6.      Ensuring that pages are accessible even when newer technologies
are not supported or are turned off.
7.      Ensuring that moving, blinking, scrolling, or auto-updating
objects or pages may be paused or stopped.
8.      Ensuing that the user interface follows principles of accessible
design: device-independent access to functionality, keyboard
operability, self-voicing, etc.
9.      Use features that enable activation of page elements via a
variety of input devices.
10.     Using interim accessibility solutions so that assistive
technologies and older browsers will operate correctly
11.     Using W3C technologies (according to specification) and follow
accessibility guidelines. Where it is not possible to use a W3C
technology, or doing so results in material that does not transform
gracefully, provide an alternative version of the content that is
accessible.
12.     Providing context and orientation information to help users
understand complex pages or elements.
13.     Providing clear and consistent navigation mechanisms --
orientation information, navigation bars, a site map, etc. -- to
increase the likelihood that a person will find what they are looking
for at a site.
14.     Ensuring that documents are clear and simple so they may be more
easily understood.

ATOM RSS1 RSS2