this is redundant. the clock is self voicing on the hour for those who don't need vo to take advantage of it. if I had a mind to, I'm sure I could write an app to have vo announce te time at peridocic intervals. The only reason to make an app self voicing is that it cannot fit into the normal paradigm. consider chess and the calculator.
On Mar 8, 2009, at 9:26 PM, Chris Gilland wrote: By self voicing I mean, have it so that with voice over not running the program would still speak right out of the box. In other words, give the user the option of using voice over, or! being able to rely on speech just within the program itself. Kind a like what happens with the clock being self voicing upon the hr half hr or quarter, if you set that up in universal access. Hince: you don't need vo running for that to work. Chris. Do you use Twitter? If so, then, I'd love! for you to follow me. My twitter URL is: http://twitter.com/chris28210 ----- Original Message ----- From: Martin Pilkington To: macvisionaries@googlegroups.com Sent: Sunday, March 08, 2009 9:09 PM Subject: Re: Understanding Blind User's Needs Hi Chris, I'm not 100% sure whether it is possible to detect whether the user is using a braille display or not, but I'll definitely look into it. If OS X doesn't allow me to give different descriptions to braille devices I'll try and get in touch with developers at Apple to see if they can add it in a future version. As for the self voicing feature, I'm a little unsure what you mean. Could you give an example of how it would be used and what it would do? My applications are already in Cocoa and it is indeed fairly easy to make them voice over friendly, though the options to do this aren't really front and centre so they can often be forgotten. Of course not everything is quite as easy to make accessible, especially as I use custom controls in places so these will require more work. As for magnification and high contrast modes, do the system wide zoom and invert colours features not solve that problem? Some things such as making text in some areas bigger and allowing users to customise colours to give them a higher contrast are relatively easy, but to do these for everything in an application would be extremely difficult. These are more system wide features Apple would need to do themselves in order to have them done right. Thanks for your feedback! --------------------------------- Martin Pilkington Writer of Weird Symbols pi...@mcubedsw.com On 9 Mar 2009, at 12:37 am, Chris Gilland wrote: > I think it would be cool to use the default voice set via system > preferences and make it where the program can be self voiceing if > needed. Also provide an option to turn on, or off the self voicing > feature, this way if a user wants to use voice over, great, if not, > he or she still can do what needs to be done. Also, I would make > your labels for the U I, very discriptive but yet maybe slightly > shorter for the interface that is viewed via a braille display. > This way the point is made but only the absolutely necessary amount > of cells are used, this way providing more room for other things, > such as the value of the U I control. I may also advise you write > your programs in cocoe as I hear that language is very very voice > over friendly. Finally maybe provide an option for the program to > be able to enable magnification in the program for low vision > usersw. Also maybe provide an option to turn the programs U I color > to high contrast. > > This way it even helps low vision users as well as us like myself > who are nearly compltely total. > > Chris. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To post to this group, send email to macvisionaries@googlegroups.com To unsubscribe from this group, send email to macvisionaries+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/macvisionaries?hl=en -~----------~----~----~----~------~----~------~--~---
