Re: [orca-list] some minor issues with orca in gnome 3.14

["B. Henry" <burt1iband gmail com>]

Has a bug been filed on this?
There are other issues that are probably gnome related, but this one is especially annoying. 
Not so much that I need more concrete feedback as to when I change a key binding, but the shortcuts interface 
is where I'd go to learn the preset 
bindings, honestly don't even know where else to look for them for sure. I suspect the F123 manual for 
example has them, and surely some where on the 
gnome site there's a list as well, but this is rather bad not to have easily accessible locally, especially 
because it should be very easily fixable I 
think.
I'll make a list of the others as they occur. Dropbox applet comes to mind, just says unknown. The unity 
indic ator for this works, as does the mate 
applet, more or less. I am not using dropbox3 BTW, as the first few releases for Linux were not working worth 
a damn, think the panel applet, icon, 
whatever you want to call it did not appear for anyone, memory leaks were crazy, and the thing took up like 
100MB extra compared with 2.10 just to break 
stuff...lol
So, while most things do indeed "work", and in general the interface is fine as far as responsiveness goes, I 
am no longer going to say that gnome3 is 
probably the most all around accessible interface. Mate has some occasional lags, and its own 
non-show-stopping accessibility bugs, but the two desktops 
are certainly in the same league as far as over all usability with Orca goes in my opinion. 
Mate does announce work areas by name or number, so does XFCE for that matter. Gnome does not for me. Pretty 
poor, again this is not so much for obvious 
reasons, but because of the way program windows are placed by default in gnome 3.12 and 3.14 anyway. It is 
often not clear if I am in the work space I 
navigated to, or if focus jumped back up to where I was before when I moved to the new work space. It seems 
that one navigates between all open windows 
with alt tab combination, not just windows on a specific work space as default behavior.
   Is there a specific bugtracker section for accessibility related bugs in gnome shell, or are they mixed in 
with other bugs?
I would assume that most of the issues I have encountered have been reported, and although I've not spent 
much time using gnome 3.x of any release I 
think most of what I am seeing has been around at least since 3.12. 
Thanks,
   

-- 
     B.H.
   Registerd Linux User 521886


  Fernando Botelho wrote:
Thu, Jan 22, 2015 at 10:09:57AM -0200

> Hi Burt, this is actually a Gnome issue.
>
> Thanks for reporting it,
>
> Fernando
>
> On 01/21/2015 10:15 PM, B. Henry wrote:
> > This may be an F123 specific issue, but using gnome 3.14 I get no indication if a keyboard shortcut is 
> > enabled, they always say disabled.
> > When editing I do hear the shortcut announced, but by name only when I enter the new combination. In most 
> > cases keybindings are not announced at all in
> > the custom section, but some are read when exploring other tabs.
> > I won't ask about any other issues here until I find out more about how much of F123 is non standard re 
> > gnome configuration.