4 ms·
I'm really big on accessibility support. The demographic that I Serve tends to have a statistically higher level of challenges than your average audience. One
by ChrisMarshallNY 3y ago
I'm really big on accessibility support. The demographic that I Serve tends to have a statistically higher level of challenges than your average audience.
One trick that I'm doing, in the app that I'm working on now, is that I have a "long-press help" feature.
I have a long-press gesture recognizer attached to the main view, and, when a long-press event is received, I find the shallowest view under that press, and examine it for the accessibility label and hint support. If it does not have any, I back up to its parent, etc.
If I find a label and hint, I use them to populate a popover, pointing at the target, and trigger a haptic. This popover has whatever is in the label (the popover title), and hint (detailed popover body).
This encourages me to make sure that as many items as possible, have accessibility support. It also is a lot easier to test, than running voiceover (which I need to do anyway, as sometimes, text does not speak the way we think).
I also localize my accessibility[0].
[0] https://github.com/RiftValleySoftware/RVS_Generic_Swift_Toolbox/blob/92e773b4ea8dfde00e3da564162df3f98c58f801/Sources/RVS_Generic_Swift_Toolbox/RVS_Generic_Swift_Toolbox_Extensions/RVS_Foundation_Extensions.swift#L192 https://github.com/RiftValleySoftware/RVS_Generic_Swift_Tool...