nvda
nvda copied to clipboard
In UIA-enabled Excel, the Element List dialog box(NVDA +F7) is not available.
Steps to reproduce:
Use UI Automation to access Microsoft Excel spreadsheet
- In NVDA's Advanced Settings panel:
- Enable "Use UI Automation to access Microsoft Excel spreadsheet controls when available";
- Try pressing
NVDA+F7
in Excel;
Actual behavior:
Excel Spell check is triggered
Expected behavior:
NVDA's element list dialog works as expected as per non-UIA in Excel (using the object model) The elements list allows to jump to graphics, formulas, notes, sheets, etc. It also allow to rename easily a sheet.
NVDA logs, crash dumps and other attachments:
None
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2022.4Alpha
Windows version:
Windows 10 21H2 (x64) build 19044.1889
Name and version of other software in use when reproducing the issue:
MSO365 (Version 2207 Build 16.0.15427.20182) 64-bit
Other information about your system:
None
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
Yes
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes
The elements list is typically tied to browse mode, and intended for documents. Excel documents are tabular and less linear and it isn't clear how browse mode / elements list would work here.
@feerrenrut wrote:
The elements list is typically tied to browse mode, and intended for documents. Excel documents are tabular and less linear and it isn't clear how browse mode / elements list would work here.
Actually, it's very clear how element list works in Excel and it provides very useful features in non-UIA mode. It allows to jump to graphics, formulas, notes, sheets, etc. It alsos allow to rename easily a sheet.
Element list is tied in browse mode in its implementation. But its features is to be able to jump to a specific element of a document. So from a UX point of view, it is not linked to browse mode.
In that case I'll label this as triaged. That would have been handy in the initial description. I'll edit it and mark this conversation as resolved.
Happy for a UIA implementation equivalent to the object model implementation to go ahead. It should be noted that using UIA within Excel is still an experimental feature.