Re: VoiceOver Accessibility Issues for Blind Users in iOS App

:* Saturday, September 3, 2016 11:33 AM > *To:* Tile Customer Support <t...@thetileapp.com>; macvisionaries < > macvisionaries@googlegroups.com> > *Subject:* Re: VoiceOver Accessibility Issues for Blind Users in iOS App > > > > I've observed same with Tiles and it's

RE: VoiceOver Accessibility Issues for Blind Users in iOS App

[mailto:macvisionaries@googlegroups.com] On Behalf Of Kevin Chao Sent: Saturday, September 3, 2016 11:33 AM To: Tile Customer Support <t...@thetileapp.com>; macvisionaries <macvisionaries@googlegroups.com> Subject: Re: VoiceOver Accessibility Issues for Blind Users in iOS App I've observed sam

Re: VoiceOver Accessibility Issues for Blind Users in iOS App

I've observed same with Tiles and it's due to custom controls and not overwriting the UIAccessibilityLabel to a sensible string. I'm considering switching to TrackR, especially since there is ALexa skill integration. On Wed, Aug 31, 2016 at 9:40 AM Jonathan Cohn wrote: >

Re: VoiceOver Accessibility Issues for Blind Users in iOS App

That sounds like they switched from a standard button to a custom widget. In which case, they need to adjust the Accessible Name. though it probably indicates that they have done additional actions with the widget that would need to be considered, probably with action a lot like the new Nearby

VoiceOver Accessibility Issues for Blind Users in iOS App

Hi, I have noticed over time that the Tile iOS app has become less and less VoiceOver accessible. The key issue I am having is each tile name (i.e. backpack, keys, etc.) is read by VoiceOver as: txt_tile_name txt_tile_name txt_tile_name Apple has specific programming guidelines for making iOS