We’re working on improving the accessibility of a MKMapView that displays custom MKAnnotationView instances.
Our implementation is fully accessible with VoiceOver:
- The custom annotation views expose the correct accessibility information.
- Users can navigate between annotations using custom accessibility rotors.
- The overall VoiceOver experience works as expected.
However, we’re unable to make the custom MKAnnotationView instances accessible through Full Keyboard Access (FKA).
Despite configuring the annotation views as accessibility elements and experimenting with focus-related APIs, the annotations never become reachable through keyboard navigation. They appear to be skipped entirely by the FKA focus system.
Is there a supported way to make custom MKAnnotationView instances participate in Full Keyboard Access navigation?
If this scenario is currently unsupported, is there a recommended approach or any plans to expose public APIs that would allow developers to provide a keyboard-accessible experience for custom annotations in MKMapView?
Any guidance would be greatly appreciated.
