[wp-trac] [WordPress Trac] #47156: Consider a way to clear the wp.a11y.speak() live regions

[WordPress Trac]

#47156: Consider a way to clear the wp.a11y.speak() live regions
-------------------------------------+-------------------------------------
 Reporter:  afercia                  |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  5.3
Component:  Administration           |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-screenshots          |     Focuses:  accessibility,
  wpcampus-report                    |  javascript
-------------------------------------+-------------------------------------

Comment (by afercia):

 > Do screen readers offer an option to visually show (caption) what they
 are speaking?

 - VoiceOver shows spoken text by default.
 - NVDA has a "Speech viewer", but it's mainly meant for debugging and
 development
 - JAWS has a "Braille Viewer", which is a separate window that shows the
 spoken text and a "Speech History", basically a log meant for debugging
 purposes
 But I guess this isn't what you hoped for.

 > The issue of the live region being announced when it is not relevant is
 not one that WordPress has introduced; whether we visually hide the
 region, the issue would persist.

 It really depends on the implementation.
 Think at a ''visible'' live region that displays the number of search
 results (and it's also spoken). Why one would ever want to clear the
 visible message?

 Other visible live regions examples:
 https://inclusive-components.design/notifications/#liveregions101

 Also relevant for better understanding (though related to Microsoft
 PowerApps):
 https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/accessible-
 apps-live-regions
 > Position the live region in a logical position in the app, even if it
 isn't visible. Ensure that its contents are sensible in context with the
 elements before and after it. Users can access a live region anytime
 through regular navigation with a screen reader, not just when changes
 happen.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47156#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform