WebAIM - Web Accessibility In Mind

E-mail List Archives

RE: Buttons vs Submit WAS: Drop down list, css, and xhtml

for

From: smithj7
Date: Apr 21, 2006 5:40PM

With the population that I serve the button element is a BAD idea. It
has caused problems for some of my users (work for Florida Blind
Services). So I learned to use input - submit.

While I still am a "baby when it comes to accessible coding using CSS,
xhtml, xml", I am "blessed" with a group of people that use assistive
technology for persons who are blind that let me know when something
doesn't work.

Problems may related to two things:

1. Lack of access for persons with disabilities to get the same ability
to upgrade accessibility technology
2. Learning curve of users

Lack of access:

For example, speech access companies have been doing a good job at
trying to keep up with the newer technology, but often my users cannot
afford to keep up with updating their speech technology. Unfortunately,
while sighted folks can just update their browers for free, many of my
users who have access technology on home computers or work for small
businesses would have to pay big bucks to get the same access to the
state of the art speech technology. But when it comes to the button
element it isn't just cost; one person who told me not to use the button
element is actually using the Beta version of JAWS. While he doesn't
understand html, he was a programmer before becoming our MIS manager.
He is a high end JAWS user. He has the best technology.

Learning curve:

We also must keep in mind the learning curve of a person using access
technology. The way a person who is blind that uses such technology, is
totally different than a sighted person does. They have learned to
navigate using stuff like "input". Agencies like ours don't keep
upgrading training. When we - tech folks - change the rules, it
inadvertently IMH because a usability issue because the folks won't
trained to adapt to the new technological changes.