[wp-trac] [WordPress Trac] #36289: WP Speak assertive message and Firefox + NVDA bug

[WordPress Trac]

#36289: WP Speak assertive message and Firefox + NVDA bug
----------------------------+----------------------------------------
 Reporter:  afercia         |       Owner:
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:  accessibility, javascript
----------------------------+----------------------------------------

Comment (by Cheffheid):

 Yeah, I agree. And it does look like a Firefox issue, triggering an alert
 for NVDA to announce. It may consider the overflow change as "making the
 element visible" and trigger the alert, as described on Example 4:
 https://developer.mozilla.org/en-
 US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_alert_role.

 But I do think we should handle this as a browser support issue and
 implement the workaround as best we can. Simply because at this point
 there's going to be two outcomes:

 1. It's not intentional Firefox behaviour, which means we'll need to wait
 for it to be fixed  ''and'' for people to adopt that version. I don't know
 exactly how Mozilla decides what fixes go where, but even if a fix were to
 land in 49 or 50 we'd be waiting for the end of Q3/early Q4 for it to be
 fixed. And potentially looking at Q1 of next year for full adoption. All
 the while we've got a bunch of irritating noise when using the Customizer.

 2. It's intentional, in which case it will never get fixed and we'll need
 to implement a workaround anyway.

 Let's assume it's not intentional for now, which means we'll definitely
 want to do that bug report on Bugzilla and get a definitive answer that
 Example 4 is actually what's happening here.

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