E-mail List Archives
Thread: Video Resources
Number of posts in this thread: 3 (In chronological order)
From: Candace Egan
Date: Fri, Jun 20 2003 12:30PM
Subject: Video Resources
No previous message | Next message →
Following up on Oliver Burmeister's message about his instructional video, you may
find two videos we produced to be of interest.
"Web Accessibility: Access For All" provides an overview of what Web accessibility
is, what it means to users with disabilities, and some suggestions for making pages
accessible. 10 minutes. (The clips are captioned.)
"Know Your Users: Web Accessibility From the Users Perspective". This is a
follow-up to the first video with a more detailed look at how users with
disabilities access the Web. Users demonstrate the assistive technologies they use
and the problems they face. 27 minutes. (Eventually, the segments will be available
for viewing on the Web.)
Go to http://www.csufresno.edu/webaccess/ to view all the segments from "Web
Accessibility" and a highlight video from "Know Your Users." There are also support
materials for "Web Accessibility" including a PowerPoint presentation that is
available for you to use in your own training.
Candace
--
--------
Candace Lee Egan
Educational Technology Consultant
Academic Innovation Center
California State University, Fresno
(559) 278-5070
----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/
From: Gerard Corboz
Date: Wed, Jun 25 2003 11:36PM
Subject: Accessibility of complex HTML forms
← Previous message | Next message →
Having done quite a bit of research into making accessible HTML forms, I
feel quite confident in regards to simple forms but I am not so sure in
regards to complex forms.
What I mean by a simple HTML form might a form, that might simply ask for
name, address, date of birth, phone number, and email address. This is
obviously a very simple form that does not have any triggers or jumps.
What I mean by a complex form is one that contains triggers or jumps. For
example, the form might ask if the user has children. If the user answers
yes then the user is expected to answer a large subset of questions related
to their children. Alternatively if the user does not have children, they
must skip to question xxx.
One way to handle the complex form example I described above is to use DHTML
such that if a user answers yes to having children, the children related
questions will dynamically appear.
What I'd like to know is how do screen readers handle this kind of DHTML?
Will the screen reader start from the top of the page thinking that the page
it is reading is new or will it continue reading from where I left off?
Does anyone have any suggestions on how one could provide a solution for the
complex form example above that is usable and accessible?
Regards
Gerard Corboz
---------
Perform
Information Design Solutions
ph: 6214 0968
fax: 6214 0964
mobile: 0402 236 358
http://www.perform.net.au
Join our mailing list - http://www.perform.net.au/News/
---------
Important
The information transmitted in this email is for the use of the intended
recipient only and may contain confidential and/or legally privileged
material. If received in error, please delete all copies and advise the
sender. The reproduction or dissemination of this email or its attachments
is prohibited without the consent of the sender.
----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/
From: Jukka K. Korpela
Date: Thu, Jun 26 2003 2:18AM
Subject: Re: Accessibility of complex HTML forms
← Previous message | No next message
On Thu, 26 Jun 2003, Gerard Corboz wrote:
> What I mean by a complex form is one that contains triggers or jumps. For
> example, the form might ask if the user has children. If the user answers
> yes then the user is expected to answer a large subset of questions related
> to their children. Alternatively if the user does not have children, they
> must skip to question xxx.
The obvious approach is precede the questions related to children by
something like
<div>If you have no children, please skip to
<a href="#q42">question 42</a>.</div>
> One way to handle the complex form example I described above is to use DHTML
> such that if a user answers yes to having children, the children related
> questions will dynamically appear.
That would make the functionality of the page depend on the settings of
the user's browser and its characteristics. It should at least be backed
up with equivalent server-side interaction, which means a lot of coding.
If the alternatives really depend on the data the user has filled in, then
such an arrangement could be practically necessary, but I would start from
the server-side processing - and consider adding faster client-side
operations only if feasible.
--
Jukka "Yucca" Korpela, http://www.cs.tut.fi/~jkorpela/
----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/