Link to issue number:

Closes #11103

Summary of the issue:

When using quick keys to navigate articles on a web page, the article text/label should be announced first and then "article" should be announced after it in order to streamline the browsing process.

Description of how this pull request fixes the issue:

As discussed here - #12277 (review)
ROLE_ARTICLE is determined to be a PRESCAT_CONTAINER via getPresentationCategory if reportArticles is enabled. The condition in determining speakContentFirst, presCat != attrs.PRESCAT_CONTAINER has been replaced with presCat != attrs.PRESCAT_CONTAINER or role == controlTypes.ROLE_ARTICLE.

The logic to determine speakContentFirst has been moved to a helper function as it is documented that we need to reduce the complexity of getControlFieldSpeech.

Testing strategy:

Manually tried it out on web pages. Example websites can be found on this issue #9227

Unit testing seems unhelpful for the new helper function, however system tests for reading articles might be helpful if reviewers think so.

Known issues with pull request:

None

Change log entries:

Changes
- If article is enabled in the user preferences for document formatting, NVDA announces "article" after the content. (#11103)

Code Review Checklist:

• Pull Request description is up to date.
• Unit tests.
• System (end to end) tests.
• Manual testing.
• User Documentation.
• Change log entry.
• Context sensitive help for GUI changes.
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers