Why would I need to contact the web developer? The web page isn’t the problem. In fact, often times it’s my own web page. I’m the author. The page pulls up fine in Apple’s “Show Reader” mode and works with “Listen to Page” until it doesn’t (“Show Reader” always works). Sometimes “Listen to Page” will read a few sentences and then stop. The indicators for playback with skip appear specifically for “Listen to Page” but simply stop working. Occasionally it may cause a random audio stream to resume (ie, a previously listened to iTunes/Apple Music item).
Once “Listen to Page” stops working it will never work again until iPhone is rebooted. Then pages that worked and stopped or didn’t work at all will work again. After about 8 hours to a day it will stop working or act weird prior to stop working altogether.
This tells me that the iOS feature has a memory leak, timing/asynchronous race condition, or some other runtime execution error either by poor design, and or quality/testing.
It would be nice if Apple fixed this so that it would “just work”. Enough users have already complained about this.
The “work around” is already known (reboot iPhone) but it is impractical and a poor solution.