Is your feature request related to a problem? Please describe.

Users interact with devices at different speeds, especially if they have mobility or cognitive disabilities.
There are many features which are blocked by the concept of waiting a user configured delay to determine if Windows/NVDA is idle.

Use-cases:

• aria-live="polite": Any region which receives updates that are important for the user to receive, but not so rapid as to be annoying, should receive this attribute. The screen reader will speak changes whenever the user is idle. ARIA live regions - Accessibility | MDN 
  • aria-live="polite" does not act as W3 Reports in Tutorials #8908
  • Aria-live "polite" not reading at all #12464
• Notifications that are important but not urgent. EG Windows notifications for background applications.
  • In this case a new speech API method "lowUrgencyNotification" could additionally play an earcon so the user is aware of the notification pending announcement.
  • NVDA update check announcements: Less intrusive automatic update notifications #2257
• Delayed reporting of phonetic character descriptions:
  • added support for delayed phonetic character descriptions #13550
  • NVDA add automatically speak character description function when cursor move #13509
  • Default time delay for Delayed descriptions for characters on cursor movement is too long #13967
• Speaking command keys
  • i.e. making sure it's not interrupted by other speech: Spoken key commands are interrupted by resulting events of the key command #13031
  • Perhaps this could be queued as NEXT not LATER

Describe the solution you'd like

An option in General/Keyboard preferences to determine how long to wait before NVDA is considered idle.
Idle: No user input / all normal speech has finished for a (configurable) period of time.

A new speech priority "LATER" to announce speech when NVDA is idle.

Existing speech levels:

• NORMAL: Indicates that a speech sequence should have normal priority.
• NEXT: Indicates that a speech sequence should be spoken after the next utterance of lower priority is complete.
• NOW: Indicates that a speech sequence is very important and should be spoken right now, interrupting low priority speech. After it is spoken, interrupted speech will resume. Note that this does not interrupt previously queued speech at the same priority.
  • TODO: Interrupt speech for assertive live regions #6335

Describe alternatives you've considered

Handling this issue on a PR/issue level basis, rather than a generic fix.

Additional context