Context: Modifications that I have done time ago for myself when working with Excel sheets.

Link to issue number:

None

Summary of the issue:

In Excel, when applying formatting to cells, nothing is reported. Instead, in Word, toggling bold, italic or underline is reported.

Description of user facing changes

When using Excel shortcuts to toggle the format of a full cell in Excel, the result is now reported. The following toggle are supported:

• bold: control+b or control+shift+2
• italic: control+I or control+shift+3
• underline: control+U or control+shift+4
• strikethrough: control+shift+5 (Note: did not find any other shortcut for it)

Description of development approach

• As done for Word text, use object model to look at the properties of the cell after the shortcut is executed.
• Copied the polling function of Word's code to check for value changes polling the object model. (I had initially thought that it was not required, but testing on another system, I have found that it was required)
• Implement the scripts on the whole worksheet so that the scripts work either on single cell or on multi-cell selections. Taking advantage that both excelCellObject and excelRangeObject have a font attribute.

Testing strategy:

Tested all listed shortcuts on single cell and on multi-cell selection.

Tested on the following versions:

• Microsoft® Excel® 2016 (16.0.5387.1000) MSO (16.0.5366.1000) 32 bits
• Microsoft® Excel® 2016 MSO (Version 2304 Build 16.0.16327.20200) 32 bits

Known issues with pull request:

• This PR does not handle the case of formatting shortcuts when editing a cell.
• On the contrary to Word's code, I have not implemented a check that Excel Object Model was available, since it does not seem to be implemented elsewhere in Excel's code. I do not know if there is a use case for it but I think that it would not be supported by existing code of NVDA anyway.

Change log entries:

New features
The result of usual formatting shortcuts on Excel cells will now be reported.

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.