Making the Web Accessible to People with Disabilities, UPS Technology Seminar, Malaysia, June 2008

Duration: 10 minutes and 59 seconds

Year: 2008

Country: Andorra

Language: English

License: CC Attribution Share Alike

Genre: Instructional

Producer: Shawn Lawton Henry

Director: Shawn Lawton Henry

Views: 701 (12 embedded)

Posted by: accessibility on Jun 10, 2008

Introduction to web accessibility guidelines and resources from the W3C Web Accessibility Initiative (WAI). Presented at a Malaysian Communications and Multimedia Commission Technology Seminar on upcoming communications projects for underserved areas and underserved groups, including people with disabilities. June 2008. Transcript

Report this video as offensive

Translate and Transcribe

Sign In/Register for dotSUB to translate this video.

Share

Embed Video
Embed normal player
Embed a smaller player
Advanced Embedding Options
Embedding Options

Size:

Language:

Embed Code
Embed transcript
Embed transcript in:
Invite a user to dotSUB

Your invitation to join dotSUB was successful

There was an error inviting that user to dotSUB

Video Transcription

Show in new window

Hi. I’m Shawn Henry from the World Wide Web Consortium Web Accessibility Initiative.
Thank you very much for inviting me to this USP Technology Seminar.
I am excited about the work of the Malaysian Communications and Multimedia Commission,
and especially the inclusion of people with disabilities in the upcoming Universal Service Provision programs.
I appreciate the opportunity to talk to you today about making the Web accessible to people with disabilities
and the benefits of this to others. I would have loved to be there in person today;
Please do contact me if you want additional information, or to share your perspectives.
At the seminar today, distinguished speakers have talked about wireless and wired technologies
to connect rural communities and improve broadband connectivity.
These connections are one aspect of providing Internet access to underserved communities.
There is another important aspect, and that is making websites themselves accessible for all.
“Web accessibility” focuses primarily on making the Web accessible to people with disabilities.
Accessibility also makes the Web more usable for older users with accessibility needs due to aging,
people with low bandwidth connections, people using older hardware and software, people who are new Internet users,
people using mobile devices to access the Web, and people who are not fluent in the language of the website.
Currently there are significant barriers on the Web for many people with disabilities.
Because most web developers do not make their web sites and their web sites accessible, many people with disabilities
have unnecessary difficulties using the Web, and in some cases, cannot effectively use it at all.
For example, when developers require mouse interactions to use a website,
people who cannot use a mouse have great difficulty.
and when podcasts or other audio information is not provided in a text transcript or other accessible format,
people who are deaf cannot get the information.
However, when Web sites are accessible, they enable people with disabilities to use the Web effectively.
For example, people who are blind use screen readers that read aloud the information from the Web page.
When a web developer puts an image on her web page, she should provide alternative text for that image.
Then, when a screen reader gets to the image, it reads the text for the image.
All website owners and web developers have responsibility for making their websites accessible.
There are international standards that organizations and developers can use to know what they need to do
for Web accessibility, and what other web software needs to do for accessibility.
These are from the W3C Web Accessibility Initiative.
The W3C is the World Wide Web Consortium that develops interoperable technologies such as HTML, CSS, XML, etc.
The W3C provides these open Web standards so that the most fundamental Web technologies are compatible
with one another and allow any software or hardware used to access the Web to work together.
Within the W3C is the Web Accessibility Initiative (WAI).
WAI works with organizations around the world to develop strategies, guidelines, and resources
to help make the Web accessible to people with disabilities and more usable for all.
WAI's accessibility guidelines are recognized as the international standard for web accessibility.
There are currently three main accessibility guidelines from the W3C WAI.
The Web Content Accessibility Guidelines (WCAG) tells web developers how to make their website accessible.
WCAG itself provides a stable standard, and the supporting resources provide examples and
guidance on implementing accessibility in specific technologies, like HTML and CSS.
WCAG 2.0 is [nearing completion] and now is a good time for organizations to look at adopting WCAG 2.0 when it is finalized,
and now is a good time for developers to start working with it in their current web projects.
A related developing technology is the Accessible Rich Internet Applications Suite (WAI-ARIA).
It primarily addresses dynamic web content and web applications developed with Ajax and similar technologies.
While web developers play a key role in accessibility by following WCAG,
others also have responsibility for making the Web accessible,
especially those who develop the software used to create websites and web “content”.
These are called “authoring tools”. The WAI’s Authoring Tool Accessibility Guidelines
(ATAG) defines how these tools should support accessibility.
When authoring tools such as HTML editors and content management systems (CMS) support accessibility,
it allows developers to create accessible websites more efficiently.
Other types of authoring tools include blogs, wikis, social networking websites, and such.
It is important that these tools are accessible so that people with disabilities, and people in underserved communities,
can contribute to information and discussions online.
As you know in Malaysia, blogs can be very powerful vehicles for communication.
Finally, the web browsers, media players, and other (what we call) “user agents” also need to support accessibility.
The WAI’s User Agent Accessibility Guidelines (UAAG) defines what this software needs to do to for accessibility.
The W3C encourages adoption of its Web standards...
These guidelines provide stable standards that governments and organizations can adopt.
The supporting material provides “how to” examples for web developers and designers.
For more information about the accessibility guidelines and other web accessibility resources,
please see the WAI home page at www.w3.org/WAI
Following these standards has additional benefits as well.
For example, many websites –including many Malaysian websites–
use images for text instead of using real text and styling it with CSS (Cascading Style Sheets).
If the developers and designers used real text, then the websites would be more accessible,
they would use less bandwidth, and they would be better optimized for search engines.
One of the many resources on the WAI website is a document on the business case
for web accessibility that explains some of these issues.
It discusses the social, technical, financial, and legal & policy factors of web accessibility.
Tim Berners-Lee, who is the inventor of the World Wide Web and the director of the W3C, has said,
Not only is connection to the Internet important,
it is also vital that websites and web software are accessible to people with disabilities
and everyone, including older users with accessibility needs due to aging, people using mobile devices to access the Web,
and many others.
I thank you for your efforts to make the Web accessible, so that all will have the ability to receive information
as well as provide information and interact with society through the Web.
Thank you.