A11y issue in iOS app

[blazing dagger]

First off, the iOS app is very accessible. I was immediately impressed.

However, there is a major bug with the way speech feedback is delivered through VoiceOver.

With VO on, after submitting a message using the Send button, VO will start to announce ChatGPTs reply, but then immediately stop as focus is placed back on either the dimmed “Sent” button or the “Stop generating” button.

The announcement of this button’s label overrides the live reading of GPTs response.

I think this has to do with the updating of the button label, but could be perhaps a manual accessibilityFocus call that’s doing it. I might try disabling the Send button but not changing its label or changing it to a new “stop generating” button. I think the injection of this new View is impacting the live announcement of GPTs reply, which is the most important part and would make this an exceptional tool for VoiceOver users.

There is also a less severe problem where the accessibilityLabel for that Send button is not always updated accurately. Several times it was reading “Sent” or “Stop generating” when it was visible in the active “Send” state.

**Steps to reproduce:**
> 1. Turn on VoiceOver
2. Enter text into message field and hit Send
**Expected result:**
1. VoiceOver should announce ChatGPTs full reply. Focus should remain on the disabled Sent button throughout. 

**Actual result:**
> instead of announcing GPTs reply, the label of the dimmed Sent button or Stop generating button is read. VoiceOver users may hear a partial readout of the reply, but they will need to navigate back up the UI to read the full reply, which violates WCAG 2.1 AA on dynamic messaging. 

**Additional information**
> Browser: n/a
> OS:``` iOS 16.5
Bug reports not following the format may be removed.

[cold mountain]

Why do you want it to read it back to you?

They might make there own version like that someday