Read aloud on a response: no highlight of the spoken text, no restart, and no way to pick where to start

The speaker button under a response in the Claude desktop app reads the response aloud, but it offers no control beyond play, pause and resume: 1. No highlight. Nothing in the text marks the sentence or word being spoken, so it's hard to follow along or find your place after looking away. 2. No start over. After pausing, the button's tooltip reads "Resume" and it continues from where it stopped. There's no way to go back to the beginning. 3. No choosing where to start. You can't click or select a paragraph and have reading start there. To hear one paragraph again, you have to listen to everything before it. The reporter's point of comparison is voice mode, where what's being said can be followed on screen and the listener can steer what gets read. The read-aloud button should work the same way. Impact: on long responses, read-aloud is hard to use for going back over one part, and it's a weaker accessibility tool for people who listen instead of reading. Reporter's screenshot (described here, not attached): a paused response with the speaker button focused and its tooltip showing "Resume". A red arrow drawn from a paragraph in the middle of the response to the speaker button marks where the reporter wanted reading to start.