Does this page look plain and unstyled?

Tools, wizards, articles and tutorials on Web Accessibility for the conscientious web developer

Subscribe to Accessify's RSS Feed   

Screen Reader testing for free?

An email recieved by the WaSP Accessibility Task Force:

I am an Intermediate skilled Website Developer who is seeking out information on doing what I can to make my websites as completely accessible as possible.

I’ve begun searching and reading articles regarding this. The thought occurred to me that it would be great to have these different “reader” software so that I could test my websites once they were reasonably finished. Then I realized the software I wanted is probably quite expensive.

So another thought occurred. What if there are disabled active volunteers who would be willing to review your website with their software? Obviously, it would be a request after one is confident that they have done everything they could rather than while the website is being built.

So I’m hoping this has already been thought of. I would appreciate any response regarding this idea and how practical or valid it would be.

I have to say that, personally, I do not know of anyone who is willing to do this for free and I’m not sure if that’s a reasonable thing to expect, to be honest (given that the software is expensive to buy and it must be more difficult for a blind person to seek gainful employment than a sighted web developer). I don’t mean for this to come across in a harsh way - it’s admirable that the sender wanted to check that the sites are accessible beyond running the pages through an automated validator.

I know that there is the Usability Exchange, which puts developers/companies in touch with disabled end users for this kind of thing, but it’s not a cheap service. So, is there something in between? Or do you know someone who’d be willing to run a few tests as requested in this email? Add comments and I’ll pass ‘em on.

Comments (8) left to “Screen Reader testing for free?”

  1. Adrian Higginbotham wrote:

    There are dozens nae hundreds of Email lists of and for VI tech users out there who often receive and respond to requests such as this. just try searching yahoogroups or freelists. the problems with such an approach other than those which Ian points out are many. You as a dev have very little knowledge about the quality of the feedback you receive, you will probably only get help from those who have time to give thus you might conclude that they are toward the lower end of the skillset of AT users. Unless you ask structured questions (and most don’t) all you get back is a flood of personal preferences, not constructive feedback. Sure you can get something for nothing but like most thngs in life you get what you pay for.

  2. Mike Stone wrote:

    You can test JAWS for free. Their demo program runs for 40 minutes on_each_boot of Windows (at least, mine does). See http://www.freedomscientific.com/fs_products/software_jaws70fea.asp for more information.

  3. Gerard Blake wrote:

    Thunder is a free screen reader.

    http://www.screenreader.net/

  4. Blair wrote:

    You might also want to check out Fangs. It’s not a reader, per-se, but it emulates one by outputting what a typical screen-reader might “say” into a text format. Check it:

    http://www.standards-schmandards.com/index.php?show/fangs

  5. Gaspar wrote:

    You can check http://www.delorie.com/web/lynxview.html emulate the lynx reader, u can download a copy and install on your server and run it from there.
    Or can create a file called delorie.htm on ur server and and usi from www.delorie.com

  6. Adrian Higginbotham wrote:

    Personally I never recommend anyone to try testing a site with a screenreader product unless they are already a confident screenreader user. you simply don’t use the tool in the same way, for example, VI users tend not to sit back and listen to an entire page read, reacting only by jabbing at the keyboard when they hear for instance the name of a Link they want to follow, which is typicly the way the in experienced user tends to approach things. this method can work to prove that the screenreader can cope with the technology, but tells you little about whether the user can. note also that demo versions are always the latest release whereas many paid-up users are using older releases. Yes thunder is a freeware screenreader and is quite good however it only works in the WEBBIE Browser www.webbie.org.uk so mightn’t be up to a test job. System Access www.freedom.info is another low cost solution. Although it costs $500 in its own right you can subscribe to the Freedombox network for around $20 a month which includes free use of SA even when not connecting to the network. free 30 day demo available, and SA retains some functionality after the trial period ends.

  7. Adam Perry wrote:

    I’ve been using FireVox [ http://www.firevox.clcworld.net/ ] a free Open Source extension for Firefox, as a Screen Reader for test purposes. I’ve also tried IBM Home Page Reader and JAWS. So far I have found that Home Page Reader is terrible at supporting so called “AJAX” web applications, while JAWS and Firevox are much better.

    I have no problems with my sight, however, and I am sure Adrians comments are correct: a Visually Impaired (VI?) person will use the screen reader in a very different way.

    Nevertheless I found using a screen reader helped to identify areas of HTML which require improvement (inadequate or missing ALT, TITLE and SUMMARY attributes, for instance).

  8. yan kit chan wrote:

    I have found NVDA to be pretty decent as a free screnreader.
    anyway, I am totally blind myself and I do use the internet extensively - work and even playing games. if there is anything that needs testing (and does not take tooooo much time) I am happy to do it.

Post a Comment

(Never published)
 

Site Navigation

Outside reading

Jeremy Keith does an excellent write-up of the Accessibility 2.0 conference (which I was unable to attend)
Sharepoint and Web Accessibility
Bruce Lawson describes the disparity between Sharepoint/MOSS developed web sites and the level of accessiblity that the tool offers to users (summary - it really is not good!)
How does a screen reader user really hear your web site?
Interesting post on Beast Blog about how a screen reader user - a real one! Not one of those fake web developer tester types! - uses the tool to read a web page. A few surprises were waiting in store for author Mike Cherim.
Web Accessibility Toolbar now available in simplified Chinese
The Web Accessibility Tools Consortium (WAT-C) release a simplified Chinese version of the Web Accessibility Toolbar.
Web 2.0 vs Web Accessibility
1-day seminar in London, 25th April, brings together experts in the field to discuss/demonstrate the accessibility issues faced by web 2.0.
Leading accessibility technologists form new alliance to fix problems
The Accessibility Interoperability Alliance (AIA), comprising (among others) Adobe, HP, Microsoft, Novell, and from the assistive tech industry Dolphin, GW Micro and HiSoftware forms to work together "to create and harmonize standards for accessible techn
Fieldsets, legends and screen readers
An excellent run-down of how fieldsets and legends can improve accessibility and how the various screen readers cope with this useful markup.
CAPTCHAs explained - WacBlog
Another really good post on the RNIB\'s Web Access Centre blog explaining captchas, why they\'re bad for accessibility and what the alternatives may be.
Making WCAG easier to read
Derek Featherstone has created some fancy style sheets to make reading WCAG documents a little easier on the eye.
Top Tips for the title attribute
Ann McMeekin provides a set of simple tips regarding when - or rather when not to - use the title attribute. \'Cos sometimes you can try *too much* to be helpful
California court tilts towards mandating web accessibility
Outlaw.com reports (on behalf of The Register) on the Target California class action lawsuit, digging a little deeper into what Target have been doing of late to address matters.
Screen Readers and display:none
Juicy Studio, aka Gez Lemon, investigate some quirks whereby screen readers announce content that they should not be. Perhaps this could be used for good rather than evil?
Google Developer Podcast: The status of accessibility on the Web
An interview with Google research scientist TV Rahman (and Hubbell, his seeing-eye dog!). Lots of talk about CAPTCHAs and accessibility, but no sign of a transcript for this interview as yet.
Transcript of Shawn Henry's talk from Jun 5th 2007 in London on RNIB's Web Access Centre Blog
Virtual worlds open up to blind
"Online virtual worlds could soon be accessible to blind people thanks to research by students at IBM in Ireland" states BBC News

View all Accessify bookmarks on del.icio.us



This page is styled using Cascading Style Sheets (CSS). If you can read this message, the chances are that your browser does not properly support CSS or you have disabled this yourself. The content on this site is perfectly readable without style sheets, though; it just doesn't look quite so fancy.

site statistics

This site is partnered with MIS Web Design and Top4Office for Copiers and Digipro for Photocopiers. Web design by Swindon Internet & PR Services.

How you can help support this site: Learn web design from the creator of this site, or help him by requesting some PR Photography