|
The true reason to
design for accessibility is greed. Quite simply, I want it all, and so
should you. Give us everything you’ve got. Give us everything there is to give.
Joe Clark (2002)
What you need to know about accessible web design
-
Much of the web is NOT accessible now
-
Access to web pages is covered by the
law (Disability Discrimination Act)
-
International guidelines exist which
describe standards for accessible web design
-
Many resources exist to help designers
design for access and usability
The legal basis
Provision of
information and other material through the Web is a service covered by the
DDA. Equal access for people with a disability in this area is required by
the DDA where it can reasonably be provided. This requirement applies to any
individual or organisation developing a World Wide Web page in Australia, or
placing or maintaining a Web page on an Australian server. This includes
pages developed or maintained for purposes relating to employment;
education; provision of services including professional services, banking,
insurance or financial services, entertainment or recreation,
telecommunications services, public transport services, or government
services; sale or rental of real estate; sport; activities of voluntary
associations; or administration of Commonwealth laws or programs. All these
are areas specifically covered by the DDA.
(HREOC, 2002)
International
Guidelines
Web Accessibility Initiative (WAI)
http://www.w3.org/WAI/
The Web Accessibility
Initiative (WAI) of the World Wide Web Consortium (W3C) published Web Content
Accessibility Guidelines 1.0 in 1999. These guidelines are seen as the
international benchmark for minimum accessibility standards. A second version
(2004) is currently in draft, and is available at the WAI site.
The current guidelines address
two general themes: ensuring graceful transformation, and making content
understandable and navigable.
The guidelines present a series
of checkpoints regarding web page design. Each checkpoint has a priority level
assigned by the Working Group based on the checkpoint's impact on accessibility.
Priority 1
A Web content developer must
satisfy this checkpoint. Otherwise, one or more groups will find it impossible
to access information in the document. Satisfying this checkpoint is a basic
requirement for some groups to be able to use Web documents.
Priority 2
A Web content developer
should satisfy this checkpoint. Otherwise, one or more groups will find it
difficult to access information in the document. Satisfying this checkpoint will
remove significant barriers to accessing Web documents.
Priority 3
A Web content developer may
address this checkpoint. Otherwise, one or more groups will find it somewhat
difficult to access information in the document. Satisfying this checkpoint will
improve access to Web documents.
Some checkpoints specify a
priority level that may change under certain (indicated) conditions.
Resources
Everyone Online, Australian Flexible Learning Framework
http://www.flexiblelearning.net.au/accessequity/everyone_online/index.php
|