ITunes
From ATHEN
Contents |
Accessibility Features
Accessibility Problems and Solutions
Posting format:
Problem:
Proposed Long-Term Solution:
Workaround:
Version of iTunes:
OS Version:
Date of review:
Other Details:
Lack of Accessibility API Hooks in Windows
Problem: iTunes does not seem to utilize Microsoft Active Accessibility (MSAA) or Microsoft User Interface Automation (MSUIA), which means that assistive technologies don't have direct access to user interface components.
Proposed Long-Term Solution: Work with Apple to ensure improved support for available accessibility API's.
Workaround: jTunes is a set of JAWS scrips that attempts to verbalize iTunes UI components for JAWS users (see below for more information on jTunes).
Version of iTunes: Please add
OS Version: Please add
Date of review: Please add
Other Details:
Captioning
Contacts and Resources
- Apple Accessibility (nothing there on iTunes yet)
Review of ITunes 7.3 accessibility
by Rich Caloggero and Mary Ziegler, MIT Posted by Kathy Cahill, MIT
Macintosh
With the latest version of iTunes (7.3), accessibility with Apple's built-in screen reader VoiceOver is very good. The two things which are difficult to do with it at the moment are:
- When setting up an iTunes store account, there is an account review process which must be completed, and it can only be done via the iTunes interface. All other setup activities can be done via the DotMac website, although that too has severe accessibility problems.
- With the current interface on Mac under VoiceOver, one cannot purchase a complete album. One can purchase one song at a time.
Windows
Under windows, iTunes accessibility is much less complete.
Keyboard controls seem to be enabled (i.e. one can tab around the interface and arrow through the menus, but the screen reader (Jaws for Windows in this case) does not always track and announce the current focus. The easiest way to deal with iTunes under windows is with the Jaws cursor (essentially the mouse cursor). Its cumbersome, but it is possible to purchase and download from the store, and browse and play tunes from various sources and playlists. However, at this time, if one must use iTunes, I'd suggest using it on the Macintosh platform with VoiceOver. If you must use windows, then iTunes is not recommended at this time.
iTunes does not offer variable font sizes. There is no option in iTunes to increase the default font size. This is problematic for users with low vision.
Regarding audio file formats: Currently, Winamp (and perhaps other Windows-based music players) can play unprotected m4a files encoded in AAC (Apple's compression format). Only iTunes can play protected mp4 (.m4p) files. So, if your podcasts are public (unprotected), then chances are iTunes is not required to play them, even though they are distributed in some mp4 format. However, if your podcasts are restricted and are using Apple's DRM, then iTunes is the only way these can be played.
Assistive Technology
T & T Consultancy's [J-Tunes] provides an accessible interface for iTunes that works for JAWS users. It is available as a demo (functioning for 10 minutes at a time, then requiring a reboot) or as a paid full version.
J-Tunes is a set of JAWS scripts that allows JAWS to verbalize the iTunes interface elements that it encounters. This currently seems to be the only available approach to accessibility since iTunes does not provide API hooks that provide for direct access to interface components by assistive technologies. The problem with this approach is that it is vulnerable if iTunes updates change the interface layout.
J-Tunes is distributed in the United States by [Next Generation Technologies] (NGT). The price is $75 ($35 for upgrades).
