Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to report the document layout in Microsoft Word #17324

Draft
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

nvdaes
Copy link
Contributor

@nvdaes nvdaes commented Oct 24, 2024

Link to issue number:

Fixes issue #15088

Summary of the issue:

Knowing the document layout in Microsoft Word may be important, for example, to figure outwhy a table is not read properly when navigating with NVDA, and in other situations.

Description of user facing changes

When using the report title command in Microsoft Word, if the document layout can be determined, it Will be added to the title.
When Microsoft Word is active, in the input gestures dialog, the description of this command will be presented indicating that it works in Word, in contrast to the global commands title.

Description of development approach

In the WinWord app module, a script has been created, using api.getStatusBar() to search for the status bar. If it can be found, and one of the bar status children has the PRESSED state, its name Will be added to the title, assuming that it correspond to the document layout.

Testing strategy:

Tested manually, in Word documents, with the ribbon active and inactive, and with a dialog opened to check that the title without the document layout is reported when the status bar is not found.

Known issues with pull request:

None.

Code Review Checklist:

  • Documentation:
    • Change log entry
    • User Documentation
    • Developer / Technical Documentation
    • Context sensitive help for GUI changes
  • Testing:
    • Unit tests
    • System (end to end) tests
    • Manual testing
  • UX of all users considered:
    • Speech
    • Braille
    • Low Vision
    • Different web browsers
    • Localization in other languages / culture than English
  • API is compatible with existing add-ons.
  • Security precautions taken.

@coderabbitai summary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant