E-mail List Archives
Re: Submitting forms via javascript: Button vs. link vs. other?
From: Moore,Michael (DARS)
Date: Dec 4, 2009 8:00AM
- Next message: Don Mauck: "Re: Submitting forms via javascript: Button vs. link vs. other?"
- Previous message: deblist@suberic.net: "Re: FW: PDF is only partially accessible"
- Next message in Thread: Don Mauck: "Re: Submitting forms via javascript: Button vs. link vs. other?"
- Previous message in Thread: Jared Smith: "Re: Submitting forms via javascript: Button vs. link vs. other?"
- View all messages in this Thread
We have found usability problems caused for screen reader users when links are styled to look like buttons. The basic scenario goes like this.
JAWS user calls the help desk for assistance with a web application.
Help desk technician walks the person through the process in the application.
Everything goes fine until the technician tell the JAWS user, "Now click on the Process Transaction Button"
JAWS user whacks the B key, or attempts to bring up a list of buttons and JAWS says "no buttons found on page"
JAWS user tells help desk technician there is no Process Transaction button on the page.
Help desk technician says sure there is, it's right next to the Cancel button ...
Buttons really need to be buttons.
Mike Moore
- Next message: Don Mauck: "Re: Submitting forms via javascript: Button vs. link vs. other?"
- Previous message: deblist@suberic.net: "Re: FW: PDF is only partially accessible"
- Next message in Thread: Don Mauck: "Re: Submitting forms via javascript: Button vs. link vs. other?"
- Previous message in Thread: Jared Smith: "Re: Submitting forms via javascript: Button vs. link vs. other?"
- View all messages in this Thread