In the Search page, when a VoiceOver user types a query and then activates the Search button on the keyboard, he/she expects to be presented with the search results. In this case, the VoiceOver cursor should jump to the first result found and the keyboard should disappear. However, activation of the Search button does not seem to have any effect for a VoiceOver user and the VoiceOver cursor stays on the Search button. To a blind user this looks like nothing happened. The user might not even be aware at all that the search results are already there in another part of the screen.

Please see the attached screenshot of a situation after the user just activated (double tapped) the Search button, but the VoiceOver cursor remains on the Search button. (The screenshot is from an older version, but I verified this still happens even with the latest version from Git).