Grant, Can you please fill us in on how you made the group chat work?
This may be useful for others on the list, too, besides me. Thanks in advance. Keith -----Original Message----- From: viphone@googlegroups.com [mailto:viphone@googlegroups.com] On Behalf Of Grant Hardy Sent: Thursday, January 24, 2013 2:37 PM To: viphone@googlegroups.com Subject: Re: Not As It Seems To Be - Was: Iphone 5 satisfaction ? ^It's worth pointing out that there are plenty, plenty of apps, both on the job and not, that JAWS doesn't work with at all including many of the built-in apps included in Windows 8, as well as most third-party "metro" apps. While you may have lucked out in your particular case with Lotus Notes on the job, there are plenty of other JAWS users that have encountered inaccessible or inefficient apps. An app being accessible to JAWS isn't the exception, but it isn't the rule either. No finger-pointing here, but simply my opinion. Recently, in the course of my university studies I encountered a situation where I needed to arrange an online chat with a group of people to collaborate. After investigating various ways to do that with JAWS on my PC, I presently changed course and turned to the device I'm learning to depend on more and more: my iPhone. That device, where I paid zero dollars for the screen reader, offered a totally accessible group chat environment that lent itself perfectly to my purposes. I'm not saying that I could not have done this on my PC, but this was a fast-paced and time-sensitive environment where backing out due to the chat not working, wasn't really an option. Frankly, I trusted my iPhone quite a bit more than my PC in this situation. (For the record, we were using Facebook Chat to conduct the meeting, a surprisingly tricky task to accomplish on a PC it seems). The reality is, everything on the iPhone talks out of the box, and VoiceOver accessible apps seem to be the rule rather than the exception. Rather than analyzing the politics of the screen reader in question, I just want to know whether it's going to meet my needs and how much I can do with it. iOS seems to be leading the way at present, and I haven't seen anything to suggest that building the screen reader into the OS is a bad thing, quite the contrary actually, it seems to make things that much more robust. On 1/24/13, Christopher Chaltain <chalt...@gmail.com> wrote: > I'm not so sure that those in the blindness community who expressed > concerns about MS getting into the screen reader business was so short > sighted. There's no guarantee that JAWS would still exist if MS had come > out with their own screen reader, and I'm sure JAWS is a superior screen > reader to anything that MS would have come up with. For example, I doubt > very much MS would have spent much time making Lotus Notes accessible > with their screen reader meaning I would have lost my job years ago. I > think there's a real concern with having the screen reader being > developed by the same company that develops the OS and the applications. > Apple's done a great job, and I'm appreciative of their commitment, but > I do wonder about non-Apple products and their support with VO. It's > obviously not a problem if you're only using Apple products, but I can > see where a job would require you to use alternative apps, like Chrome, > MS Office and so on. Sure you can say it's up to the app developer to > make their application accessible, but I need accessible apps and not > finger pointing between the OS developer and the app developer. > > > On 23/01/13 19:19, David Chittenden wrote: >> Then, I am doubly thankful that Apple exhibited the foresight to not check >> with the apparently short-sighted blindness community. >> >> David Chittenden, MSc, MRCAA >> Email: dchitten...@gmail.com >> Mobile: +64 21 2288 288 >> Sent from my iPhone >> >> On 24/01/2013, at 6:03, "Bill Gallik" <wfgal...@charter.net> wrote: >> >>> Please pardon me for this somewhat off topic message, but I do feel >>> obligated to clear the air just a wee bit on a subtle matter that has >>> come up in the original thread. >>> >>> Now first, let me say that I also am extremely pleased with my iPhone 5 >>> and the embedded accessibility. And likewise; major, major KUDOS to >>> Apple for having the (dare I say) foresight to design that accessibility >>> right into their products. Certainly, Apple is to be commended for the >>> effort to provide devices that customers can use right out of the box >>> without incurring additional, prohibitive expense. >>> >>> But I have to point out that Microsoft at one point had mulled around the >>> idea of providing at least an embedded screen reader in the Windows OS; >>> I'm sure there are more than a few others on this list that will remember >>> this. The company had approached both NFB and ACB with feelers to get an >>> idea how that would be received by the blind and visually impaired >>> community. The result of that inquiry caused Microsoft to drop the idea. >>> I must confess my guilt here as I replied with a resounding "NO" to this >>> idea -- I regret to say now. Why I (and many others I presume) replied >>> that way is not germane to this list, but I think we should be careful >>> not to imply that Microsoft has been insensitive to our circumstances. >>> Just for the record. >>> ---------------- >>> Holland's Man, Bill >>> - "A hospital bed is a parked taxi with the meter running." >>> - Julius Henry (Groucho) Marx, 1890 - 1977 >>> -- >>> 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. >>> >>> >> > > -- > Christopher (CJ) > chaltain at Gmail > > -- > 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 "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 "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.
