WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Keyboard behavior with JAWS

for

From: _mallory
Date: Aug 26, 2015 12:16PM

On Wed, Aug 26, 2015 at 10:56:41PM +0530, pratik roy wrote:
> Correct guess!
>
> Our developers are using <div> with tabindex="0" and role="button", so you
> can say these are fake buttons.

Okay, but so you're listening to both events then?

click, keyup? (I use either keyup or keydown, and avoid keypress
like the plague)

_mallory
>
> Thanks & Regards
> PRATIK ROY

> > ---------- Forwarded message ----------
> > From: _mallory < <EMAIL REMOVED> >
> > To: <EMAIL REMOVED> , WebAIM Discussion List <
> > <EMAIL REMOVED> >
> > Cc:
> > Date: Mon, 24 Aug 2015 21:59:53 +0200
> > Subject: Re: [WebAIM] Keyboard behavior with JAWS
> > On Mon, Aug 24, 2015 at 01:19:41PM +0100, Léonie Watson wrote:
> > > > From: WebAIM-Forum On Behalf Of pratik roy
> > > > Sent: 24 August 2015 11:05
> > > >
> > > > In our webpage, we have some button elements and onclick of those
> > > > buttons, it is performing some action. We have used onkeypress event
> > with
> > > > keycode="13" (Enter) to handle the functionality. But when I hit Enter
> > it is
> > > > not even firing the event but working absolutely normal with
> > "Alt+Enter".
> > >
> > > You don't need to use the keypress handler. When the <button> element is
> > used with a click handler, the browser automatically handles keyboard
> > interaction for you.
> > >
> >
> > Unless they're fake buttons... are they?
> > _mallory