WebAIM - Web Accessibility In Mind

E-mail List Archives

RE: Speech Synthesizer or Screen Readers rendering of quotes

for

From: Robinson, Norman B - Washington, DC
Date: Jun 10, 2005 3:36PM

I'm making an inference based on your email. If you are focusing on this
in a printed document, then you may wish to consider the Firefox browser
with a specific extension called "Fangs"
(http://www.standards-schmandards.com/index.php?show/fangs). I find it
useful in capturing the text equivalent of simulation of a screen
reader. Note that I usually 'capture' it with Fangs, then read the text
while I browse with a real screen reader.

Also, although not your question, you indicated this was for creating an
accessibility guidelines document. If you only state one thing, consider
proper (X)HTML coding allows for better accessibility, as the tools that
function and assist us rely on those standards to be present to
manipulate content. Validation against standards isn't the be-all and
end-all, but it goes a long way to solving the "works for me" problem.
Where possible I always encourage developers and *designers* validate
their code. I'd rather they learn when to ignore errors from an attempt
at valid code rather than suggest they don't validate at all or use
manual inspection only.

As to your real question, there are plenty of synthesizers available for
free if you search for them. If you are using MS Windows you can go to
Microsoft's page and search to find their free version. What usually
works best is if you already have a defined standard set of assistive
technology or specific browsers you expect your user audience to have,
is to test using those applications.

Regards,


Norman Robinson