Is your feature request related to a problem? Please describe.
I propose that NVDA implement a quick navigation key for browse mode that allows to skip back and forward by articles. So far, this is done via the Enhanced ARIA add-on, which simply expands the landmark navigation to include articles. However, with many articles, the rest of the landmarks get drowned out easily, so it makes sense to use a separate keystroke specifically for articles.
Describe the solution you'd like
- Introduce a new keystroke in quick nav scripts to jump back and forward between article elements on a page. Alternatively, repurpose the keystroke previously used to navigate among Flash objects. Flash is dead, so it makes sense to repurpose this keystroke. Mozilla announced that Flash will be gone in Firefox 69, and object navigation, with the last of the NPAPI plugins gone, is then obsolete.
- When navigating with the virtual cursor, announce when the user enters a new article similar to what is being done for other landmarks.
Describe alternatives you've considered
Using the Enhanced ARIA add-on, which works on and off depending on the new NVDA add-on compatibility feature, making this unreliable, but the need for this kind of navigation is definitely there. Also, see above, using the same landmark navigation also for articles drowns other landmarks.
Additional context
Many websites like the new Twitter, AKA Mobile Twitter, or Threema Web, or the Mastodon or Pinafore Mastodon clients use articles to separate one message or tweet from one another. In addition, the Feed design pattern in WAI-ARIA 1.1 encourages to group entities by elements with the article role to separate them and make them navigable.
Is your feature request related to a problem? Please describe.
I propose that NVDA implement a quick navigation key for browse mode that allows to skip back and forward by articles. So far, this is done via the Enhanced ARIA add-on, which simply expands the landmark navigation to include articles. However, with many articles, the rest of the landmarks get drowned out easily, so it makes sense to use a separate keystroke specifically for articles.
Describe the solution you'd like
Describe alternatives you've considered
Using the Enhanced ARIA add-on, which works on and off depending on the new NVDA add-on compatibility feature, making this unreliable, but the need for this kind of navigation is definitely there. Also, see above, using the same landmark navigation also for articles drowns other landmarks.
Additional context
Many websites like the new Twitter, AKA Mobile Twitter, or Threema Web, or the Mastodon or Pinafore Mastodon clients use articles to separate one message or tweet from one another. In addition, the Feed design pattern in WAI-ARIA 1.1 encourages to group entities by elements with the article role to separate them and make them navigable.