I went on Facebook and looked for JAWS support and user groups. I posted a polite request for volunteers to participate in a user study of foss community build

I went on Facebook and looked for JAWS support and user groups. I posted a polite request for volunteers to participate in a user study of foss community building software. A couple of volunteers came forward. I supplied them with a URL to a standard build and a list of tasks covering the basic feature set -- read topics list, find particular topic, particular user, apply tags, register, post something under account, sign out, look up stats. Because I had already tested with Netscape, IE, textmode, NoJS, keyboard-driven, and because I'd already conducted several revealing user tests with novice users, the screen reader tests passed with flying colors on the first try and with no reported issues. That doesn't mean my work is done, and I'll have to keep re-testing as I continue development. However, I think it illustrates well the benefit of trying to support not just 10% browsers, and not just 1% browsers, and not just 0.1% browsers, but every single configuration you find or can imagine. Of course, if your goal is development speed and such, the top most common refrain I hear when presenting this point of view, this may not work for you, and I wish you the best of luck, it's not for everyone. But if you're writing for longevity and accessibility, this is the routr I'd recommend.