E-mail List Archives
Thread: Keyboard behavior with JAWS
Number of posts in this thread: 8 (In chronological order)
From: pratik roy
Date: Mon, Aug 24 2015 4:04AM
Subject: Keyboard behavior with JAWS
No previous message | Next message →
Recently, I faced a scenario where keyboard "Enter" key is not functioning
as expected and we have to press "Alt+Enter" in order to make it work.
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".
After that, I tried to do console.log() and saw that all key stock action
is working normally if I press any key with "Alt".
Now, my problem is, I am not sure whether that key combination is common
for screen reader user or not.
If anyone can share user experience for this kind of senario or a solution
of this problem, that will be GREAT Help.
Note: All keyboard keys are working fine with role="application" but I
don't want to make it a application region. :)
Thanks & Regards
PRATIK ROY
On Sat, Aug 22, 2015 at 11:30 PM, < = EMAIL ADDRESS REMOVED = >
wrote:
> Send WebAIM-Forum mailing list submissions to
> = EMAIL ADDRESS REMOVED =
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://list.webaim.org/mailman/listinfo/webaim-forum
> or, via email, send a message with subject or body 'help' to
> = EMAIL ADDRESS REMOVED =
>
> You can reach the person managing the list at
> = EMAIL ADDRESS REMOVED =
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WebAIM-Forum digest..."
>
> Today's Topics:
>
> 1. Re: WCAG Extensions (Kroon, Kurtis@FTB)
> 2. Re: WCAG Extensions (Chagnon | PubCom)
> 3. Re: Developing an Accessibility Team (Kline, Jeff)
> 4. a few recent links related to CAPTCHA (Jennifer Sutton)
> 5. Re: W3C-WAI Low Vision Accessibility Task Force - Seeking
> Participation (Chaals McCathie Nevile)
>
>
> ---------- Forwarded message ----------
> From: "Kroon, Kurtis@FTB" < = EMAIL ADDRESS REMOVED = >
> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> Cc:
> Date: Fri, 21 Aug 2015 18:33:47 +0000
> Subject: Re: [WebAIM] WCAG Extensions
>
From: Birkir R. Gunnarsson
Date: Mon, Aug 24 2015 4:15AM
Subject: Re: Keyboard behavior with JAWS
← Previous message | Next message →
Patrick
Jaws/NVDA in browse mode activate the element's onclick event when
enter is pressed with focus on that element (not the onKey events). In
application/forms mode howver, the onKey events are triggered when
user presses enter.
If you change the function trigger to be the onClick event, you should be fine.
On 8/24/15, pratik roy < = EMAIL ADDRESS REMOVED = > wrote:
> Recently, I faced a scenario where keyboard "Enter" key is not functioning
> as expected and we have to press "Alt+Enter" in order to make it work.
>
> 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".
>
> After that, I tried to do console.log() and saw that all key stock action
> is working normally if I press any key with "Alt".
>
> Now, my problem is, I am not sure whether that key combination is common
> for screen reader user or not.
>
> If anyone can share user experience for this kind of senario or a solution
> of this problem, that will be GREAT Help.
>
> Note: All keyboard keys are working fine with role="application" but I
> don't want to make it a application region. :)
>
> Thanks & Regards
> PRATIK ROY
>
> On Sat, Aug 22, 2015 at 11:30 PM, < = EMAIL ADDRESS REMOVED = >
> wrote:
>
>> Send WebAIM-Forum mailing list submissions to
>> = EMAIL ADDRESS REMOVED =
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://list.webaim.org/mailman/listinfo/webaim-forum
>> or, via email, send a message with subject or body 'help' to
>> = EMAIL ADDRESS REMOVED =
>>
>> You can reach the person managing the list at
>> = EMAIL ADDRESS REMOVED =
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of WebAIM-Forum digest..."
>>
>> Today's Topics:
>>
>> 1. Re: WCAG Extensions (Kroon, Kurtis@FTB)
>> 2. Re: WCAG Extensions (Chagnon | PubCom)
>> 3. Re: Developing an Accessibility Team (Kline, Jeff)
>> 4. a few recent links related to CAPTCHA (Jennifer Sutton)
>> 5. Re: W3C-WAI Low Vision Accessibility Task Force - Seeking
>> Participation (Chaals McCathie Nevile)
>>
>>
>> ---------- Forwarded message ----------
>> From: "Kroon, Kurtis@FTB" < = EMAIL ADDRESS REMOVED = >
>> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
>> Cc:
>> Date: Fri, 21 Aug 2015 18:33:47 +0000
>> Subject: Re: [WebAIM] WCAG Extensions
>>
From: Léonie Watson
Date: Mon, Aug 24 2015 6:19AM
Subject: Re: Keyboard behavior with JAWS
← Previous message | Next message →
> 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.
Léonie.
--
GDS Accessibility consultant +44.7921168551 @LeonieWatson
From: Jonathan Avila
Date: Mon, Aug 24 2015 7:46AM
Subject: Re: Keyboard behavior with JAWS
← Previous message | Next message →
> Jaws/NVDA in browse mode activate the element's onclick event when enter is pressed with focus on that element (not the onKey events). In application/forms mode howver, the onKey events are triggered when user presses enter.
Correct, and as an FYI to new people -- for other elements (not buttons and anchors) such as divs, adding an onlick and tabindex is not enough to provide keyboard access -- an author would need an onlick and keyboard event handlers to support both the click from a screen reader in browse mode and keyboard access.
Jonathan
--
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
= EMAIL ADDRESS REMOVED =
703-637-8957 (o)
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter
From: _mallory
Date: Mon, Aug 24 2015 1:59PM
Subject: Re: Keyboard behavior with JAWS
← Previous message | Next message →
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
From: pratik roy
Date: Wed, Aug 26 2015 11:26AM
Subject: Re: Keyboard behavior with JAWS
← Previous message | Next message →
Correct guess!
Our developers are using <div> with tabindex="0" and role="button", so you
can say these are fake buttons.
Thanks & Regards
PRATIK ROY
On Tue, Aug 25, 2015 at 11:30 PM, < = EMAIL ADDRESS REMOVED = >
wrote:
> Send WebAIM-Forum mailing list submissions to
> = EMAIL ADDRESS REMOVED =
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://list.webaim.org/mailman/listinfo/webaim-forum
> or, via email, send a message with subject or body 'help' to
> = EMAIL ADDRESS REMOVED =
>
> You can reach the person managing the list at
> = EMAIL ADDRESS REMOVED =
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WebAIM-Forum digest..."
>
> Today's Topics:
>
> 1. Question about tagged PDF (Ãcsvári Ãron)
> 2. Re: Question about tagged PDF (_mallory)
> 3. Re: Question about tagged PDF (Duff Johnson)
> 4. Re: Keyboard behavior with JAWS (_mallory)
> 5. making search input field accessible without a <label>
> (Angela French)
> 6. Re: making search input field accessible without a <label>
> (Léonie Watson)
> 7. Re: making search input field accessible without a <label>
> (Angela French)
> 8. Re: making search input field accessible without a <label>
> (Angela French)
> 9. Re: making search input field accessible without a <label>
> (Birkir R. Gunnarsson)
> 10. Re: Question about tagged PDF (_mallory)
> 11. Re: making search input field accessible without a <label>
> (Chaals McCathie Nevile)
> 12. Slack for accessibility policy geeks! (Jon Metz)
> 13. Re: Question about tagged PDF (Duff Johnson)
>
>
> ---------- Forwarded message ----------
> From: "Ãcsvári Ãron" < = EMAIL ADDRESS REMOVED = >
> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> Cc:
> Date: Mon, 24 Aug 2015 21:11:10 +0200
> Subject: [WebAIM] Question about tagged PDF
> Hello,
> I've created a web-application, and I generate pdf files. The biggest
> problem is that these files are not tagged. I know I can add tags with
> Adobe softvare, but it would be great if I can do it automaticaly. A year
> ago I've tried to TcPdf (it is a php-based Pdf generator), but it didn't
> support the tagging function. Is there any script which can generate an
> accessible pdf file from a html document?
> Thanks for your help!
> Regards,
> Aron
>
>
>
> ---------- Forwarded message ----------
> From: _mallory < = EMAIL ADDRESS REMOVED = >
> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> Cc:
> Date: Mon, 24 Aug 2015 21:12:20 +0200
> Subject: Re: [WebAIM] Question about tagged PDF
> On Mon, Aug 24, 2015 at 09:11:10PM +0200, Ãcsvári Ãron wrote:
> > Hello,
> > I've created a web-application, and I generate pdf files. The
> > biggest problem is that these files are not tagged. I know I can add
> > tags with Adobe softvare, but it would be great if I can do it
> > automaticaly.
>
> It would be great if I could tag on Linux, or anywhere I want, without
> specifically Adobe software. </offtopic>
>
>
>
>
> ---------- Forwarded message ----------
> From: Duff Johnson < = EMAIL ADDRESS REMOVED = >
> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> Cc:
> Date: Mon, 24 Aug 2015 15:25:16 -0400
> Subject: Re: [WebAIM] Question about tagged PDF
> > On Mon, Aug 24, 2015 at 09:11:10PM +0200, Ãcsvári Ãron wrote:
> >> Hello,
> >> I've created a web-application, and I generate pdf files. The
> >> biggest problem is that these files are not tagged. I know I can add
> >> tags with Adobe softvare, but it would be great if I can do it
> >> automaticaly.
> >
> > It would be great if I could tag on Linux, or anywhere I want, without
> > specifically Adobe software. </offtopic>
>
> PDF is an ISO standardized technology. You do not need "specifically Adobe
> software" to author "born tagged" PDF documents. There are a wide variety
> of non-Adobe options.
>
> - On the desktop, tools such as Apache Open Office (including for Linux).
> - Application developers can choose from a range of toolkits to produce
> tagged PDF documents.
>
> Duff.
>
>
> ---------- Forwarded message ----------
> From: _mallory < = EMAIL ADDRESS REMOVED = >
> To: = EMAIL ADDRESS REMOVED = , WebAIM Discussion List <
> = EMAIL ADDRESS 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
>
>
>
> ---------- Forwarded message ----------
> From: Angela French < = EMAIL ADDRESS REMOVED = >
> To: "WebAim Forum ( = EMAIL ADDRESS REMOVED = )" <
> = EMAIL ADDRESS REMOVED = >
> Cc:
> Date: Mon, 24 Aug 2015 20:49:55 +0000
> Subject: [WebAIM] making search input field accessible without a <label>
> I am trying to validate to WCAG 2.0 AA. I'm getting the error that I am
> missing an associated label on my search field.
>
> I have tried aria-label="search" and title="search" but neither one kept
> the error from being thrown. Are these not true solutions? Or must I
> have a <label> tag?
>
> Thanks
>
> Angela French
> Internet Specialist
> Washington State Board for Community and Technical Colleges
> 360-704-4316
> = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
> www.checkoutacollege.com<;http://www.checkoutacollege.com/>;
> www.sbctc.edu<;http://www.sbctc.edu/>;
>
>
>
>
> ---------- Forwarded message ----------
> From: "Léonie Watson" < = EMAIL ADDRESS REMOVED = >
> To: "'WebAIM Discussion List'" < = EMAIL ADDRESS REMOVED = >
> Cc:
> Date: Mon, 24 Aug 2015 22:11:30 +0100
> Subject: Re: [WebAIM] making search input field accessible without a
> <label>
> > From: WebAIM-Forum On Behalf Of Angela French
> > Sent: 24 August 2015 21:50
> > I am trying to validate to WCAG 2.0 AA. I'm getting the error that I am
> missing
> > an associated label on my search field.
> >
> > I have tried aria-label="search" and title="search" but neither one
> kept the
> > error from being thrown. Are these not true solutions? Or must I have
> a
> > <label> tag?
>
> These are both valid techniques. Technique ARIA14 describes how to use
> aria-label to provide a label [1], and technique H65 describes how to use
> the title attribute [2].
>
> The proviso (in both cases) being that the purpose of the field is
> apparent to sighted users based on context. The nearby search button being
> the visible cue in this situation.
>
> Sounds like it might be worth filing a bug with the vendors of the
> checking tool you're using though?
>
> HTH.
> Léonie.
> [1] http://www.w3.org/TR/WCAG20-TECHS/aria#ARIA14
> [2] http://www.w3.org/TR/WCAG20-TECHS/H65.html
>
>
>
>
> ---------- Forwarded message ----------
> From: Angela French < = EMAIL ADDRESS REMOVED = >
> To: " = EMAIL ADDRESS REMOVED = " < = EMAIL ADDRESS REMOVED = >, WebAIM
> Discussion List < = EMAIL ADDRESS REMOVED = >
> Cc:
> Date: Mon, 24 Aug 2015 21:23:28 +0000
> Subject: Re: [WebAIM] making search input field accessible without a
> <label>
> Actually, I didn't realize/forgot there were two search fields on the page
> and so I was seeing the error for the other one. The fact that there are
> two search fields is another issue.
>
>
From: _mallory
Date: Wed, Aug 26 2015 12:16PM
Subject: Re: Keyboard behavior with JAWS
← Previous message | Next message →
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 ADDRESS REMOVED = >
> > To: = EMAIL ADDRESS REMOVED = , WebAIM Discussion List <
> > = EMAIL ADDRESS 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
From: Bossley, Pete
Date: Wed, Aug 26 2015 2:47PM
Subject: Re: Keyboard behavior with JAWS
← Previous message | No next message