viezel
Accessibility Issues
I am using this great module in my app without problems - I thought.
Now that my app has been released I am having users report that they cannot use the app due to VoiceOver not working for them. These users have visual impairments.
What I discovered from a quick play is that when my app is opened the VoiceOver works fine - until I open a fresh Window that is using the NappSlideMenu. At that point the accessibility features of my app cease working and VoiceOver does nothing. In fact some buttons while in VoiceOver mode become completely useless. With VoiceOver "off" all is well.
Any other developers experienced this? I am wondering if accessibility was tested as part of this module? I know I didn't look at this until now :/
I will play around some more and see what I find, but I thought I would post this and see what others have to say...
Hi
Just a thought I had a similar problem with a different module and the cause for me was due to when I opened a new window or focused on a text field or something of the same nature .
For my issue the root of the problem was when I did one of the things mentioned above it took away the 'first responder to events' privilege that the module had initially.
The fix that the developer implemented for me was he added in an event which I could call to give back this 'first responder' privilege .
I'm guessing this May be the same kind of issue.
The module I was using at the time was the media controls module.
.... Just an idea.
Cheers Gary
Sent from my iPhone
On 4 Apr 2014, at 22:06, "Mobilizr" [email protected] wrote:
I am using this great module in my app without problems - I thought.
Now that my app has been released I am having users report that they cannot use the app due to VoiceOver not working for them. These users have visual impairments.
What I discovered from a quick play is that when my app is opened the VoiceOver works fine - until I open a fresh Window that is using the NappSlideMenu. At that point the accessibility features of my app cease working and VoiceOver does nothing. In fact some buttons while in VoiceOver mode become completely useless. With VoiceOver "off" all is well.
Any other developers experienced this? I am wondering if accessibility was tested as part of this module? I know I didn't look at this until now :/
I will play around some more and see what I find, but I thought I would post this and see what others have to say...
— Reply to this email directly or view it on GitHub.
