[nfbcs] Using Apple Photo Stream on Windows with JAWS or NVDA

[David Andrews]

Kevin,  It seems to me that for all intents and purposes, Chromevox 
is a screen reader, so Google is forcing your screen reader choice if 
you want the complete benefits of some of their apps.  I can't agree with this.

Dave

At 03:10 PM 1/4/2014, you wrote:
>ChromeVox has built-in navigation controls and accessibility i.e., 
>speech and Braille output, that permit one to access the app without 
>the need for a separate screen reader.
>So neither Window Eyes, Voiceover,  or JAWS is required.
>This is not a web site context it is an accessibility context for 
>the app itself i.e., Google Chrome.
>
>-Kevin
>
>On Jan 4, 2014, at 2:55 PM, Mike Freeman <k7uij at panix.com> wrote:
>
> > If one were to employ your reasoning throughout the software industry, then
> > window-eyes users would have no reason to complain if software and web site
> > developers developed their sites for JAWS. I'm afraid that won't fly in the
> > blind user community.
> >
> > Mike Freeman
> >
> >
> > -----Original Message-----
> > From: nfbcs [mailto:nfbcs-bounces at nfbnet.org] On Behalf Of Kevin Fjelsted
> > Sent: Saturday, January 04, 2014 8:55 AM
> > To: NFB in Computer Science Mailing List
> > Subject: Re: [nfbcs] Using Apple Photo Stream on Windows with JAWS or NVDA
> >
> > I can use Chromevox across multiple platforms i.e., it is accessible.
> > However it is accessible through the implementation of it's own
> > accessibility platform which actually improves consistency and
> > supportability.  It is totally acceptable. to facilitate a common
> > accessibility interface in this manner. In other words, I don't think that
> > there should be a mandate that products be accessible via JAWS for the
> > instance of  the windows platform, If they are indeed accessible through
> > another method such as ChromeVox supports.
> >
> > -Kevin
> >
> > On Jan 4, 2014, at 12:10 AM, Nicole Torcolini <ntorcolini at wavecable.com>
> > wrote:
> >
> >> I don't quite understand what you mean about Chromevox.
> >>
> >> -----Original Message-----
> >> From: nfbcs [mailto:nfbcs-bounces at nfbnet.org] On Behalf Of Kevin Fjelsted
> >> Sent: Friday, January 03, 2014 3:51 PM
> >> To: NFB in Computer Science Mailing List
> >> Subject: Re: [ ] Using Apple Photo Stream on Windows with JAWS or NVDA
> >>
> >> Interesting question about accessibility on a second platform.
> >> Microsoft word is not at accessible on the Mac in fact none of the office
> >> products are.
> >> In the case of Microsoft office for windows, would there be any
> >> accessibility without a third party screen reader since Microsoft seems to
> >> get by being off the hook for supporting screen reading functions beyond
> > the
> >> Navigator bare bones?
> >>
> >> iTunes is only accessible on windows because of outside pressures
> >> litigiously or otherwise.
> >>
> >> Chromevox is accessible on multiple platforms only because it made it's
> > own
> >> sub platform. :) We should be demanding that an app be accessible on any
> >> platform it is built for.
> >>
> >> -Kevin
> >>
> >> On Jan 3, 2014, at 5:34 PM, Nicole Torcolini <ntorcolini at wavecable.com>
> >> wrote:
> >>
> >>> Has anyone had any luck with managing the Apple photo stream on
> >>> Windows using JAWS or NVDA? It shows up in two places, which are the
> >>> actual location and some sort of shortcut under My Computer. The one
> >>> under My Computer is completely inaccessible. The actual location
> >>> works like a regular folder; however, moving the files around there
> >>> has no effect on the files that get synced to my iPhone, so I am
> >>> guessing that there is something magical about the not accessible one.
> >>> Any suggestions? Also, to that end, out of curiosity, if a company
> >>> makes a product that runs on an operating system besides their own,
> >>> should they have to make it work with the accessibility features of that
> >> operating system?
> >>>
> >>> Nicole