Re: Blind user 2

In message <117a885dhp9r142@corp.supernews.com>, trevor <not@your.house>
writes
[snip]

>
>copywriting for the blind: sentence headings should be complete sentences
>WITH PERIODS AT THE END otherwise some speech-recogs

speech-recogs??

Text-to-speech engines, surely?

>will treat it as
>part of the next sentence.

Probably not -- if they're actually marked up as <Hn></Hn>. A problem,
though, if they're simply stylized in the CSS.

>use commas liberally, commas are respected by
>speech recognition software with a slight delay, preserving the rhythmic
>flow of sentences. commas are your friend. quotes and other characters
>are not interpolated, they are stated. thus, "trevor is a rock-star" may
>be read as "open quote trevor is a rock hyphen star end quote".

may be, but almost certainly won't be -- just don't leave a space
between quote-words and words-quote ;-)

(You need to be specific about the screen-reader or talking browser
you're referring to.)

>other
>special characters and especially snippets of HTML code sound like utter
>hell on speech-recog but can be made much better with commas. as such,
><p>hello</p> can read
>lessthanpgreaterthenhellolessthanforewardslashpgr eaterthan or it can read
>lessthan p greaterthan hello lessthan forewardslash p greaterthan.

A problem? On encountering this, the AT user will simply ask the
software to read out the code letter-by-letter. Depends what you're
trying to accomplish.

>also,
>SHOUTING DOESN'T WORK. words in uppercase are usually interpreted as
>acronyms: S-H-O-U-T.

Nope. It's usually interpreted as 'shout' and pronounced 'shout' ;-)

>
>you know, i might just as well set up a blog for this. anywho, TTYL,

Why not, indeed. There's always room for another.

>
>trevor

--
Jake

jake <jake@gododdin.demon.co.uk> wrote in
news:dikRUvKINqdCFwaf@gododdin.demon.co.uk:

ok Jake, it sounds like you have probably more experience with this and i
appreciate your input, just please feel free to contribute more than one-
liners in the future. i'm not here trying to play expert, i'm sharing my
findings as they occur and hoping other developers and blind surfers can
be found to participate. hint hint.

you hit it on the head when you said i need to be specific about the tool
in use. what we really need is a chart showing the various capabilities
and pitfalls of the speech tools and an idea of the marketshare.
otherwise we'll end up with this yes-it-do or no-it-don't format which
has gotten old in about 30 seconds. other responses inline.


> Text-to-speech engines, surely?
>

yes, speech recognition software, also called speech-reading or text-to-
speech software.

>
> Probably not -- if they're actually marked up as <Hn></Hn>. A problem,
> though, if they're simply stylized in the CSS.

ok, what the heck is <Hn>? are you specifying an arbitrary <h> tag or is
this some demonological proprietary tag? we are so NOT going down any
proprietary roads here no matter what the installed base.

>
> (You need to be specific about the screen-reader or talking browser
> you're referring to.)
>

we all do. would you by chance be willing to tell us what you know about
the software tools out there? thanks in advance.

trevor wrote:

> yes, speech recognition software, also called speech-reading or text-to-
> speech software.

Speech recognition software is the opposite of text-to-speech. Think about
it.

--
Toby A Inkster BSc (Hons) ARCS
Contact Me ~ http://tobyinkster.co.uk/contact

In message <117dlsqh5bmu03f@corp.supernews.com>, trevor <not@your.house>
writes
>jake <jake@gododdin.demon.co.uk> wrote in
>news:dikRUvKINqdCFwaf@gododdin.demon.co.uk:
>
[snip]

>>
>> Probably not -- if they're actually marked up as <Hn></Hn>. A problem,
>> though, if they're simply stylized in the CSS.
>
>ok, what the heck is <Hn>? are you specifying an arbitrary <h> tag or is
>this some demonological proprietary tag? we are so NOT going down any
>proprietary roads here no matter what the installed base.
>

<Hn> ........ as in <H1> <H2> <H3> <H4> <H5> and <H6>




[snip]

regards.
--
Jake

trevor wrote:
> Toby Inkster <usenet200504@tobyinkster.co.uk> wrote in
> news:pan.2005.05.03.06.37.07.735656@tobyinkster.co .uk:
>
>
>>Speech recognition software is the opposite of text-to-speech. Think
>>about it.
>>
>
>
> i smell smoke.

Smell recognition ... no thats different software .... text smeller ...
that would be cool!

Gerry for email use my name at dergal dt com <sales@exleaseit.co.uk>
wrote in news:zxOde.22867$u5.16067@newsfe2-gui.ntli.net:

>
> One company I worked for wasted over £10k on Webtrends

throw it away.

MGW <mgw1979@hotmail.com> wrote in news:12ef71topu7l9mmjkrcvrhi3r0jgqfhllv@
4ax.com:

>>and I don't know of a way of testing a site using a Screen Reader which
>>follows AURAL CSS which is within my "testing" budget.
>

actually a good point. aural hasn't come up yet. i have no idea what
software supports it.

> There are free screen readers available. Here's a list from
> http://uniquelygifted.org/other_resources.htm:
>

i think we have to be carefull. lots of software will read text to you but
isn't designed for blind websurfers.