Morning,
I am trying to implement the accessibility (voice over) apis for a couple controls in my storyboard and
was wondering if anyone might have some pointers for determining which elements should be used for
these situations.
Elements:
1) UIPicker which selects a date value ( Is this an example of UIAccessibilityTraits: UIAccessibilityTraitAdjustable?)
2) TableViewCell which contains an Image and three text labels with values that are calculated (Not sure on this)
3) Three text labels that I would like to be grouped into one phrase (Not sure on this)
Thanks,
Kelly
After viewing the video sessions from 2012 to 2015 from WWDC, I was able to figure out how to set up a table cell and and group text labels into one phrase.
However, I am disappointed in the current support provided for the UIPicker. This just isn't acceptable. The accessibility API needs to be expanded for elements
that take input so that the user has a better experience. Specifically, it would be nice to have an API that summarizes the UIPicker and helps to describe how many columns have been placed side by side. If multiple columns are being used (ie, a date picker), it would also be nice if the user received the changing values periodically and cohesively across the columns.
I am also very disappointed with the accessibility API for the UITextField. More API is needed to guide the user to understand the usage of things like customized keyboards and scrolling to edit multiple textfields. When a textfield is used in an alertViewController, the voice over message is incoherent as it bounces from textfield value, to alert title, and skips the alert message entirely.
And finally, I am noticing that VoiceOver gets confused when layouts are composited with container views. It gives the dreaded hollow bouncing noise
as it doesn't find the parent elements and container elements smoothly.
The things I am describing above need investigation by experienced Apple Accessbility experts who can provide API where needed and facilitate
some document changes and sample code.
I would greatly appreciate a complete AccessibilityCatalog demo app before the next WWDC session that demonstrates how to implement accessibility features for all of the standard component items that the UICatalog demo app details today. (Examples are needed with code and with a Storyboard.)
I am committed to improving the quality of the accessibility features in my apps. To accomplish that, we need some help from Apple experts.