Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
[ID: 1223031]
Blink>Accessibility
Supplemental component tags only. Set main component first. [ID: 1222907]
[ID: 1223136]
Design doc to be reviewed. [ID: 1223032]
[ID: 1223087]
[ID: 1223134]
Milestone(s) impacted by this issue. [ID: 1223085]
[ID: 1223084]
[ID: 1223086]
[ID: 1223034]
Link to incidents in IRM as a result of this ticket. [ID: 1300460]
[ID: 1223088]
This field contains Gerrit urls of code changes that ‘fix’ a security bug (i.e., excluding logging/cleanup commits) and is used when a singular fix cannot be uniquely identified from the existing “Code Changes” field. The change can be in the chromium repo or any other third_party repo. [ID: 1358989]
Blink
[ID: 1253656]
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Estimated effort
Description
I’m Riya Singla, Quality Engineering Manager at PayGlocal, a cross-border payments platform. I’m reaching out to report a critical issue we’ve identified in our production systems, linked to the behavior of Google Read Aloud.
While investigating a recurring problem affecting our payment flow, we discovered that one of our backend APIs was being unexpectedly triggered a second time, shortly after the user initiated a payment. This was causing certain transactions to fail.
Upon analyzing the request patterns and User-Agent headers, we found that the second request was coming from Google Read Aloud. It appears that Read Aloud is making a separate automated request to the page/API, which occurs after user interaction, and this secondary request is unintentionally disrupting critical backend logic.
Impact:
* Failed transactions
* Broken payment flows for end users
* Increased operational overhead (refunds, support, error handling)
* Potential exposure for any system that depends on timing-sensitive or stateful requests
This behavior, while likely intended to support accessibility, has unintended side effects that can break key user journeys — especially in financial or transactional environments where consistency and timing are critical.
We believe this issue could be affecting many other platforms without their awareness, especially those handling sensitive operations on web pages where Read Aloud is active.
We kindly request your team to:
* Review how and when Read Aloud makes additional network requests.
* Consider mechanisms for developers to detect or opt-out of such automated behavior.
* Provide clearer documentation around the impact of Read Aloud on interactive and transactional pages.
We’d be happy to share more context or technical details to assist with investigation. Thank you for your attention — we truly value the accessibility goals of Read Aloud and hope this feedback helps improve its integration with critical user flows.
Best Regards,
Riya Singla
Quality Engineering Manager
Payglocal Technologies