[mac4theblind] Re: Are there any developers here

  • From: Daniel McGee <danielmcgee134@xxxxxxxxxx>
  • To: "mac4theblind@xxxxxxxxxxxxx" <mac4theblind@xxxxxxxxxxxxx>
  • Date: Sun, 28 Jun 2015 18:40:31 +0100

Thanks Sarah, have passed the video along. Will see what happens.



On 28 Jun 2015, at 17:31, Sarah k Alawami <marrie12@xxxxxxxxx> wrote:

If you want ot tell them how to make their app accessible point to the very
good documentation at applevis and his key note video.

How easy is it to make an iOS app accessible? This easy:
https://t.co/twgEzMlrJo

Hope it helps.
On Jun 28, 2015, at 8:52 AM, Daniel McGee <danielmcgee134@xxxxxxxxxx> wrote:

Hi all, recently, I have been having a discussion with @overcast.fm about if
it was possible for a VO user to reorganise a playlist in the app. E.G. All
playlist.Daniel McGee (@@danielmcgee134): @OvercastFM any way to do this
with VoiceOver?
http://m.imore.com/how-manually-reorder-podcast-playlists-overcast thank you.

Overcast (@@OvercastFM): @danielmcgee134 I’m not sure how to do it, but it’s
the iOS standard table-reordering mechanism. Is it possible to reorder other
iOS tables?

Daniel McGee (@@danielmcgee134): @OvercastFM would it look something like
this. http://twitter.com/danielmcgee134/status/613383607248420864/photo/1

Daniel McGee (@@danielmcgee134): @OvercastFM hi Marko, was the screen shot
and demo I sent to you any help in knowing how to re order podcast episodes
with VO?for all here, the screen shot was referring to:
Settings, general, accessibility, voiceover, Rotor Button.
For developers,would this be considered as what Marko quotes about the IOS
standard reordering mechanism..
Thanks for any replies in advance.daniel ************


You are subscribed to the mac4theblind mailing list.


The url for this list, where one can unsubscribe or make any changes to
their list subscription is:

//www.freelists.org/list/mac4theblind

The list archive is located at

//www.freelists.org/archive/mac4theblind/

All emails intended for the list owner can be sent to:

john@xxxxxxxxxxxxxxxxxx

Other related posts: