*********************************************************************
WEB STANDARDS GROUP MAIL LIST DIGEST
*********************************************************************
From: "Minh D. Tran" <[EMAIL PROTECTED]>
Date: Wed, 5 Dec 2007 07:47:19 -0800 (PST)
Subject: Simple question on forms
Hi Everyone,
I just have a question regarding forms. How do I set the cursor to
default on a certain form input field?
Thanks,
M
---------------------------------
Looking for last minute shopping deals? Find them fast with Yahoo!
Search.
*********************************************************************
From: "Max A. Shpack" <[EMAIL PROTECTED]>
Date: Wed, 5 Dec 2007 17:56:29 +0200
Subject: Re: [WSG] Simple question on forms
form elements have focus() method in javascript. plain html doesn't
allow this.
Cheers,
Max.
2007/12/5, Minh D. Tran <[EMAIL PROTECTED]>:
Hi Everyone,
I just have a question regarding forms. How do I set the cursor to
default
on a certain form input field?
Thanks,
M
________________________________
Looking for last minute shopping deals? Find them fast with Yahoo!
Search.
*******************************************************************
List Guidelines:
http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe:
http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: "Matthew Pennell" <[EMAIL PROTECTED]>
Date: Wed, 5 Dec 2007 15:59:06 +0000
Subject: Re: [WSG] Simple question on forms
On 12/5/07, Minh D. Tran <[EMAIL PROTECTED]> wrote:
I just have a question regarding forms. How do I set the cursor to
default
on a certain form input field?
Do you mean you want to automatically give focus to a particular
form field
when the page loads? You can simply call the .focus() method on the
element:
document.getElementById('myfield').focus();
Consider the accessibility implications, first, though; not
everyone will be
happy to have decisions made for them about where they want their
cursor to
be. ;)
- Matthew.
*********************************************************************
From: "Minh D. Tran" <[EMAIL PROTECTED]>
Date: Wed, 5 Dec 2007 07:47:19 -0800 (PST)
Subject: [WSG] Simple question on forms
Hi Everyone,
I just have a question regarding forms. How do I set the cursor to
default on a certain form input field?
Thanks,
M
---------------------------------
Looking for last minute shopping deals? Find them fast with Yahoo!
Search.
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: "Matthew Pennell" <[EMAIL PROTECTED]>
Date: Wed, 5 Dec 2007 15:59:06 +0000
Subject: Re: [WSG] Simple question on forms
On 12/5/07, Minh D. Tran <[EMAIL PROTECTED]> wrote:
I just have a question regarding forms. How do I set the cursor to
default
on a certain form input field?
Do you mean you want to automatically give focus to a particular
form field
when the page loads? You can simply call the .focus() method on the
element:
document.getElementById('myfield').focus();
Consider the accessibility implications, first, though; not
everyone will be
happy to have decisions made for them about where they want their
cursor to
be. ;)
- Matthew.
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: "Max A. Shpack" <[EMAIL PROTECTED]>
Date: Wed, 5 Dec 2007 17:56:29 +0200
Subject: Re: [WSG] Simple question on forms
form elements have focus() method in javascript. plain html doesn't
allow this.
Cheers,
Max.
2007/12/5, Minh D. Tran <[EMAIL PROTECTED]>:
Hi Everyone,
I just have a question regarding forms. How do I set the cursor to
default
on a certain form input field?
Thanks,
M
________________________________
Looking for last minute shopping deals? Find them fast with Yahoo!
Search.
*******************************************************************
List Guidelines:
http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe:
http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: Charlesthomas Eaton <[EMAIL PROTECTED]>
Date: Wed, 5 Dec 2007 10:16:09 -0600
Subject: Re: [WSG] Simple question on forms
By default, forms fields take focus from the top-down and left to
right. All you have to do, is line them up in the order you want them
to have focus.
-chuck
=================================
On Dec 5, 2007, at 9:47 AM, Minh D. Tran wrote:
Hi Everyone,
I just have a question regarding forms. How do I set the cursor to
default on a certain form input field?
Thanks,
M
*********************************************************************
From: Charlesthomas Eaton <[EMAIL PROTECTED]>
Date: Wed, 5 Dec 2007 10:16:09 -0600
Subject: Re: [WSG] Simple question on forms
By default, forms fields take focus from the top-down and left to
right. All you have to do, is line them up in the order you want them
to have focus.
-chuck
=================================
On Dec 5, 2007, at 9:47 AM, Minh D. Tran wrote:
Hi Everyone,
I just have a question regarding forms. How do I set the cursor to
default on a certain form input field?
Thanks,
M
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: Paul Hanson <[EMAIL PROTECTED]>
Date: Wed, 5 Dec 2007 10:32:48 -0600
Subject: Default Cursor into Search box
Matthew,
I don't have a field name. I only have one field on my HTML pages,
which is
the search box. This is my Form:
|
<form method="get" action="#" onsubmit="highlight(this.highl.value)
;return false">
<input type="text" id="highl" />
<input type="submit" value="Search this Page" /><br />
</form>
|
How do I make the cursor default to the search box? Where would I
put the d
ocument.getElementById('myfield').focus(); line in my HTML code?
Can I add
it to this code:
|
<body onLoad="beginSearch ()">
|
Help?
Paul Hanson
Technical Writer
RoboHelp ACE - http://www.adobe.com/support/forums/team macromedia/
robohelp
.html
Quintrex Data Systems http://www.quintrex.com<http://
www.quintrex.com/>
email: phanson at quintrex.com
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On B
ehalf Of Matthew Pennell
Do you mean you want to automatically give focus to a particular
form field
when the page loads? You can simply call the .focus() method on
the elemen
t:
document.getElementById('myfield').focus();
Consider the accessibility implications, first, though; not
everyone will b
e happy to have decisions made for them about where they want their
cursor
to be. ;)
- Matthew.
*********************************************************************
From: Paul Hanson <[EMAIL PROTECTED]>
Date: Wed, 5 Dec 2007 10:32:48 -0600
Subject: [WSG] Default Cursor into Search box
Matthew,
I don't have a field name. I only have one field on my HTML pages,
which is
the search box. This is my Form:
|
<form method="get" action="#" onsubmit="highlight(this.highl.value)
;return false">
<input type="text" id="highl" />
<input type="submit" value="Search this Page" /><br />
</form>
|
How do I make the cursor default to the search box? Where would I
put the
document.getElementById('myfield').focus(); line in my HTML code?
Can I ad
d it to this code:
|
<body onLoad="beginSearch ()">
|
Help?
Paul Hanson
Technical Writer
RoboHelp ACE - http://www.adobe.com/support/forums/team macromedia/
robohelp
.html
Quintrex Data Systems http://www.quintrex.com<http://
www.quintrex.com/>
email: phanson at quintrex.com
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Matthew Pennell
Do you mean you want to automatically give focus to a particular
form field
when the page loads? You can simply call the .focus() method on
the elemen
t:
document.getElementById('myfield').focus();
Consider the accessibility implications, first, though; not
everyone will
be happy to have decisions made for them about where they want
their curso
r to be. ;)
- Matthew.
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: "James Leslie" <[EMAIL PROTECTED]>
Date: Wed, 5 Dec 2007 17:03:10 -0000
Subject: RE: [WSG] Simple question on forms
That is not really true. Form fields take focus from the order they
are
in the code. They can be positioned anywhere on the screen using CSS.
Without intervention they will follow this order regardless of top,
bottom, left or right on the screen.
'Lining them up' would (hopefully) be done with CSS but will not
affect
the document flow.
James
------------------------------
By default, forms fields take focus from the top-down and left to
right.
All you have to do, is line them up in the order you want them to have
focus.
-chuck
*********************************************************************
From: [EMAIL PROTECTED]
Date: Wed, 5 Dec 2007 10:52:25 -0600
Subject: [WSG] Default Cursor into Search box
Return Receipt
Your [WSG] Default Cursor into Search box
document:
was Marjori Blaske/PGG/Cummins
received
by:
at: 12/05/2007 10:52:25 CST
*********************************************************************
From: [EMAIL PROTECTED]
Date: Wed, 5 Dec 2007 11:15:34 -0600
Subject: [WSG] Default Cursor into Search box
Return Receipt
Your [WSG] Default Cursor into Search box
document:
was Marjori Blaske/PGG/Cummins
received
by:
at: 12/05/2007 11:15:34 CST
*********************************************************************
From: "James Leslie" <[EMAIL PROTECTED]>
Date: Wed, 5 Dec 2007 17:03:10 -0000
Subject: RE: [WSG] Simple question on forms
That is not really true. Form fields take focus from the order they
are
in the code. They can be positioned anywhere on the screen using CSS.
Without intervention they will follow this order regardless of top,
bottom, left or right on the screen.
'Lining them up' would (hopefully) be done with CSS but will not
affect
the document flow.
James
------------------------------
By default, forms fields take focus from the top-down and left to
right.
All you have to do, is line them up in the order you want them to have
focus.
-chuck
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: [EMAIL PROTECTED]
Date: Wed, 5 Dec 2007 10:52:25 -0600
Subject: [WSG] Default Cursor into Search box
Return Receipt
Your [WSG] Default Cursor into Search box
document:
was Marjori Blaske/PGG/Cummins
received
by:
at: 12/05/2007 10:52:25 CST
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: [EMAIL PROTECTED]
Date: Wed, 5 Dec 2007 11:15:34 -0600
Subject: [WSG] Default Cursor into Search box
Return Receipt
Your [WSG] Default Cursor into Search box
document:
was Marjori Blaske/PGG/Cummins
received
by:
at: 12/05/2007 11:15:34 CST
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: Michael Horowitz <[EMAIL PROTECTED]>
Date: Wed, 05 Dec 2007 11:48:25 -0500
Subject: Re: [WSG] Simple question on forms
tabindex determines the order in which people tab through a form. I
would prefer this to using javascript because it avoids problems with
browsers that don't recognize the javascript.
http://www.w3.org/TR/html4/interact/forms.html#h-17.11
Michael Horowitz
Your Computer Consultant
http://yourcomputerconsultant.com
561-394-9079
Charlesthomas Eaton wrote:
By default, forms fields take focus from the top-down and left to
right. All you have to do, is line them up in the order you want them
to have focus.
-chuck
=================================
On Dec 5, 2007, at 9:47 AM, Minh D. Tran wrote:
Hi Everyone,
I just have a question regarding forms. How do I set the cursor to
default on a certain form input field?
Thanks,
M
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: [EMAIL PROTECTED]
Date: Wed, 5 Dec 2007 12:20:51 -0600
Subject: [WSG] Default Cursor into Search box
Return Receipt
Your [WSG] Default Cursor into Search box
document:
was Chris Block/PGG/Cummins
received
by:
at: 12/05/2007 12:20:51 CST
*********************************************************************
From: Michael Horowitz <[EMAIL PROTECTED]>
Date: Wed, 05 Dec 2007 11:48:25 -0500
Subject: Re: [WSG] Simple question on forms
tabindex determines the order in which people tab through a form. I
would prefer this to using javascript because it avoids problems with
browsers that don't recognize the javascript.
http://www.w3.org/TR/html4/interact/forms.html#h-17.11
Michael Horowitz
Your Computer Consultant
http://yourcomputerconsultant.com
561-394-9079
Charlesthomas Eaton wrote:
By default, forms fields take focus from the top-down and left to
right. All you have to do, is line them up in the order you want them
to have focus.
-chuck
=================================
On Dec 5, 2007, at 9:47 AM, Minh D. Tran wrote:
Hi Everyone,
I just have a question regarding forms. How do I set the cursor to
default on a certain form input field?
Thanks,
M
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: [EMAIL PROTECTED]
Date: Wed, 5 Dec 2007 12:21:09 -0600
Subject: [WSG] Default Cursor into Search box
Return Receipt
Your [WSG] Default Cursor into Search box
document:
was Chris Block/PGG/Cummins
received
by:
at: 12/05/2007 12:21:09 CST
*********************************************************************
From: [EMAIL PROTECTED]
Date: Wed, 5 Dec 2007 12:20:51 -0600
Subject: [WSG] Default Cursor into Search box
Return Receipt
Your [WSG] Default Cursor into Search box
document:
was Chris Block/PGG/Cummins
received
by:
at: 12/05/2007 12:20:51 CST
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: [EMAIL PROTECTED]
Date: Wed, 5 Dec 2007 12:21:09 -0600
Subject: [WSG] Default Cursor into Search box
Return Receipt
Your [WSG] Default Cursor into Search box
document:
was Chris Block/PGG/Cummins
received
by:
at: 12/05/2007 12:21:09 CST
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: "Alastair Campbell" <[EMAIL PROTECTED]>
Date: Wed, 5 Dec 2007 19:02:32 +0000
Subject: Re: [WSG] Simple question on forms
Michael Horowitz wrote:
tabindex determines the order in which people tab through a form.
The default tabindex simply follows the source order, as mentioned
before.
I would recommend not specifying the tabindex unless you are prepared
to spend a lot of time doing everything, as it overrides the default.
For more:
http://joeclark.org/book/sashay/serialization/Chapter08.html#h3-5325
http://www.netmag.co.uk/zine/the-accessibility-test/www-
huntforproperty-ie
There are two main methods of going through a page with a screen
reader, with 'next' (arrowing in JAWs) or with the tab, through links
and form controls. When those two don't match, it's pretty confusing.
Kind regards,
-Alastair
*********************************************************************
From: "Alastair Campbell" <[EMAIL PROTECTED]>
Date: Wed, 5 Dec 2007 19:02:32 +0000
Subject: Re: [WSG] Simple question on forms
Michael Horowitz wrote:
tabindex determines the order in which people tab through a form.
The default tabindex simply follows the source order, as mentioned
before.
I would recommend not specifying the tabindex unless you are prepared
to spend a lot of time doing everything, as it overrides the default.
For more:
http://joeclark.org/book/sashay/serialization/Chapter08.html#h3-5325
http://www.netmag.co.uk/zine/the-accessibility-test/www-
huntforproperty-ie
There are two main methods of going through a page with a screen
reader, with 'next' (arrowing in JAWs) or with the tab, through links
and form controls. When those two don't match, it's pretty confusing.
Kind regards,
-Alastair
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: [EMAIL PROTECTED]
Date: Thu, 6 Dec 2007 09:43:12 +1100
Subject: [WSG] Default Cursor into Search box
Return Receipt
Your [WSG] Default Cursor into Search box
document:
was Lisa Kerrigan/StateDevPolicy/DSD
received
by:
at: 06/12/2007 09:45:48 AM
**********************************************************************
Department of Innovation, Industry and Regional Development,
Government of Victoria, Victoria, Australia.
This e-mail and any attachments may contain privileged and
confidential
information. If you are not the intended recipient, you may not
distribute
reproduce this e-mail or the attachments. If you have received
this message
in error, please notify us by return e-mail.
**********************************************************************
*********************************************************************
From: [EMAIL PROTECTED]
Date: Thu, 6 Dec 2007 09:43:32 +1100
Subject: [WSG] Default Cursor into Search box
Return Receipt
Your [WSG] Default Cursor into Search box
document:
was Lisa Kerrigan/StateDevPolicy/DSD
received
by:
at: 06/12/2007 09:46:08 AM
**********************************************************************
Department of Innovation, Industry and Regional Development,
Government of Victoria, Victoria, Australia.
This e-mail and any attachments may contain privileged and
confidential
information. If you are not the intended recipient, you may not
distribute
reproduce this e-mail or the attachments. If you have received
this message
in error, please notify us by return e-mail.
**********************************************************************
*********************************************************************
From: [EMAIL PROTECTED]
Date: Thu, 6 Dec 2007 09:43:12 +1100
Subject: [WSG] Default Cursor into Search box
Return Receipt
Your [WSG] Default Cursor into Search box
document:
was Lisa Kerrigan/StateDevPolicy/DSD
received
by:
at: 06/12/2007 09:45:48 AM
**********************************************************************
Department of Innovation, Industry and Regional Development,
Government of Victoria, Victoria, Australia.
This e-mail and any attachments may contain privileged and
confidential
information. If you are not the intended recipient, you may not
distribute
reproduce this e-mail or the attachments. If you have received
this message
in error, please notify us by return e-mail.
**********************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: [EMAIL PROTECTED]
Date: Thu, 6 Dec 2007 09:43:32 +1100
Subject: [WSG] Default Cursor into Search box
Return Receipt
Your [WSG] Default Cursor into Search box
document:
was Lisa Kerrigan/StateDevPolicy/DSD
received
by:
at: 06/12/2007 09:46:08 AM
**********************************************************************
Department of Innovation, Industry and Regional Development,
Government of Victoria, Victoria, Australia.
This e-mail and any attachments may contain privileged and
confidential
information. If you are not the intended recipient, you may not
distribute
reproduce this e-mail or the attachments. If you have received
this message
in error, please notify us by return e-mail.
**********************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: Jixor - Stephen I <[EMAIL PROTECTED]>
Date: Thu, 06 Dec 2007 11:49:44 +1100
Subject: Re: [WSG] Article: "Vocalize Firefox" (text-to-speech
extensions for Firefox)
That said how would it compare for a developer that is making an
effort
to correctly mark up their html just to get an impression of how it
would work for a screen reader user?
Steve Green wrote:
A year ago I started to evaluate FireVox 2.6 and had a dialog with
Charles
Chen, its creator. At that time there is no way I would describe
it as
"full-fledged screen reader" as it had many shortcomings. I got the
impression it was really just a hobby project, and Charles said he
had
pretty much abandoned it in order to work on more interesting
stuff. I see
it is now up to version 3.4 so it will be interesting to see how
it has
progressed.
It was certainly usable, but it bears no comparison with a
professional
screen reader like JAWS, which is a far superior product. OK, it
should be
for $1500 but people should not think that they're getting a $1500
product
for free when they install FireVox. It's more akin to products in
the $200
price bracket.
One example of the difference is in forms where <label> elements
have not
been used, and let's face it, that's 99% of all forms. JAWS applies
heuristics to identify the text that is most likely to be the
label, and
associates it with the form control as if a <label> element had
been used. 9
times out of 10 it gets it right. FireVox does not do this.
Steve
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Nick Lo
Sent: 05 December 2007 04:25
To: wsg@webstandardsgroup.org
Subject: [WSG] Article: "Vocalize Firefox" (text-to-speech
extensions for
Firefox)
I'm wondering if anyone has tried/tested the following potentially
useful
extensions and if so what their opinion was/is:
"Two recently released text-to-speech extensions can transform
Firefox into
a talking Web browser suitable for users with visual impairments
-- and
anyone else who can use a speech interface to the Web. Fire Vox is
designed
to be a full-fledged "screen reader in a browser," usable for
daily browsing
even for unsighted users. CLiCk, Speak provides point-and-click
screen
reading, which can be helpful for partially-sighted users or
sighted users
who have written language difficulties (such as dyslexia)."
http://www.linux.com/feature/122197
Nick
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: Jixor - Stephen I <[EMAIL PROTECTED]>
Date: Thu, 06 Dec 2007 11:49:44 +1100
Subject: Re: [WSG] Article: "Vocalize Firefox" (text-to-speech
extensions for Firefox)
That said how would it compare for a developer that is making an
effort
to correctly mark up their html just to get an impression of how it
would work for a screen reader user?
Steve Green wrote:
A year ago I started to evaluate FireVox 2.6 and had a dialog with
Charles
Chen, its creator. At that time there is no way I would describe
it as
"full-fledged screen reader" as it had many shortcomings. I got the
impression it was really just a hobby project, and Charles said he
had
pretty much abandoned it in order to work on more interesting
stuff. I see
it is now up to version 3.4 so it will be interesting to see how
it has
progressed.
It was certainly usable, but it bears no comparison with a
professional
screen reader like JAWS, which is a far superior product. OK, it
should be
for $1500 but people should not think that they're getting a $1500
product
for free when they install FireVox. It's more akin to products in
the $200
price bracket.
One example of the difference is in forms where <label> elements
have not
been used, and let's face it, that's 99% of all forms. JAWS applies
heuristics to identify the text that is most likely to be the
label, and
associates it with the form control as if a <label> element had
been used. 9
times out of 10 it gets it right. FireVox does not do this.
Steve
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Nick Lo
Sent: 05 December 2007 04:25
To: wsg@webstandardsgroup.org
Subject: [WSG] Article: "Vocalize Firefox" (text-to-speech
extensions for
Firefox)
I'm wondering if anyone has tried/tested the following potentially
useful
extensions and if so what their opinion was/is:
"Two recently released text-to-speech extensions can transform
Firefox into
a talking Web browser suitable for users with visual impairments
-- and
anyone else who can use a speech interface to the Web. Fire Vox is
designed
to be a full-fledged "screen reader in a browser," usable for
daily browsing
even for unsighted users. CLiCk, Speak provides point-and-click
screen
reading, which can be helpful for partially-sighted users or
sighted users
who have written language difficulties (such as dyslexia)."
http://www.linux.com/feature/122197
Nick
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: russ - maxdesign <[EMAIL PROTECTED]>
Date: Thu, 06 Dec 2007 12:32:28 +1100
Subject: Mail issues
Hey all,
As you know, we are experiencing some mail issues.
The "read receipts" issue has been resolved and the offender
removed from
the WSG system.
However, the double posts has not yet been resolved. It appears
that the
problem is not with the WSG mail server but being caused by someone
who is
reposting messages.
Regardless, we are looking into the problem now. Be aware that we
may shut
down the mail server for a short time today.
Thanks for your patience!
Russ
*********************************************************************
From: "Peter Firminger" <[EMAIL PROTECTED]>
Date: Thu, 6 Dec 2007 12:43:43 +1100
Subject: Test
Hi,
The duplicate posts are coming from a "Globe IT" server in the
Netherlands.
I have blocked the IP address 217.148.170.240
So we'll see if this message comes back...
Please don't reply to this post.
Peter Firminger
*********************************************************************
From: "Steve Green" <[EMAIL PROTECTED]>
Date: Thu, 6 Dec 2007 02:43:09 -0000
Subject: RE: [WSG] Article: "Vocalize Firefox" (text-to-speech
extensions for Firefox)
Whether or not FireVox is a valid tool for testing really depends
on the
content. If you've got a static site that's got all the appropriate
semantic
structure, then it's going to behave much like JAWS or any other
screen
reader. However, as you start to add complexity, the differences
between the
products become more significant. Of course it's these more complex
sites
that you'll want to be testing.
The sort of things I mean would include DOM scripting, CSS
overlays, AJAX,
forms, accessible Flash, data tables etc. The behaviour with JAWS
can vary
significantly from version to version, so we always specify which
version
has been used for testing. If you're testing with FireVox, you
won't be able
to equate it to any particular JAWS version.
I suppose that if you can make sense of the content using FireVox,
then in
all probability it won't be any worse with JAWS. The problem is
when your
site does not work well with FireVox - what do you do then? Do you
spend
time making changes that might not actually be necessary for JAWS
users? Do
you ignore the results and hope it's going to be ok?
Of course if the developer does not have a good understanding of
how screen
reader users 'visualise' web pages, how they navigate through
different
types of content and how they are likely to interpret what they
hear, then
there's not much point testing with any kind of screen reader
except to
verify that the content is actually read out.
Steve
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Jixor - Stephen I
Sent: 06 December 2007 00:50
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Article: "Vocalize Firefox" (text-to-speech
extensions
for Firefox)
That said how would it compare for a developer that is making an
effort to
correctly mark up their html just to get an impression of how it
would work
for a screen reader user?
Steve Green wrote:
A year ago I started to evaluate FireVox 2.6 and had a dialog with
Charles Chen, its creator. At that time there is no way I would
describe it as "full-fledged screen reader" as it had many
shortcomings. I got the impression it was really just a hobby
project,
and Charles said he had pretty much abandoned it in order to work on
more interesting stuff. I see it is now up to version 3.4 so it will
be interesting to see how it has progressed.
It was certainly usable, but it bears no comparison with a
professional screen reader like JAWS, which is a far superior
product.
OK, it should be for $1500 but people should not think that they're
getting a $1500 product for free when they install FireVox. It's more
akin to products in the $200 price bracket.
One example of the difference is in forms where <label> elements have
not been used, and let's face it, that's 99% of all forms. JAWS
applies heuristics to identify the text that is most likely to be the
label, and associates it with the form control as if a <label>
element
had been used. 9 times out of 10 it gets it right. FireVox does
not do
this.
Steve
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Nick Lo
Sent: 05 December 2007 04:25
To: wsg@webstandardsgroup.org
Subject: [WSG] Article: "Vocalize Firefox" (text-to-speech extensions
for
Firefox)
I'm wondering if anyone has tried/tested the following potentially
useful extensions and if so what their opinion was/is:
"Two recently released text-to-speech extensions can transform
Firefox
into a talking Web browser suitable for users with visual impairments
-- and anyone else who can use a speech interface to the Web. Fire
Vox
is designed to be a full-fledged "screen reader in a browser," usable
for daily browsing even for unsighted users. CLiCk, Speak provides
point-and-click screen reading, which can be helpful for
partially-sighted users or sighted users who have written language
difficulties (such as dyslexia)."
http://www.linux.com/feature/122197
Nick
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: Stijn Audooren <[EMAIL PROTECTED]>
Date: Thu, 6 Dec 2007 07:58:08 +0100
Subject: [WSG] Default Cursor into Search box
Return Receipt
Your [WSG] Default Cursor into Search box
document
:
was Stijn Audooren/TVH
received
by:
at: 06/12/2007 07:57:24
*********************************************************************
From: Stijn Audooren <[EMAIL PROTECTED]>
Date: Thu, 6 Dec 2007 07:58:04 +0100
Subject: [WSG] Default Cursor into Search box
Return Receipt
Your [WSG] Default Cursor into Search box
document
:
was Stijn Audooren/TVH
received
by:
at: 06/12/2007 07:57:20
*********************************************************************
From: Stijn Audooren <[EMAIL PROTECTED]>
Date: Thu, 6 Dec 2007 07:58:08 +0100
Subject: [WSG] Default Cursor into Search box
Return Receipt
Your [WSG] Default Cursor into Search box
document
:
was Stijn Audooren/TVH
received
by:
at: 06/12/2007 07:57:24
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: Stijn Audooren <[EMAIL PROTECTED]>
Date: Thu, 6 Dec 2007 07:58:04 +0100
Subject: [WSG] Default Cursor into Search box
Return Receipt
Your [WSG] Default Cursor into Search box
document
:
was Stijn Audooren/TVH
received
by:
at: 06/12/2007 07:57:20
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*********************************************************************
From: "Steven Faulkner" <[EMAIL PROTECTED]>
Date: Thu, 6 Dec 2007 11:42:00 +0000
Subject: Re: [WSG] Article: "Vocalize Firefox" (text-to-speech
extensions for Firefox)
To get an idea of how screen readers vocalise content (it also many
other features) I would recommend trying adesigner
(http://www.alphaworks.ibm.com/tech/adesigner)
On 06/12/2007, Jixor - Stephen I <[EMAIL PROTECTED]> wrote:
That said how would it compare for a developer that is making an
effort
to correctly mark up their html just to get an impression of how it
would work for a screen reader user?
Steve Green wrote:
A year ago I started to evaluate FireVox 2.6 and had a dialog
with Charles
Chen, its creator. At that time there is no way I would describe
it as
"full-fledged screen reader" as it had many shortcomings. I got the
impression it was really just a hobby project, and Charles said
he had
pretty much abandoned it in order to work on more interesting
stuff. I see
it is now up to version 3.4 so it will be interesting to see how
it has
progressed.
It was certainly usable, but it bears no comparison with a
professional
screen reader like JAWS, which is a far superior product. OK, it
should be
for $1500 but people should not think that they're getting a
$1500 product
for free when they install FireVox. It's more akin to products in
the $200
price bracket.
One example of the difference is in forms where <label> elements
have not
been used, and let's face it, that's 99% of all forms. JAWS applies
heuristics to identify the text that is most likely to be the
label, and
associates it with the form control as if a <label> element had
been used. 9
times out of 10 it gets it right. FireVox does not do this.
Steve
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Nick Lo
Sent: 05 December 2007 04:25
To: wsg@webstandardsgroup.org
Subject: [WSG] Article: "Vocalize Firefox" (text-to-speech
extensions for
Firefox)
I'm wondering if anyone has tried/tested the following
potentially useful
extensions and if so what their opinion was/is:
"Two recently released text-to-speech extensions can transform
Firefox into
a talking Web browser suitable for users with visual impairments
-- and
anyone else who can use a speech interface to the Web. Fire Vox
is designed
to be a full-fledged "screen reader in a browser," usable for
daily browsing
even for unsighted users. CLiCk, Speak provides point-and-click
screen
reading, which can be helpful for partially-sighted users or
sighted users
who have written language difficulties (such as dyslexia)."
http://www.linux.com/feature/122197
Nick
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
--
with regards
Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium
www.paciellogroup.com | www.wat-c.org
Web Accessibility Toolbar -
http://www.paciellogroup.com/resources/wat-ie-about.html
*********************************************************************
From: "Steven Faulkner" <[EMAIL PROTECTED]>
Date: Thu, 6 Dec 2007 11:42:00 +0000
Subject: Re: [WSG] Article: "Vocalize Firefox" (text-to-speech
extensions for Firefox)
To get an idea of how screen readers vocalise content (it also many
other features) I would recommend trying adesigner
(http://www.alphaworks.ibm.com/tech/adesigner)
On 06/12/2007, Jixor - Stephen I <[EMAIL PROTECTED]> wrote:
That said how would it compare for a developer that is making an
effort
to correctly mark up their html just to get an impression of how it
would work for a screen reader user?
Steve Green wrote:
A year ago I started to evaluate FireVox 2.6 and had a dialog
with Charles
Chen, its creator. At that time there is no way I would describe
it as
"full-fledged screen reader" as it had many shortcomings. I got the
impression it was really just a hobby project, and Charles said
he had
pretty much abandoned it in order to work on more interesting
stuff. I see
it is now up to version 3.4 so it will be interesting to see how
it has
progressed.
It was certainly usable, but it bears no comparison with a
professional
screen reader like JAWS, which is a far superior product. OK, it
should be
for $1500 but people should not think that they're getting a
$1500 product
for free when they install FireVox. It's more akin to products in
the $200
price bracket.
One example of the difference is in forms where <label> elements
have not
been used, and let's face it, that's 99% of all forms. JAWS applies
heuristics to identify the text that is most likely to be the
label, and
associates it with the form control as if a <label> element had
been used. 9
times out of 10 it gets it right. FireVox does not do this.
Steve
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Nick Lo
Sent: 05 December 2007 04:25
To: wsg@webstandardsgroup.org
Subject: [WSG] Article: "Vocalize Firefox" (text-to-speech
extensions for
Firefox)
I'm wondering if anyone has tried/tested the following
potentially useful
extensions and if so what their opinion was/is:
"Two recently released text-to-speech extensions can transform
Firefox into
a talking Web browser suitable for users with visual impairments
-- and
anyone else who can use a speech interface to the Web. Fire Vox
is designed
to be a full-fledged "screen reader in a browser," usable for
daily browsing
even for unsighted users. CLiCk, Speak provides point-and-click
screen
reading, which can be helpful for partially-sighted users or
sighted users
who have written language difficulties (such as dyslexia)."
http://www.linux.com/feature/122197
Nick
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
--
with regards
Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium
www.paciellogroup.com | www.wat-c.org
Web Accessibility Toolbar -
http://www.paciellogroup.com/resources/wat-ie-about.html
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
**************************************************************
Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
**************************************************************
