Re: [Audacity-devel] Keyboard Preferences
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Leland <le...@au...> - 2013-10-03 15:08:25
|
On 10/3/2013 9:45 AM, David Bailes wrote: > On Wed, Oct 2, 2013 at 6:43 PM, Leland <le...@au... > <mailto:le...@au...>> wrote: > > On 10/2/2013 11:52 AM, David Bailes wrote: >> On Wed, Oct 2, 2013 at 5:47 PM, Leland <le...@au... >> <mailto:le...@au...>> wrote: >> >> On 10/2/2013 11:27 AM, David Bailes wrote: >> > HI Leland, >> > I've had a quick look at keyboard preferences using NVDA >> and Jaws. >> > There's a problem! They both think the item before the item >> with the >> > keyboard focus is the focus. (Microsoft's inspect tool >> indicates the >> > same problem). >> > There may be some more minor issues, but it would probably >> aid my >> > testing if this was fixed first, >> There is one thing I'd like to point out that I'd like your >> opinion on. >> >> In the "Name" and "Key" views, you'll only hear the actual >> menu item. >> You won't hear the submenu text. For instance, Instead of >> "Add New - >> Audio Track", you should hear "Audio Track". I thought it >> was a bit too >> chatty, but then it may be more confusing than it's worth. >> >> >> Yes, I did notice this. I think it's probably better to keep the >> sub menu name in, despite being a tad chatty: >> - some items from different sub menus have the same names >> - In the case of the Name view, if you're doing first character >> navigation, then it would be a little confusing, as the full >> string is used. > Made it the full label now. > > > thanks. However: > - in the tree view, when reading sub menu items it also reads the name > of the sub menu first, which I don't think it should do. > - in the key view, then name of the command is read first - I think it > should be the keystroke. > DOH! Of course it should be view specific. Refresh SVN and see if that's better. > The view by radio buttons. Since they're not in a group box, the view > by text is not read. So it would be clearer either to prefix the > accessibility names or the radio buttons with view by, or put the > radio buttons in a group box. The first is probably the better option > to conserve screen space. This one sounded simple as well, but NVDA doesn't say what I set with SetName(). I originally did have these guys in a group box and you're right, it does take up some real estate. Leland |