Link to issue number:

Fixes #10271 (last part)
Also could be considered a partial fix of #3293.

Summary of the issue:

In Word / Outlook, nothing is reported when using the switch case command (shift+f3 in both, control+shift+a in Outlook only). Since it is a toggle/cycle command, the user needs to have the result to be reported.

Description of user facing changes

Using the switch case formatting command in Word or Outlook now reports its result, i.e. the type of case in which the selection has been formatted.

When possible, the message being reported illustrates its own casing, as in Word menus, e.g. "lower case", "UPPERCASE", "Each Word Capitalized"; this may be useful in braille. Exception, for "Mixed case", I have not done something such as "mIxEd cAsE" because it is not correctly understandable through speech.

Description of development approach

• Used Word object model as for other Word formatting scripts.
• Introduced a delay (set empirically), since the property retrieved from the object model transitions through other values (no case or lower case) before reaching its definitive value.
• Bind gestures according to the ones existing in Word and Outlook.

Note: shift+f3 performs case switch both in Word and Outlook, whereas control+shift+A does it only in Outlook. See "Notes about various capitalization shortcuts" in #17197 for more details.

Testing strategy:

Manual test:
Test shift+f3 and control+shift+A in the following conditions:

• In Word and in Outlook
• With or without UIA
• With various types of selection: no selection, piece of word selected, word selected, few words selected, sentence selected, all selected, only digits or punctuation selected, mix of letters and digits selected (e.g. "a0b1" between other words).

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