soffice: Implement methods for status bar announcement

[michaelweghorn]

Link to issue number:

Fixes #11698

Summary of the issue:

Announcement of the status bar in LibreOffice (e.g. triggered by NVDA+End) didn't work because the default implementations do not work for the LibreOffice case.

Description of user facing changes

Announcement of the status bar (e.g. triggered
by NVDA+End) works for LibreOffice.

Description of development approach

Override the default app module implementation to retrieve the status bar and announce its text in the LibreOffice app module, since the default implementations are not sufficient for the LibreOffice case:

• To retrieve the status bar object, locate the descendant with the corresponding role, but only descend into children of role ROOTPANE and WINDOW for performance reasons.

• To generate text from the status bar object, retrieve the text of each status bar child using the IAccessibleText interface. (The default implementation in api.py only uses the object names and values, which are both empty.)

Testing strategy:

1. start NVDA
2. start LibreOffice Writer
3. Press NVDA+End key to trigger announcement of status line 4) check that the visible content of the status bar is announced
   (e.g. something like "Page 1 of 1 5 words, 20 characters Default
   Page Style English (United States) {en-US} 80%")
4. repeat the above steps, but use LibreOffice Calc, Draw and Impress
   instead of Writer (in step 2)

Known issues with pull request:

none

Change log entries:

Changes
Announcement of the status bar (e.g. triggered by NVDA+End) works for LibreOffice. (#11698)

Code Review Checklist:

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

[seanbudd]

Thanks @michaelweghorn, the approach looks good, just need type hints added to each function

[michaelweghorn]

Thanks @michaelweghorn, the approach looks good, just need type hints added to each function

Thanks @seanbudd for the review. I've updated the PR as suggested.

[seanbudd]

thanks @michaelweghorn