Link to issue number:

fixes #13380

Background

Improved support for reporting details summary: #13106

Summary of the issue:

Web authors would like to start using aria-details, however:

• It is not enabled by default.
• There is no default gesture to fetch the details.

information about longdesc

• The longdesc attribute is only valid on an img element.
• longdesc does not seem to be exposed in Chrome / edge, it continues to work in Firefox.
• longdesc is deprecated, mdn advises not using it and transitioning away from current uses.
• longdesc has an incompatible UX with aria details. The longdesc attribute contains a URL, the browser exposes an action, when triggered the URL is opened in a new tab. Aria details is expected to be read without leaving the page.

Anyone who still relies on longdesc support can assign an alternative gesture.

Description of how this pull request fixes the issue:

• NVDA+d now runs aria-details summary script
• report has details by default

Testing strategy:

Using long-desc vs aria-details full page codepen or the same sample editor link:

• Navigate with down arrow in browse mode to the image with alt text "taco tuesday"
• In Chrome / Edge note "long description" is not announced, but is in Firefox.
• Navigate with down arrow / control + right arrow, to the marked text that "has details"
• Press NVDA+d to report details summary, "successful test" reported (in Chrome / edge, not firefox)

Other tests:

• Via Input gestures, browse mode category, Activate long description has no gesture, and can be assigned one.

Known issues with pull request:

Summary of aria-details can not be reported in firefox. This will be addressed separately:

Change log entries:

Changes

- Activate long description no longer has a default gesture assigned.
- Report details summary now has a default gesture, ``NVDA+d``. (#13380)

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