The problem with the two lists for windows screen readers is that they are of high volume. If we can keep someone on the list, maybe they'll buy a Mac or stop using windows on that mac. If someone is reading this list, they are already aware or soon will be if they stic around long enough of the potential of the Mac as a viable alternative to the windows screeen readers. Let's not throw the baby out with the bath watter here.
One more thing though, it is not because the screen readers do things in radically different ways that it is the responsibility of the AT and the Developper, it is because the windows platform makes this necessary. ----- Original Message ----- From: "Jacob Schmude" <[EMAIL PROTECTED]> To: "General discussions on all topics relating to the use of Mac OS X by theblind" <[email protected]> Sent: Friday, October 03, 2008 1:21 PM Subject: Re: iTunes 8.0.1 released with Accessibility Enhancements There's the gw-info list for window-eyes users, can't say about jaws though I'm sure there is at least one such list. It's quite a different situation on Windows than on the Mac, though, as far as responsibility goes. On windows the responsibility is divided, because of the ridiculous amount of different API hooks and video driver intercepts that are used by the various screen reader products to retrieve information from the system. Further, given the price of such products, it is not feasible for many developers to test their product with screen readers themselves. So, as much as I'd like to say it is the developers' responsibility, realistically that isn't fair at this point. Software such as NVDA and SA to go have the potential to change this, but they aren't used nearly as much as the expensive screen readers and don't have as much functionality at the moment. Thus, responsibility falls equally upon the software developers and the screen reader manufacturers, with many developers foisting it off to the screen reader manufacturers entirely. Specifically regarding iTunes, I think Apple has put in their part with implementing MSAA into it. In theory it will actually work with any screen reader that has full MSAA support, though in practice they often need tweaking on an application-specific basis to fully make it work. This is contrasted with the situation on the Mac, obviously. On Oct 3, 2008, at 10:05, UCLA Bruins Fan wrote: > is there another list for windows users tht would help jaws and > window eyes users out with Itunes issues? > I, myself, can't offer any guidence because I haven't touched jaws > since switching to the mac in December. > Is it apple's responsibility to make sure Itunes works with third > party windows screen readers? Or does the responsibility fall to > places like GW micro and freedom scientific to make sure their > products are compatible with Itunes? > Just curious. > Olivia > .
