> Using non-native controls, for example, has accessibility consequences
Correct me if I'm wrong, but don't people with serious accessibility needs typically prefer web because there are way more tools optimized for web than for native?
Not necessarily. macOS and iOS have multiple accommodations for users with accessibility needs, from dynamic type to UI element voiceover plus pretty decent speech-to-text recognition and haptic feedback. Developers that want to take the time can build apps that can be effectively used by users with visual and/or auditory deficits.
Correct me if I'm wrong, but don't people with serious accessibility needs typically prefer web because there are way more tools optimized for web than for native?