![]() ![]() >is not just using Xcode and Visual Studio - if >short cut similar to your initial suggestion >week just looking at it and trying to get a >have been some major changes so this is not >and we must switch to a newer version that came This is not a complicated process by any means and I'm sure that the License Manager could be made accessible within a short amount of time. I've sat at an office in Daly City while a programmer typed a few words, recompiled a Pro Tools beta and, within moments, a new UI element was made accessible. ![]() I assure you that a program such as Pro Tools, with its thousands of custom UI elements, is far more complex to make accessible than the iLok License Manager. ![]() Combo box lists are navigable just as they are anywhere else in the OS. Often, Apple's underlying framework takes over at that point and browsing dialogs is already accessible by default. In most cases, it's a matter of typing a few words per control. However, if it's defined as a button and also labeled, the user can perform the default action, interact in whichever way is appropriate and use the UI controls as intended. If that button is unlabeled, well, that's not so great. If a button is defined as a button, the user sees the button. If UI elements are undefined or unlabeled, the user sees nothing in the application apart from the menu bar. Largely, it's a matter of simply defining UI elements. I offer you a fairly simple solution: Apple has some basic programming guidelines for making applications accessible with VoiceOver. ![]()
0 Comments
Leave a Reply. |