I can think of two additional accessibility objectives but both only apply in special cases. For a case of a program in which a user has the opportunity to choose colors which will be used as part of the program's hard copy output (stuff sighted co-workers or managers or clients) will review and perhaps use. Color choices need to be verbal in controls so VoiceOver can tell a user where their selection pointer is not just show a block of the color on the screen like Microsoft Word and Excel do. When color combinations can be selected and used for those of us who have never seen color it would be helpful if we could set a preference that would offer advice about a color combination about to be chosen and ones already chosen. Black and neon colors don't go together well, I will hear sighted people say as much as well as talk about what they call eye sores but these are concepts unique to their own experience of sight. If an organization has standards for color selection and color combination selection these can be configured by preferences and that would be done by support staff but when not working or not yet working in an organizational context it would be nice to have this kind of help available. Maybe that's another piece of software, one could find out the user's context for using colors and color combinations for parts of a presentation then inform the user based on prevailing industry standards x is the message you're sending and let the user know of other possibilities that may be more appropriate if such exist for what they're trying to do. Maybe a color expert system like apple interior decorator.
On Mon, 9 Mar 2009, John J Herzog wrote: For the case where top view rpg's are being built ascii would be helpful to use for screen output. Perhaps direction of approaching monsters might also be something to verbalize based on a user's preference setting. > Hi Martin, > First, thank you for making your programs accessible. > Second, I would like to share my brief thoughts on the subject. I like > your five objectives a lot. I think that if you can achieve all five > of them, no further work will be necessary on your part. > Some others have encouraged you to build self voicing capabilities > into your programs, but I do not think this is necessary. I'm > concerned first and foremost, that it would be a lot of work, and a > possible deterrent to other apple developers thinking about future > accessibility projects. > I do want accessible apps, but this should be as easy to do as > possible on the developers part. You are being considerate of us, so > we should be considerate of you and your time and use pre-existing > tools like VO to get the job done. > Second, like another poster said, I find the voiceover settings and > commands convenient for use in all programs. It would be counter > intuitive to add different voicing keystrokes. > > Thank you for reading, and I look forward to your useable applications > for the mac. If there is anything I can do to help, please let me know. > > Sincerely, > > John > > On Mar 8, 2009, at 8:25 PM, Martin Pilkington wrote: > >> Hi All, >> >> Let me introduce myself. My name is Martin Pilkington and I'm a >> software developer on the Mac. I'm starting to do a big >> accessibility push and I'm trying to get many developers to join me. >> One of the key parts of this push is a pledge to make all my >> applications 100% accessible by the end of 2009. I've defined 100% >> accessible to mean 5 things: >> >> 1. The UI available to VoiceOver users should be as user friendly as >> the visual UI. >> 2. All UI elements should have titles and/or descriptions. >> 3. All custom controls should provide full keyboard access. >> 4. There should be a clear and logical order to navigating UI fields >> with the keyboard. >> 5. Every part of an application should be reachable without the mouse. >> >> Now I'm coming at this from the perspective of someone who hasn't >> got a disability, so I'm hoping everyone on this list could help me. >> Are there any other major points you would say an application needs >> to be 100% accessible to you? Are there any things you would like to >> find in an application as a user with a visual impairment that >> aren't part of the standard Mac accessibility tool? For example, an >> option to get a full text description of the current window and how >> to use it, at any point in the application >> >> Hopefully I can get a lot of other Mac developers to join me in my >> pledge, some others have already come on board with the idea. But >> getting the developers on board is just one piece of the puzzle. The >> most important piece is understanding exactly what your current >> problems and wishes are for accessibility in Mac apps so any >> feedback you can give me is greatly appreciated. >> >> Thanks >> >> --------------------------------- >> Martin Pilkington >> Writer of Weird Symbols >> pi...@mcubedsw.com >> >> >> >>> > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
