Changes between Initial Version and Version 1 of Ticket #14045, comment 31
- Timestamp:
- 03/01/2013 02:39:16 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #14045, comment 31
initial v1 3 3 I am nervous about the verbosity but esmi's concise solution could help there. 4 4 5 I'm also unsure about the issue of using the arrow keys to influence 'movement' of an item. When using screen r aeders the arrow keys are normally associated with moving around within the page. I've just tested this functionality on NVDA on Firefox and I can't get the arrows to work without the override keystroke command. It would be a real pain for people to have to do that override every time they want to move an item - even though they probably won't be changing their menus every day.5 I'm also unsure about the issue of using the arrow keys to influence 'movement' of an item. When using screen readers the arrow keys are normally associated with moving around within the page. I've just tested this functionality on NVDA on Firefox and I can't get the arrows to work without the override keystroke command. It would be a real pain for people to have to do that override every time they want to move an item - even though they probably won't be changing their menus every day. 6 6 7 7 Could the necessary 'move' commands be included as text within the dropdown panel? That way, screen reader users could open the panel to access the options (which they might want to do anyway) and they would find the text links to influence the position. The challenge would be to find the right language to convey what we're trying to achieve here. Left and right aren't right here I feel. Knowing which way to move the item presupposes you have the 'sighted' model in your head.