I would really like to write to the Audible developers, as well. What email 
address have any of you used to contact them?


Thanks,
Ari

On Mar 10, 2013, at 12:26 AM, "Robin Frost" <robinn...@gmail.com> wrote:

> Hi,
> I know this wasn’t directed to me but thank you for your concise explanation 
> expounding on this topic.  It’s always fun to learn from others.  And if 
> you’ve the time feel free to join our communicating with Audible party I’ve 
> tried my best to communicate with them over the past two weeks regarding this 
> issue to what end yet remains yet to be seen but it's always more fun to have 
> company in such endeavors (smiles). and I’d suspect that your knowledge of 
> such matters could only serve to be of benefit to the efforts and their 
> understanding and enlightenment.
> Robin
>  
>  
> From: Cara Quinn
> Sent: Sunday, March 10, 2013 12:34 AM
> To: viphone@googlegroups.com
> Subject: Re: Audible app update 2.1 has arrived
>  
> Hi Sieghard,
>  
> I hadn't seen your prior note. Did you have trouble accessing the button-free 
> mode from the instructions in my note?
>  
> Anyway, yes, I absolutely agree that this should be universally discoverable 
> whether someone uses VO or not.
>  
> However, from my own experience as a developer, not all VO gestures can be 
> captured and communicated to the app, without making some special 
> arrangements  in such app to recreate those gestures. For example, last time 
> I checked, a developer couldn't actually capture a three-finger swipe upward 
> / downward but could capture the left / right swipes.
>  
> So in essence, what this means is that without creating a special area on the 
> screen where VO lets certain gestures pass through automatically, there's no 
> way for an app to know what gesture a user has done. this happens because 
> Voiceover intercepts certain gestures before they actually reach the app.
>  
> So while some VO gestures are easily integrated with a mainstream app, not 
> all gestures are. Some would take a bit of work / creativity on the part of 
> the developers to come up with analogs for.
>  
> However, having said all this, I still agree with you and I'd even go further 
> to say that the button-free mode could be a whole lot neater in its 
> implementation, even for sighted users.
>  
> The idea that you can only access the jump forward feature on one, and only 
> one, screen is really poor design in my opinion. Even for a sighted user, how 
> would you know you needed to swipe up to go into this obscure special mode so 
> you can use gestures to navigate your book if you wanted to?… this is sooo 
> not discoverable…
>  
> Lastly, I'd also be curious to know why the scrub feature is not accessible 
> with VO. it's really quite maddening to deal with. Audible should definitely 
> be aware of this as I'm sure it's not their intention to isolate or segregate 
> a segment of their users…
>  
> Anyway, thanks for your thoughtful note!
>  
> Have a great weekend!…
>  
> Smiles,
>  
> Cara :)
> ---
> View my Online Portfolio at:
>  
> http://www.onemodelplace.com/CaraQuinn
>  
> Follow me on Twitter!
>  
> https://twitter.com/ModelCara
>  
> On Mar 9, 2013, at 10:34 AM, Sieghard Weitzel <siegh...@live.ca> wrote:
>  
> Hi Cara and Robin,
>  
> I guess for those of us who don’t necessarily read the user’s guide these 
> hidden, non-Voiceover accessible features remain a mystery until somebody 
> points them out *smile*. Thanks, Cara, for doing so.
>  
> However, I agree with Robin that this should be accessible. I was just about 
> to post a message to you, Cara, telling you that you should upgrade your app 
> since in the new version there was no such thing as Button-Free mode. Then I 
> thought I better make sure so I called Audible support. At first the 
> technical support guy told me as well that he could not find it, but then he 
> put me on hold and told me that this was there. The way to get to it is to 
> turn Voiceover off, then do a one-finger swipe up from the bottom of the 
> screen just above the home key towards the top. This will enable button-free 
> mode and you can jump forward and back by doing a left to right swipe for 
> forward and a right to left swipe for back. A vertical swipe, either up or 
> down, will insert a bookmark.
>  
> I told him that I would like him to take my feedback which he did by asking 
> me for my Audible email so he could properly log the call and request, and I 
> then told him to document that this is completely not accessible with 
> Voiceover and that Voiceover users have no way to turn on Button-Free mode or 
> to use it with Voiceover.
> The other big issue for me is the fact that in the Chapters and Bookmarks 
> area, the currently playing Chapter is visually highlighted, but Voiceover 
> gives no indication what chapter is currently playing.
>  
> I will also send another email about the Button-Free mode and the fact that 
> Voiceover should say “selected” or “Currently Playing” when you come to the 
> chapter which is currently playing.
>  
> As for Button-Free mode, I don’t see why similar to how Apple solved the 
> Notification Center activation, Audible couldn’t do this so that a 3-finger 
> swipe up would start button-free mode when Voiceover is on. Then maybe a 
> 2-finger or 3-finger swipe left or right could be used for the Jump Forward 
> or Jump Back command just as a 3-finger swipe changes pages when you are on 
> the home screen.
>  
>  

-- 
You received this message because you are subscribed to the "VIPhone" Google 
Group.
To search the VIPhone public archive, visit 
http://www.mail-archive.com/viphone@googlegroups.com/.
To post to this group, send email to viphone@googlegroups.com.
To unsubscribe from this group, send email to 
viphone+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/viphone?hl=en.
--- 
You received this message because you are subscribed to the Google Groups 
"VIPhone" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to viphone+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to