WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: doPostBack and Keyboard accessibility

for

From: Ryan E. Benson
Date: Oct 4, 2011 10:51AM

Vincent,

I can use the app fine with JAWS (IE8 & J 11). When I am not using any
AT, just hitting tab and enter, I don't activate/follow any links. Ex
there is a table with a list of US states, each state is a link:
Using only a mouse: Clicking on a random state, I go to that state's info page.
Using only a keybard: Tabbing to that same state's link, press enter,
nothing happens.
Using JAWS: Navigate to the same state's link, press enter, I go to
that state's info page.


--
Ryan E. Benson



On Tue, Oct 4, 2011 at 12:37 PM, Vincent Young < <EMAIL REMOVED> > wrote:
> What version of jaws/browser are you using?  As long as there is text within
> the link, it should be announced.
>
> On Tue, Oct 4, 2011 at 9:31 AM, Ryan E. Benson < <EMAIL REMOVED> >wrote:
>
>> I am evaluating an ASP.Net app, and noticed all of the links are:
>> <a href="javascript:doPostBack(...)">Blah</a>
>>
>> While I don't know why it is done like this, I noticed when navigating
>> to a link using just the keyboard, the browser thinks it is a dead
>> link. However if I click or use JAWS on the link, it correctly goes to
>> the destination. Does anybody knows why this is? Is there an easy fix,
>> or does the app have to be redone?
>>
>> I am not the dev, and it is an internal app, so I can't give a link.
>>
>> --
>> Ryan E. Benson
>>