Problems with the Visual Basic for Applications editor in Excel and NVDA
An user has written us to report several problems with the Visual
Basic for Applications (VBA) editor in Excel with NVDA (same with
Narrator though). We are able to reproduce all of them.
1. Event selection: We are unable to insert events into the thisWorkbook module. We haven't found an accessible way of accessing the dropdown that should allow to visually select, for example, the open event and insert it into that module.
2. Control insertion in userForms: The same happens for the
UserForm's controls toolbox that is shown when working with an
userForm (Insert>userForm). We haven't found a way to access it
with the keyboard, we have even tried hiding it and showing it
again (Alt+V, X for Excel configured in english, Alt+V, H for
Spanish). If we try to use object navigation to move keyboard
focus into it (it appears as a top-level window just under
Desktop), the only thing the screen reader reports within that
a "Controls" tab. Tab, arrows and other common keys and keystrokes
seem to do nothing.
3. Control selection and customization in userForms: Even if we
have an already-built userForm, we are unable to navigate by any
of the inserted controls either.We haven't found an accessible way
to have the different inserted controls reported.
4. Outside of the VBA editor, in the workbook itself, we haven't found an accesible way to insert a button to run a macro. If I use NVDA's mouse simulation I may be able to get it but not on the cell or cell range where it would be supposed to be located.
Have you experienced this issues and do you have any tricks to
Thanks in advance. Regards.
Iván Novegil Cancelas
toggle quoted message Show quoted text
I’m glad somebody is bringing some attention to this issue. The accessibility of the VBA editor has been broken for a long time. While I suspect most of what needs to be fixed falls under Microsoft’s umbrella, maybe somebody can do something cool with an NVDA add-on or something to bridge the gap. Good luck!
On Nov 18, 2022, at 9:47 AM, Iván Novegil via groups.io <ivan.novegil@...> wrote:
|1 - 2 of 2|