Link to issue number:

Fixes #14519
Fixup of #14303

Summary of the issue:

#14303 fixed a bug where landmarks and regions were not correctly reported in some cases.
However, #14303 failed to check/respect the config setting for reportLandmarks

Description of user facing changes

Landmarks are no longer reported incorrectly

Description of development approach

Check the config setting when reporting landmarks/regions in the case introduced by #14303

Testing strategy:

Manually tested the STR outlined in #14519

1. open preferences, Document formatting, and disable landmarks reporting;
2. go i.e. to issues page;
3. press 3 to find h3 Footer navigation.
4. Check whether or not "landmark" is reported

Known issues with pull request:

None

Change log entries:

None, fixes unreleased bug

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.