You can read RTF using Microsoft Word or anything more-or-less compatible with it - OpenOffice, AppleWorks, whatever. The Apple stuff has built-in text-to-speech and the Windows stuff interworks with good, if expensive, text-to-speech add-ons. Usually. Microsoft change the RTF spec every so often and you can get bitten by version incompatibilities. Greg has now posted on Usenet saying he's happy with the RTF form of the magazine, so it looks like that's sorted.

An RTF reader doesn't help a lot with websites.

The Sing Out! website navigation is all done by Javascript mouseovers. If you can't see what your cursor is pointing at, you don't have any idea where clicking will take you.

Ordinary HTML links, either from speakable text items or from images with ALT tags describing their content, can be created with any text editor, including any freeware one. I use BBEdit Lite (freeware for MacOS 9), which has some extra utilities to help with this (like the Mudcat blickifier but easier and more wide-ranging), but you don't actually need that much for such a small site as Sing Out!.

What I think has happened is that whoever did Sing Out!'s pages is using a website-creation package that only does Javascript navigation, and that's all the web"master" knows how to use. The "master" probably can't read the code the package has created, let alone edit it.