Sorry for the last (empty) reply. I actually didn't want to send this one. However, no time to cry over spilt milk. There's accidently also the newest 'TrackPanelAx.cpp' (for Audacity Rev 13653) attached. I've switched from "helpText" to "description". The consequence is that Jaws should now give the extra information without the Insert-F1 hint. Concretely: Tracks get type as a suffix, i.e. "Label Track", "Note Track" and "Time Track" A Label Track that is waiting for text input has also "Edit On" attached. This information is stored in the name property (as it is the case with e.g. "Mute On". After that, the description string is presented under certain circumstances: 1. Audio Tracks will display - Stereo information (only if the track is stereo, left or right but not mono) - , Sample rate and Sample format, if they differ from the project settings. 2. For Label Tracks - How many Labels are defined (if not in edit mode) - The label text when the label is open (enclosed in '>' and '<') David, I am against a property dialog because the information should readily be available and warn the user of any mismatch. For example: You import a 22050 Hz file in a 44100 Hz project. This will immediately obvious as soon as this track has focus and you know you should/could resample the track in order to keep all tracks consistent. Or you record your voice and you read "Stereo" after the recording has finished. You'll better delete one channel to reduce the file size or project size. It is also much easier to manipulate stereo channels separately since Left or Right is written after the name when "Split Stereo Track" is applied. I don't think that beginners will open the property dialog (or the track dropdown menu) to search for this data. It is obvious that scripts for NVDA, JAWS, SuperNova etc. can do a lot more out of this information: The Tracks could be sorted by those advanced properties for instance. My NVDA module is now able to directly edit label tracks in the track view. Tab and shift Tab jump from one to the other and report start time and/or label text (one can toggle thru the combinations). In play mode, the same keystrokes jump without reporting anything, but do resume playback immediately after a jump. I'll see if I can make a mp3 that illustrates this in a less theoretical manner. Cheers Robert The audacity4blind web site is at //www.freelists.org/webpage/audacity4blind Subscribe and unsubscribe information, message archives, Audacity keyboard commands, and more... To unsubscribe from audacity4blind, send an email to audacity4blind-request@xxxxxxxxxxxxx with subject line unsubscribe