search

jasonzhyan / google-axs-chrome

Automatically exported from code.google.com/p/google-axs-chrome
0 stars 0 forks source link

Drop-down menu #28

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Navigate to a drop-down menu in a form (HTML SELECT)
2. ChromeVox reads (x of y) 
3. Navigate to each value in the box.

What is the expected output? What do you see instead?

The expected outcome would be that x was the right position in the menu list 
(whether hearing this is in fact necessary or not), however, the position 
appears to be out by one - possibly because of the "search within" text at the 
top of the list.

Secondly, I would hope to hear the options in the list - however, going up and 
down the list I do not hear any of the other options.

What version of the product are you using? On what operating system?

I'm using MAC + Snow Leopard.  ChromeVox 1.15.1 + Chrome 16.0.899.0. 

Please provide any additional information below.

Original issue reported on code.google.com by alistair...@gmail.com on 10 Oct 2011 at 10:21

GoogleCodeExporter commented 8 years ago 
Additional info:  

This issue happens on this page - 
http://code.google.com/p/google-axs-chrome/issues/detail?id=28 when looking at 
the Open issues drop-down.

Possibly, the reason for chromevox being out when it reads out this drop-down 
is that a disabled option has been used to add "search within".  The code 
relating to this issue sits in the dom_util.js file - but has been copied below.

info = info + ' ' + (targetNode.selectedIndex + 1) + ' of ' +
        targetNode.options.length;

The suggested fix, for at least the x of y issue would be to have the 
targetNode.selectedIndex (if needed) and targetNode.options take into account 
options which have been disabled - removing them from the count.

Original comment by alistair...@gmail.com on 10 Oct 2011 at 2:44

GoogleCodeExporter commented 8 years ago 
I disagree with the premise of this bug. The first menu item option actually 
gets focus (you can up arrow and it gains selection) even though it is dimmed, 
so it is technically still contributing to the total number of items in the 
drop down.

From a userperspective, count announcement is useful because a user can 
anticipate how many items they'll have to slog through when arrowing; (i.e. a 
hundreddown arrow presses might make one hold the down arrow key or up arrow to 
the end if the menu wraps, etc).

Original comment by dts...@google.com on 11 Nov 2011 at 10:29

GoogleCodeExporter commented 8 years ago 
Unfortunately, this is still broken/not working in ChromeVox 1.16.0

Original comment by KevinCha...@gmail.com on 24 Nov 2011 at 12:06