Open edenwaith opened 5 years ago
So we have accessibilityElements bound I believe as GetAccessibilityElements ().
However, you appear correct that
UINavigationItem is not a subclass of UIAccessibility in our bindings, so we aren't seeing those APIs.
Until we fix that, you should be able to use this work around (manual binding)
Thanks for the quick response! I'll try out these suggestions.
@chamons For accessibilityElements, UIView and any NSObject should implement the UIAccessibilityContainer protocol but does not.
While adding better accessibility/VoiceOver support for an app, I've noticed a couple of areas where Xamarin is missing some accessibility features in Xamarin for iOS (but are available in Swift).
accessibilityLabel
for the title in a navigation itemaccessibilityElements
Steps to Reproduce
accessibilityLabel Description: If one tries to add an
accessibilityLabel
to a navigation item'stitle
, it results in a compilation error.Example:
this.NavigationItem.Title.AccessibilityLabel = "Some Text";
accessibilityElements Description: The
accessibilityElements
property is missing for views. This is useful if one wants to put together a specific order that VoiceOver should read elements on a page.Example:
this.View.AccessibilityElements = [button1, button2, button3];
Expected Behavior
The expected behavior is that these accessibility properties should be available on Xamarin for iOS.
Actual Behavior
The actual behavior is that these properties are not available.
Environment
Build Logs
N/A
Example Project (If Possible)
N/A