WEB ACCESSABILITY
Download
Report
Transcript WEB ACCESSABILITY
WEB ACCESSABILITY
Web Accessibility in Reality
List of Content
Background
– What is the issue?
Moving on
– How can me learn more?
Some QuickTips
– What can we do now?
This material is mainly from W3C and ISOC Vietnam
Background
What do we mean by Accessability?
– Content is accessible when it may be used by
someone with a disability.
W3C / WAI (Web Accessibility Initiative)
– Impact of the Web on People with Disabilities
– Why is Web Accessibility an Issue?
– Web Accessibility is a Cross-Disability Issue
Why is Web Accessibility an Issue?
There are several reasons why Web accessibility is important:
– use of the Web is spreading rapidly into all areas of
society;
– there are barriers on the Web for many types of
disabilities;
– millions of people have disabilities that affect access to
the Web;
– Web accessibility has carry-over benefits for other
users;
– some Web sites are required to be accessible.
Web Accessibility is a Cross-Disability Issue
The Web can present barriers to people with different kinds of
disabilities:
visual disabilities:
– unlabeled graphics, undescribed video, etc.
hearing disabilities:
– lack of captioning for audio, etc.
physical disabilities:
– lack of keyboard or single-switch support for menu commands
other disabilities (ex. Cognitive, technical):
– lack of consistent navigation structure, overly complex presentation
or language, low connection speed, small displays etc.
What do we do now?
Validate your pages (W3C, Cast/Bobby)
Getting Started (also in Vietnamese)
10 QuickTips (also in Vietnamese)
Full checklist http://www.w3.org/TR/WAI-WEBCONTENT/full-checklist.html
Read & follow W3C Recomendations
5 recommendations to a better Accessible Website:
1. Always state the W3C standard that the
page are based on. Every page should start
with stating this.
The ISOC pages are following XHTML 1.0 standard and the
transitional dtd. Every page (in Vietnamese) on our site should
start with:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 transitional//EN”
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd
<html xmlns=http://www.w3.org/1999/xhtml lang="vi">
5 Recommendations ... 2
2. You should always have alternative text for
every photo and image on your site.
Then screenreaders and non-images
browsers like Lynx can read and show them
properly.
Example:
<img src="images/UKflagtop.gif" border="0" alt="English version" />
5 Recommendations ... 3
3. Use external CSS for text size, fonts and
colors. Separate information from its
presentation.
This gives you a much more flexible page and it is
also easier for people with their own .CSS to use it on
your site. Always use relative sizing instead of fixed
numbers. If you do not know how to begin then you
can use the ISOC Vietnam CSS and then modify it.
5 Recommendations ... 4
4. Be modest in putting a lot of images,
scripts and other features on your site if
it does not add something valuable to
the content.
This will only make it slow to download. Since
a lot of people is sitting on computers which
they are not allowed to upgrade your "full
feature flash movie" may not be accessible.
5 Recommendations ... 5
5. Use heading1, heading2, paragraph
and so on for stating text structure.
This is very helpful especially on large sites
when you can use the functions of just
reading the headers in order to "scan" the
site. This is very much used by blind people
to get an overview of the site.
Examples
Screenreader (Jaws)
Non-image browser (Lynx)