Bug 222189 – AX: Repeated message to live region is not read out when alternating live regions are used

• Component: Accessibility
• Status: RESOLVED MOVED

**Overview:**

When using alternating aria-live regions to announce messages to users on screen reader (common approach for this purpose), a repeated announcement to a specific region is not read out.

**Steps to Reproduce:**

1. Open this Codepen: https://codepen.io/cw22/pen/JjbGbYb
2. Enable VoiceOver
3. Click Button 5, “Send Repeated Message to Alternating Live Region”
4. Notice that “Hello, world” is announced successfully
5. Click Button 5, “Send Repeated Message to Alternating Live Region”
6. Notice that “Hello, world” is announced successfully
7. Click Button 5, “Send Repeated Message to Alternating Live Region”
8. **Issue:** Notice that “Hello, world” is not announced successfully
9. Click Button 6, “Send Unique Message to Alternating Live Region”
10. Notice that “Hello #1” is announced successfully
11. Click Button 6, “Send Unique Message to Alternating Live Region”
12. Notice that “Hello #2” is announced successfully
13. Click Button 6, “Send Unique Message to Alternating Live Region”
14. Notice that “Hello #3” is announced successfully

**Actual Result:**

In Step 8, the live region text value goes from "" to "Hello, World!", so based on the implied aria-relevant value of "additions text", "Hello, World!" should be read out.

**Expected Result:**

In Step 8, "Hello, world" is never read out by VoiceOver.

**Build Date & Hardware**

MacBook Pro (16-inch, 2019)
MacOS Catalina 10.15.7 (19H512)
Safari Version 14.0.2 (15610.3.7.1.10, 15610)

**Additional Builds and Platforms:**

- Firefox Mac OS: FAIL (VoiceOver)
- Chrome Mac OS: FAIL (VoiceOver)
- Chrome Windows: SUCCESS (JAWS & NVDA)
- Firefox Windows: SUCCESS (JAWS & NVDA)

[Radar WebKit Bug Importer]

<rdar://problem/74532730>

Here is a screencast demonstrating this issue: https://www.dropbox.com/s/mguvbjuucq77fai/Webkit%20222189.mov?dl=0

[chris fleizach]

this ended up being a VoiceOver bug. I have moved to the right component and a fix will be provided in an update to macOS