Skip to main content

Search and Top Navigation

#9918 closed bug (patcheswelcome)

Opened March 17, 2014 06:19PM UTC

Closed March 31, 2014 09:49PM UTC

Autocomplete above focusable list moves focus from autocomplete results to list (JAWS)

Reported by: norabora Owned by: dylanb
Priority: minor Milestone: none
Component: ui.autocomplete Version: 1.10.4
Keywords: Cc:
Blocked by: Blocking:

My application has an autocomplete input right above a list with focusable list items. When running JAWS 15 and testing in FF 26 on Windows 7, if I perform a search and start using the down arrow to navigate the results, after correctly going through 2-3 items in the autocomplete list, focus will move to the other list with no indication to JAWS that focus has moved. This issue is not seen when running NVDA or without JAWS so there could be something JAWS is doing wrong but there should be some indication from the autocomplete list that focus has moved out of it.

Attachments (0)
Change History (9)

Changed March 18, 2014 01:00PM UTC by tj.vantoll comment:1

owner: → norabora
status: newpending

Hi norabora,

Can you confirm that this behavior still occurs with the latest build of the library and this reduced test case:

Changed March 18, 2014 04:51PM UTC by norabora comment:2

status: pendingnew

Replying to [comment:1 tj.vantoll]:

Hi norabora, Can you confirm that this behavior still occurs with the latest build of the library and this reduced test case:

No, the issue happens only when there's a focusable list below the autocomplete input box in the DOM. With the list added back and simplified,, yes I still see the issue.

Changed March 18, 2014 08:00PM UTC by tj.vantoll comment:3

owner: noraboradylanb
status: newassigned

Changed March 28, 2014 06:44PM UTC by dylanb comment:4

This is a JAWS 15 specific problem. It does not occur in JAWS 14. I will report the problem to Freedom Scientific.

Changed March 28, 2014 06:47PM UTC by norabora comment:5

If you file a bug with them, can you put the ticket number/link here so that I can track it?

Changed March 31, 2014 07:24PM UTC by dylanb comment:6

Norabora - Can you tell me whether you were using IE or Firefox when you produced this problem? We are able to reproduce this problem only in FF with JAWS 15.

Changed March 31, 2014 07:52PM UTC by norabora comment:7


Changed March 31, 2014 09:35PM UTC by dylanb comment:8

Yeah, JAWS does not work well with Firefox, please use JAWS with IE and NVDA with Firefox.

Changed March 31, 2014 09:49PM UTC by scottgonzalez comment:9

resolution: → patcheswelcome
status: assignedclosed

Yeah, those are the combinations we try to support, along with VoiceOver for Safari/iOS. If there's a workaround that isn't really hacky or large, we can consider it.