E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 7 (In chronological order)

From: Ryan E. Benson
Date: Tue, Oct 04 2011 10:33AM
Subject: doPostBack and Keyboard accessibility
No previous message | Next message →

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

From: Vincent Young
Date: Tue, Oct 04 2011 10:39AM
Subject: Re: doPostBack and Keyboard accessibility
← Previous message | Next message →

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 ADDRESS 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
>

From: Ryan E. Benson
Date: Tue, Oct 04 2011 10:51AM
Subject: Re: doPostBack and Keyboard accessibility
← Previous message | Next message →

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 ADDRESS 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 ADDRESS 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
>>

From: Vincent Young
Date: Tue, Oct 04 2011 11:06AM
Subject: Re: doPostBack and Keyboard accessibility
← Previous message | Next message →

Would need to see what the function is doing to not allow keyboard click,
but allow mouse click.

On Tue, Oct 4, 2011 at 9:50 AM, Ryan E. Benson < = EMAIL ADDRESS REMOVED = >wrote:

> 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 ADDRESS 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 ADDRESS 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
> >>

From: Ryan E. Benson
Date: Tue, Oct 04 2011 11:33AM
Subject: Re: doPostBack and Keyboard accessibility
← Previous message | Next message →

I would have to dig through the scripts to find it. Is there anything
particular to look for?

--
Ryan E. Benson



On Tue, Oct 4, 2011 at 1:04 PM, Vincent Young < = EMAIL ADDRESS REMOVED = > wrote:
> Would need to see what the function is doing to not allow keyboard click,
> but allow mouse click.
>
> On Tue, Oct 4, 2011 at 9:50 AM, Ryan E. Benson < = EMAIL ADDRESS REMOVED = >wrote:
>
>> 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 ADDRESS 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 ADDRESS 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
>> >>

From: Ryan Hemphill
Date: Tue, Oct 04 2011 1:45PM
Subject: Re: doPostBack and Keyboard accessibility
← Previous message | Next message →

The reason that JAWS is working pretty well is because it automatically
converts enter and space key events to click events. Of course, that isn't
doing you much good here. There are some ways to force the correct behavior
by binding a enter/space event listener that occurs on the element you are
dealing with and triggering a click event, but that may be overkill in your
case.

Let's assume that there is an easier way to resolve this. The first thing I
would try is the dumb things...

like tabindex="-1" .

Yeah, I know it sounds ridiculous. Give it a shot though - a lot of the
.Net apps that I have seen over the years do some really wacky stuff. I
would also recommend another stupid thing. Copy that link and put it into
its own html page and try it there. At least then you will know for certain
that it is the code itself that is the problem. Then, tinker a little and
you may find it isn't as much of a trial as you thought.

Good luck.




On Tue, Oct 4, 2011 at 1:30 PM, Ryan E. Benson < = EMAIL ADDRESS REMOVED = >wrote:

> I would have to dig through the scripts to find it. Is there anything
> particular to look for?
>
> --
> Ryan E. Benson
>
>
>
> On Tue, Oct 4, 2011 at 1:04 PM, Vincent Young < = EMAIL ADDRESS REMOVED = >
> wrote:
> > Would need to see what the function is doing to not allow keyboard click,
> > but allow mouse click.
> >
> > On Tue, Oct 4, 2011 at 9:50 AM, Ryan E. Benson < = EMAIL ADDRESS REMOVED =
> >wrote:
> >
> >> 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 ADDRESS 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 ADDRESS 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
> >> >>

From: Ryan E. Benson
Date: Tue, Oct 04 2011 3:51PM
Subject: Re: doPostBack and Keyboard accessibility
← Previous message | No next message

Thanks, I will suggest the tabindex trick.
--
Ryan E. Benson



On Tue, Oct 4, 2011 at 3:45 PM, Ryan Hemphill
< = EMAIL ADDRESS REMOVED = > wrote:
> The reason that JAWS is working pretty well is because it automatically
> converts enter and space key events to click events.  Of course, that isn't
> doing you much good here.  There are some ways to force the correct behavior
> by binding a enter/space event listener that occurs on the element you are
> dealing with and triggering a click event, but that may be overkill in your
> case.
>
> Let's assume that there is an easier way to resolve this.  The first thing I
> would try is the dumb things...
>
> like tabindex="-1" .
>
> Yeah, I know it sounds ridiculous.  Give it a shot though - a lot of the
> .Net apps that I have seen over the years do some really wacky stuff.  I
> would also recommend another stupid thing.  Copy that link and put it into
> its own html page and try it there.  At least then you will know for certain
> that it is the code itself that is the problem.  Then, tinker a little and
> you may find it isn't as much of a trial as you thought.
>
> Good luck.
>
>
>
>
> On Tue, Oct 4, 2011 at 1:30 PM, Ryan E. Benson < = EMAIL ADDRESS REMOVED = >wrote:
>
>> I would have to dig through the scripts to find it. Is there anything
>> particular to look for?
>>
>> --
>> Ryan E. Benson
>>
>>
>>
>> On Tue, Oct 4, 2011 at 1:04 PM, Vincent Young < = EMAIL ADDRESS REMOVED = >
>> wrote:
>> > Would need to see what the function is doing to not allow keyboard click,
>> > but allow mouse click.
>> >
>> > On Tue, Oct 4, 2011 at 9:50 AM, Ryan E. Benson < = EMAIL ADDRESS REMOVED =
>> >wrote:
>> >
>> >> 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 ADDRESS 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 ADDRESS 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
>> >> >>