Link to issue number:

fixes #12751

Summary of the issue:

When using quick nav ("h" in browse mode) to navigate to a heading nested in an article with a description, the description is announced before the heading. For quicknav and for focus changes, the most inner element should always be announced first, working outwards to provide additional context.

Using the following example:

data:text/html,<p>Start</p><article aria-describedby="desc"><h4>Test Title</h4><p id="desc">Test description</p>

With "report articles" unchecked, speech should be:
Test title heading level 4

Instead it was:
Test description Test title heading level 4

With "report articles" checked, speech was:
Test title heading level 4 article test description

Description of how this pull request fixes the issue:

• Adds a test for quick nav reporting and focus changed reporting. The target element is a child node of a container that is usually spoken.
• Don't speak description for the container unless it is an aria-description.

Testing strategy:

System tests

Known issues with pull request:

Is aria-description doing the right thing in this case?

Change log entries:

New features
Changes
Bug fixes
For Developers

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