But since this only effect default actions in IE (i.e. not event 
handlers), and it's easy to figure those out and call them though JS 
manually, this is a viable workaround.
All known access key methods we currently use seem to work 
consistently across all browsers now, yay!

Yes, the default behavior in IE is to only focus the element with the 
access key, and this is only possible with visible elements of course.
Furthermore browsers must not allow to trigger default actions of 
elements through manually created events for security reasons (click 
jacking etc.). Chrome still allows that though, so we had to catch that.

This is a limitation of several browsers (e.g. IE) and, AFAICT from my 
research, can not be worked around.

FWIW, these accesskeys can't be accessed via non-javascript either.   
So this has nothing to do with our javascript code.

Changes have been made in CVS for this ticket:

http://cvs.horde.org/diff.php/horde/js/accesskeys.js?rt=horde&r1=1.6.2.3&r2=1.6.2.4&ty=u
http://cvs.horde.org/diff.php/horde/js/src/accesskeys.js?rt=horde&r1=1.7.2.3&r2=1.7.2.4&ty=u

Initially playing around with this, I can't figure out a way to make 
this work (since the accesskeys are hidden via CSS, not javascript).   
Since I don't use accesskeys personally, this is not at the top of my 
list.

This is a showstopper for releasing further Horde 3.3.x versions.

Follow-up from ticket #7866.



Access keys on hidden elements like IMP sub menus don't work with the 
new JS code.