nvda
nvda copied to clipboard
nvaccess
NVDA+O gesture in Excel does not appear in user guide
Steps to reproduce:
- Check "Use UI Automation to access Microsoft Excel spreadsheet controls when available" in the NVDA Advanced Settings panel.
- Try pressing NVDA+O in Excel.
Actual behavior:
Shows a browseable message Listing information about a cell's appearance such as outline and fill colors, rotation and size. However this gesture does not appear in the NVDA user guide.
Expected behavior:
Mention this gesture in the user guide.
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:
MS 365
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
btw, wondering if the gesture is available in non-UIA mode. Is this limited by UIA support?
Note this comment in #12210's description:
As some Excel-specific information on cells does not quite fit with standard NVDA concepts. A new Cell Appearance script (NVDA+o) has been added, which presents a browse mode document, listing these specific bits of information. This script may be changed or removed in future as it is possible to find this information out by looking in the Cell formatting dialog etc anyway, but for now it is there to demonstrate NVDa's ability to fetch this kind of information from UI Automation.
Before adding it to the user guide, it should be clarified if this script
- is only for demo purpose for developers/testers
- or if it is intended to be used by standard Excel users.
If 1, adding the information in the dev Guide or the script's docstring may be enough. If 2, the script should be added for legacy (not UIA) Excel usage and try to provide information as similar as possible with UIA mode.
