Re: [WSG] Is pressing Enter to submit (or not) on forms an accessability issue? [SEC=UNCLASSIFIED]

2009-10-22 Thread sharon . pegg
Return Receipt
   
   Your   Re: [WSG] Is pressing Enter to submit (or not) on forms an   
   document:  accessability issue? [SEC=UNCLASSIFIED]  
   
   wassharon.p...@centrelink.gov.au
   received
   by: 
   
   at:23/10/2009 13:01:33  
   





**
IMPORTANT:  This e-mail is intended for the use of the addressee and may 
contain information that is confidential, commercially valuable or subject to 
legal or parliamentary privilege.  If you are not the intended recipient you 
are notified that any review, re-transmission, disclosure, use or dissemination 
of this communication is strictly prohibited by several Commonwealth Acts of 
Parliament.  If you have received this communication in error please notify the 
sender immediately and delete all copies of this transmission together with any 
attachments.
**



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



Re: [WSG] Is pressing Enter to submit (or not) on forms an accessability issue? [SEC=UNCLASSIFIED]

2009-10-21 Thread Mark Stickley
I don't think that pressing enter to submit is an accessibility issue  
at all, it's simply expected behaviour. If people are used to being  
able to do that in their browser then it should not be forced or  
suppressed in any way.


Keyboard only users is an interesting one... so if the person is a  
keyboard user out of choice (as in they prefer to use the keyboard for  
ease of use) they might well be using a setup where it's not possible  
to highlight the submit button to submit it. Someone who is using the  
keyboard only because they have difficulty with a mouse is unlikely to  
have that problem as they'd choose a setup which allows them to do that.


As for putting line breaks in the field, as far as I know no browsers  
will submit a form when you press enter on a textarea, and as input  
type=field /'s are only one line, they surely wouldn't expect to be  
able to put a line break there anyway.


I actually publish a blog post on a very similar topic (although not  
so focussed on the accessibility side of things) yesterday:


http://www.norestfortheweekend.com/2009/10/20/on-forms-submit-buttons-and-browsers/

I hope you find it interesting!

Mark


On 21 Oct 2009, at 04:39, Chris Vickery wrote:


Thanks Jason,
In this case it’s for an input field, not a textarea, and enter will  
still not submit (unless you tab out) so in this case makes it  
contrary to ‘native browser behaviour’.
Essentially our input fields would, (although they identify  
themselves as input fields) would behave like textareas, without  
line breaks.


I’m not really familiar with using a text to speech reader, but that  
sounds messy to me. Interestingly the source itself looks pretty  
straight forward:


div id=abc-form class=form
form name=abcform id=abcform method=post action= 
input type=text name=abcform[email1] value= id=email1  
class=text /input type=submit name=form[subscribebutton1]  
value=Subscribe id=subscribebutton1  /

/form
/div

There must be something buried in the styling causing this behaviour.
Chris

From: li...@webstandardsgroup.org  
[mailto:li...@webstandardsgroup.org] On Behalf Of ja...@flexewebs.com

Sent: Wednesday, 21 October 2009 11:03 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Is pressing Enter to submit (or not) on forms an  
accessability issue? [SEC=UNCLASSIFIED]


Hi Chris,

The submission by pressing enter is a native browser behaviour,  
hence is not an accessibility issue.


You will only be able to submit via enter from an input field and  
not from a textarea, which you have to tab out of and then hit enter.


So I doubt you will find any references to back-up your claim. If  
you do, send it through so we can debunk it. :-D


Best,

Jason
Sent from my BlackBerry® wireless device

From: Chris Vickery chris.vick...@privacy.gov.au
Date: Wed, 21 Oct 2009 10:20:51 +1100
To: wsg@webstandardsgroup.orgwsg@webstandardsgroup.org
Subject: [WSG] Is pressing Enter to submit (or not) on forms an  
accessability issue? [SEC=UNCLASSIFIED]


We’re accessibility testing at the moment. We’ve got some email  
forms (ie. Put in your email address to subscribe - submit) that do  
not currently submit if you press enter.
Personally I feel this should be an accessibility issue, but I am  
finding it difficult to locate any solid documentation to back up my  
claim. I’ve had the argument put to me that a keyboard only user  
could still tab to the submit button, then press enter, but this  
seems very unintuitive to me to force users to do this.


I’ve also had put to me that some users get confused if they want to  
put line breaks in a field and submit by accident... and so to be  
consistent pressing enter should never submit a form. (data entry  
people would love that one :P)


Is submitting by pressing enter from a form best practice, or just  
common practice? Is it an accessibility problem? ... and to what  
degree?


***
WARNING: The information contained in this email may be confidential.
If you are not the intended recipient, any use or copying of any part
of this information is unauthorised. If you have received this email  
in

error, we apologise for any inconvenience and request that you notify
the sender immediately and delete all copies of this email, together
with any attachments.
***


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org

Re: [WSG] Is pressing Enter to submit (or not) on forms an accessability issue? [SEC=UNCLASSIFIED]

2009-10-21 Thread Nathanael Boehm
Sorry Mark but I'm going to have to counter that argument because I believe
it *is* in part an accessibility issue, particularly relating to screen
readers which as we know linearly parse a page ... so unless there is
instructional text or help before the text field advising them of how to
activate or submit that form field or if the behaviour is inconsistent with
both web and on-site conventions then the possible data loss, accidental
data submission or lack of any response on pressing Enter because that user
isn't aware of what is going to happen or not happen (until deciding after a
delay that the Enter key did nothing) until they try it.

The standard browser convention is that in an input field (not textarea),
pressing Enter will activate the action of the containing form element (if
it has one, or unless it's an ASP.NET app in which case the form element
envelops the entire page). Speaking of which, does ASP.NET 3.5 handle that
differently?

Nathanael Boehm
http://www.purecaffeine.com/about/
Canberra, Australia
0409 288 464


On Wed, Oct 21, 2009 at 6:26 PM, Mark Stickley 
markstick...@theyakshack.co.uk wrote:

 I don't think that pressing enter to submit is an accessibility issue at
 all, it's simply expected behaviour. If people are used to being able to do
 that in their browser then it should not be forced or suppressed in any way.

 Keyboard only users is an interesting one... so if the person is a keyboard
 user out of choice (as in they prefer to use the keyboard for ease of use)
 they might well be using a setup where it's not possible to highlight the
 submit button to submit it. Someone who is using the keyboard only because
 they have difficulty with a mouse is unlikely to have that problem as they'd
 choose a setup which allows them to do that.

 As for putting line breaks in the field, as far as I know no browsers will
 submit a form when you press enter on a textarea, and as input type=field
 /'s are only one line, they surely wouldn't expect to be able to put a line
 break there anyway.

 I actually publish a blog post on a very similar topic (although not so
 focussed on the accessibility side of things) yesterday:


 http://www.norestfortheweekend.com/2009/10/20/on-forms-submit-buttons-and-browsers/

 I hope you find it interesting!

 Mark


 On 21 Oct 2009, at 04:39, Chris Vickery wrote:

  Thanks Jason,
 In this case it’s for an input field, not a textarea, and enter will still
 not submit (unless you tab out) so in this case makes it contrary to ‘native
 browser behaviour’.
 Essentially our input fields would, (although they identify themselves as
 input fields) would behave like textareas, without line breaks.

 I’m not really familiar with using a text to speech reader, but that sounds
 messy to me. Interestingly the source itself looks pretty straight forward:

 div id=abc-form class=form
 form name=abcform id=abcform method=post action= 
 input type=text name=abcform[email1] value= id=email1 class=text
 /input type=submit name=form[subscribebutton1] value=Subscribe
 id=subscribebutton1  /
 /form
 /div

 There must be something buried in the styling causing this behaviour.
 Chris

 *From:* li...@webstandardsgroup.org 
 [mailto:li...@webstandardsgroup.orgli...@webstandardsgroup.org
 ] *On Behalf Of *ja...@flexewebs.com
 *Sent:* Wednesday, 21 October 2009 11:03 AM
 *To:* wsg@webstandardsgroup.org
 *Subject:* Re: [WSG] Is pressing Enter to submit (or not) on forms an
 accessability issue? [SEC=UNCLASSIFIED]

 Hi Chris,

 The submission by pressing enter is a native browser behaviour, hence is
 not an accessibility issue.

 You will only be able to submit via enter from an input field and not from
 a textarea, which you have to tab out of and then hit enter.

 So I doubt you will find any references to back-up your claim. If you do,
 send it through so we can debunk it. :-D

 Best,

 Jason

 Sent from my BlackBerry® wireless device
 --
 *From: *Chris Vickery chris.vick...@privacy.gov.au
 *Date: *Wed, 21 Oct 2009 10:20:51 +1100
 *To: *...@webstandardsgroup.orgwsg@webstandardsgroup.org
 *Subject: *[WSG] Is pressing Enter to submit (or not) on forms an
 accessability issue? [SEC=UNCLASSIFIED]

 We’re accessibility testing at the moment. We’ve got some email forms (ie.
 Put in your email address to subscribe - submit) that do not currently
 submit if you press enter.
 Personally I feel this should be an accessibility issue, but I am finding
 it difficult to locate any solid documentation to back up my claim. I’ve had
 the argument put to me that a keyboard only user could still tab to the
 submit button, then press enter, but this seems very unintuitive to me to
 force users to do this.

 I’ve also had put to me that some users get confused if they want to put
 line breaks in a field and submit by accident... and so to be consistent
 pressing enter should never submit a form. (data entry people would love
 that one :P)

 Is submitting by pressing enter from 

Re: [WSG] Is pressing Enter to submit (or not) on forms an accessability issue? [SEC=UNCLASSIFIED]

2009-10-21 Thread Oliver Boermans
2009/10/21 Chris Vickery chris.vick...@privacy.gov.au:
 In this case it’s for an input field, not a textarea, and enter will still
 not submit (unless you tab out) so in this case makes it contrary to ‘native
 browser behaviour’.

This would potentially create annoyance to users of Safari on an
iPhone or iPod Touch.
When you have a text input focused (in contrast to a textarea) Mobile
Safari displays a big blue [ Go ] button in the bottom right corner
which one would expect will submit the form (equivalent to hitting
Enter).
If Enter does not submit the form it will be necessary for Mobile
Safari users to leave the 'form mode' by clicking [Done] and then
manually tap the submit button. I would consider this unexpected
behaviour a usability issue at very least.

Cheers Ollie
--
@ollicle


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



Re: [WSG] Is pressing Enter to submit (or not) on forms an accessability issue? [SEC=UNCLASSIFIED]

2009-10-21 Thread Dennis Lapcewich
Return Receipt
   
   Your   Re: [WSG] Is pressing Enter to submit (or not) on forms an   
   document:  accessability issue? [SEC=UNCLASSIFIED]  
   
   wasdlapcew...@fs.fed.us 
   received
   by: 
   
   at:10/21/2009 08:20:47  
   






***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



RE: [WSG] Is pressing Enter to submit (or not) on forms an accessability issue? [SEC=UNCLASSIFIED]

2009-10-21 Thread Chris Vickery
Thanks everyone for the feedback. Lots to work with there.

Good stuff.

-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On 
Behalf Of Oliver Boermans
Sent: Wednesday, 21 October 2009 8:58 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Is pressing Enter to submit (or not) on forms an 
accessability issue? [SEC=UNCLASSIFIED]

2009/10/21 Chris Vickery chris.vick...@privacy.gov.au:
 In this case it's for an input field, not a textarea, and enter will still
 not submit (unless you tab out) so in this case makes it contrary to 'native
 browser behaviour'.

This would potentially create annoyance to users of Safari on an
iPhone or iPod Touch.
When you have a text input focused (in contrast to a textarea) Mobile
Safari displays a big blue [ Go ] button in the bottom right corner
which one would expect will submit the form (equivalent to hitting
Enter).
If Enter does not submit the form it will be necessary for Mobile
Safari users to leave the 'form mode' by clicking [Done] and then
manually tap the submit button. I would consider this unexpected
behaviour a usability issue at very least.

Cheers Ollie
--
@ollicle


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



***
WARNING: The information contained in this email may be confidential.
If you are not the intended recipient, any use or copying of any part
of this information is unauthorised. If you have received this email in
error, we apologise for any inconvenience and request that you notify
the sender immediately and delete all copies of this email, together
with any attachments.
***


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



Re: [WSG] Is pressing Enter to submit (or not) on forms an accessability issue? [SEC=UNCLASSIFIED]

2009-10-20 Thread jason
Hi Chris,

The submission by pressing enter is a native browser behaviour, hence is not an 
accessibility issue.

You will only be able to submit via enter from an input field and not from a 
textarea, which you have to tab out of and then hit enter.

So I doubt you will find any references to back-up your claim. If you do, send 
it through so we can debunk it. :-D

Best,

Jason
Sent from my BlackBerry® wireless device

-Original Message-
From: Chris Vickery chris.vick...@privacy.gov.au
Date: Wed, 21 Oct 2009 10:20:51 
To: wsg@webstandardsgroup.orgwsg@webstandardsgroup.org
Subject: [WSG] Is pressing Enter to submit (or not) on forms an accessability 
issue? [SEC=UNCLASSIFIED]

We're accessibility testing at the moment. We've got some email forms (ie. Put 
in your email address to subscribe - submit) that do not currently submit if 
you press enter.
Personally I feel this should be an accessibility issue, but I am finding it 
difficult to locate any solid documentation to back up my claim. I've had the 
argument put to me that a keyboard only user could still tab to the submit 
button, then press enter, but this seems very unintuitive to me to force users 
to do this.

I've also had put to me that some users get confused if they want to put line 
breaks in a field and submit by accident... and so to be consistent pressing 
enter should never submit a form. (data entry people would love that one :P)

Is submitting by pressing enter from a form best practice, or just common 
practice? Is it an accessibility problem? ... and to what degree?


***
WARNING: The information contained in this email may be confidential.
If you are not the intended recipient, any use or copying of any part
of this information is unauthorised. If you have received this email in
error, we apologise for any inconvenience and request that you notify
the sender immediately and delete all copies of this email, together
with any attachments.
***


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

Re: [WSG] Is pressing Enter to submit (or not) on forms an accessability issue? [SEC=UNCLASSIFIED]

2009-10-20 Thread Julia . Dalbo
Return Receipt
   
   Your   Re: [WSG] Is pressing Enter to submit (or not) on forms an   
   document:  accessability issue? [SEC=UNCLASSIFIED]  
   
   wasJulia Dalbo/ACT/IMMI/AU  
   received
   by: 
   
   at:21/10/2009 11:10:40 AM   
   







Important Notice: If you have received this email by mistake, please advise
the sender and delete the message and attachments immediately.  This email,
including attachments, may contain confidential, sensitive, legally privileged
and/or copyright information.  Any review, retransmission, dissemination
or other use of this information by persons or entities other than the
intended recipient is prohibited.  DIAC respects your privacy and has
obligations under the Privacy Act 1988.  The official departmental privacy
policy can be viewed on the department's website at www.immi.gov.au.  See:
http://www.immi.gov.au/functional/privacy.htm


-



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



Re: [WSG] Is pressing Enter to submit (or not) on forms an accessability issue? [SEC=UNCLASSIFIED]

2009-10-20 Thread Nathanael Boehm
Hi Chris,

I'm not sure I'd agree with Jason on if it's a native browser
behaviour/function then it's accessible. I see what he's getting at and
technically it's accessible, just as progressive enhancement is box-ticking
accessibility ... but I believe you'd have to test it to determine whether
it's accessible or not.

It depends on the context of the form, what instructional text has been
provided to the user, their expectations of that particular form on that
page in the context of that particular web site. It's a unique situation and
the provision of Enter key submission or suppression could swing both ways.

Does the Enter key submit on other forms? Does it submit or cancel? Is the
behaviour consistent across the site? Do you differentiate between single
field forms and full page forms?

Nathanael Boehm
http://www.purecaffeine.com/about/
Canberra, Australia
0409 288 464


On Wed, Oct 21, 2009 at 11:03 AM, ja...@flexewebs.com wrote:

 Hi Chris,

 The submission by pressing enter is a native browser behaviour, hence is
 not an accessibility issue.

 You will only be able to submit via enter from an input field and not from
 a textarea, which you have to tab out of and then hit enter.

 So I doubt you will find any references to back-up your claim. If you do,
 send it through so we can debunk it. :-D

 Best,

 Jason

 Sent from my BlackBerry® wireless device
 --
 *From: * Chris Vickery chris.vick...@privacy.gov.au
 *Date: *Wed, 21 Oct 2009 10:20:51 +1100
 *To: *...@webstandardsgroup.orgwsg@webstandardsgroup.org
 *Subject: *[WSG] Is pressing Enter to submit (or not) on forms an
 accessability issue? [SEC=UNCLASSIFIED]

  We’re accessibility testing at the moment. We’ve got some email forms
 (ie. Put in your email address to subscribe - submit) that do not currently
 submit if you press enter.

 Personally I feel this should be an accessibility issue, but I am finding
 it difficult to locate any solid documentation to back up my claim. I’ve had
 the argument put to me that a keyboard only user could still tab to the
 submit button, then press enter, but this seems very unintuitive to me to
 force users to do this.



 I’ve also had put to me that some users get confused if they want to put
 line breaks in a field and submit by accident... and so to be consistent
 pressing enter should never submit a form. (data entry people would love
 that one :P)



 Is submitting by pressing enter from a form best practice, or just common
 practice? Is it an accessibility problem? ... and to what degree?


 ***
 WARNING: The information contained in this email may be confidential.
 If you are not the intended recipient, any use or copying of any part
 of this information is unauthorised. If you have received this email in
 error, we apologise for any inconvenience and request that you notify
 the sender immediately and delete all copies of this email, together
 with any attachments.
 ***

 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: memberh...@webstandardsgroup.org
 ***
 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: memberh...@webstandardsgroup.org
 ***



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


Re: [WSG] Is pressing Enter to submit (or not) on forms an accessability issue? [SEC=UNCLASSIFIED]

2009-10-20 Thread lisa . kerrigan
Return Receipt
   
   Your   Re: [WSG] Is pressing Enter to submit (or not) on forms an   
   document:  accessability issue? [SEC=UNCLASSIFIED]  
   
   wasLisa Kerrigan/StateDevPolicy/DSD 
   received
   by: 
   
   at:21/10/2009 11:30:58 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  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: memberh...@webstandardsgroup.org
***



Re: [WSG] Is pressing Enter to submit (or not) on forms an accessability issue? [SEC=UNCLASSIFIED]

2009-10-20 Thread Mark Gladman
Hi all,

It's probably also worth mentioning that browsers such as Lynx don't
use enter to submit a form unless you have focus on the submit
button itself. Hitting enter will progress the user through the
different input fields until you reach the submit button, and only
then will hitting enter trigger the submission.

You do need to be careful if you're using some form of scripting to
submit a form too - especially if you're providing instructional text
relating to that functionality incase the user has scripting disabled
etc.

Hope this is of some help.

Mark Gladman
Multimedia Analyst
The Learning Federation
PO Box 177, Carlton South VIC 3053 AUSTRALIA 
Ph:  +613 9657 9734 
Fax: +613 9910 9840 


This email and any files transmitted with it (Email) is intended
solely for the individual or entity to whom it is addressed and may be
confidential and also may be legally privileged. If you are not the
intended recipient or the person responsible for delivering the Email to
the intended recipient, you are prohibited from disclosing, copying or
using the information contained in it or taking any action in reliance
upon it. If you have received this email in error, please notify
postmas...@curriculum.edu.au by return email and delete this Email from
your computer.
This Email represents the views of the individual sender, which do not
necessarily reflect those of Curriculum Corporation except where the
sender expressly states otherwise.
It is your responsibility to scan this Email and any files transmitted
with it for viruses or any other defects. 
Curriculum Corporation will not be liable for any loss, damage or
consequence caused directly or indirectly by this Email.



On Wed, 21 Oct 2009 11:24:47 +1100
Nathanael Boehm n...@purecaffeine.com wrote:

 Hi Chris,
 
 I'm not sure I'd agree with Jason on if it's a native browser
 behaviour/function then it's accessible. I see what he's getting at
 and technically it's accessible, just as progressive enhancement is
 box-ticking accessibility ... but I believe you'd have to test it to
 determine whether it's accessible or not.
 
 It depends on the context of the form, what instructional text has
 been provided to the user, their expectations of that particular form
 on that page in the context of that particular web site. It's a
 unique situation and the provision of Enter key submission or
 suppression could swing both ways.
 
 Does the Enter key submit on other forms? Does it submit or cancel?
 Is the behaviour consistent across the site? Do you differentiate
 between single field forms and full page forms?
 
 Nathanael Boehm
 http://www.purecaffeine.com/about/
 Canberra, Australia
 0409 288 464
 
 
 On Wed, Oct 21, 2009 at 11:03 AM, ja...@flexewebs.com wrote:
 
  Hi Chris,
 
  The submission by pressing enter is a native browser behaviour,
  hence is not an accessibility issue.
 
  You will only be able to submit via enter from an input field and
  not from a textarea, which you have to tab out of and then hit
  enter.
 
  So I doubt you will find any references to back-up your claim. If
  you do, send it through so we can debunk it. :-D
 
  Best,
 
  Jason
 
  Sent from my BlackBerry® wireless device
  --
  *From: * Chris Vickery chris.vick...@privacy.gov.au
  *Date: *Wed, 21 Oct 2009 10:20:51 +1100
  *To: *...@webstandardsgroup.orgwsg@webstandardsgroup.org
  *Subject: *[WSG] Is pressing Enter to submit (or not) on forms an
  accessability issue? [SEC=UNCLASSIFIED]
 
   We’re accessibility testing at the moment. We’ve got some email
  forms (ie. Put in your email address to subscribe - submit) that
  do not currently submit if you press enter.
 
  Personally I feel this should be an accessibility issue, but I am
  finding it difficult to locate any solid documentation to back up
  my claim. I’ve had the argument put to me that a keyboard only user
  could still tab to the submit button, then press enter, but this
  seems very unintuitive to me to force users to do this.
 
 
 
  I’ve also had put to me that some users get confused if they want
  to put line breaks in a field and submit by accident... and so to
  be consistent pressing enter should never submit a form. (data
  entry people would love that one :P)
 
 
 
  Is submitting by pressing enter from a form best practice, or just
  common practice? Is it an accessibility problem? ... and to what
  degree?
 
 
  ***
  WARNING: The information contained in this email may be
  confidential. If you are not the intended recipient, any use or
  copying of any part of this information is unauthorised. If you
  have received this email in error, we apologise for any
  inconvenience and request that you notify the sender immediately
  and delete all copies of this email, together 

Re: [WSG] Is pressing Enter to submit (or not) on forms an accessability issue? [SEC=UNCLASSIFIED]

2009-10-20 Thread Jason Grant
This issue has very little (if anything) to do with accessibility. The
functionality in question is accessible via hitting a button or hitting an
enter key.
Perhaps it would be better to ask whether the enter functionality is usable
and whether it might cause annoyances for users who are not familiar with
ancient, default browser presets?
Thanks,
Jason

On Wed, Oct 21, 2009 at 1:24 AM, Nathanael Boehm n...@purecaffeine.comwrote:

 Hi Chris,

 I'm not sure I'd agree with Jason on if it's a native browser
 behaviour/function then it's accessible. I see what he's getting at and
 technically it's accessible, just as progressive enhancement is box-ticking
 accessibility ... but I believe you'd have to test it to determine whether
 it's accessible or not.

 It depends on the context of the form, what instructional text has been
 provided to the user, their expectations of that particular form on that
 page in the context of that particular web site. It's a unique situation and
 the provision of Enter key submission or suppression could swing both ways.

 Does the Enter key submit on other forms? Does it submit or cancel? Is the
 behaviour consistent across the site? Do you differentiate between single
 field forms and full page forms?

 Nathanael Boehm
 http://www.purecaffeine.com/about/
 Canberra, Australia
 0409 288 464


 On Wed, Oct 21, 2009 at 11:03 AM, ja...@flexewebs.com wrote:

 Hi Chris,

 The submission by pressing enter is a native browser behaviour, hence is
 not an accessibility issue.

 You will only be able to submit via enter from an input field and not from
 a textarea, which you have to tab out of and then hit enter.

 So I doubt you will find any references to back-up your claim. If you do,
 send it through so we can debunk it. :-D

 Best,

 Jason

 Sent from my BlackBerry® wireless device
 --
 *From: * Chris Vickery chris.vick...@privacy.gov.au
 *Date: *Wed, 21 Oct 2009 10:20:51 +1100
 *To: *...@webstandardsgroup.orgwsg@webstandardsgroup.org
 *Subject: *[WSG] Is pressing Enter to submit (or not) on forms an
 accessability issue? [SEC=UNCLASSIFIED]

  We’re accessibility testing at the moment. We’ve got some email forms
 (ie. Put in your email address to subscribe - submit) that do not currently
 submit if you press enter.

 Personally I feel this should be an accessibility issue, but I am finding
 it difficult to locate any solid documentation to back up my claim. I’ve had
 the argument put to me that a keyboard only user could still tab to the
 submit button, then press enter, but this seems very unintuitive to me to
 force users to do this.



 I’ve also had put to me that some users get confused if they want to put
 line breaks in a field and submit by accident... and so to be consistent
 pressing enter should never submit a form. (data entry people would love
 that one :P)



 Is submitting by pressing enter from a form best practice, or just common
 practice? Is it an accessibility problem? ... and to what degree?


 ***
 WARNING: The information contained in this email may be confidential.
 If you are not the intended recipient, any use or copying of any part
 of this information is unauthorised. If you have received this email in
 error, we apologise for any inconvenience and request that you notify
 the sender immediately and delete all copies of this email, together
 with any attachments.
 ***

 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: memberh...@webstandardsgroup.org
 ***
 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: memberh...@webstandardsgroup.org
 ***



 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: memberh...@webstandardsgroup.org
 ***




-- 
Jason Grant BSc, MSc
CEO, Flexewebs Ltd.
www.flexewebs.com
ja...@flexewebs.com
+44 (0)7748 591 770
Company no.: 5587469

www.flexewebs.com/semantix
www.twitter.com/flexewebs
www.linkedin.com/in/flexewebs


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


RE: [WSG] Is pressing Enter to submit (or not) on forms an accessability issue? [SEC=UNCLASSIFIED]

2009-10-20 Thread Chris Vickery
Thanks Jason,
In this case it's for an input field, not a textarea, and enter will still not 
submit (unless you tab out) so in this case makes it contrary to 'native 
browser behaviour'.
Essentially our input fields would, (although they identify themselves as input 
fields) would behave like textareas, without line breaks.

I'm not really familiar with using a text to speech reader, but that sounds 
messy to me. Interestingly the source itself looks pretty straight forward:

div id=abc-form class=form
form name=abcform id=abcform method=post action= 
input type=text name=abcform[email1] value= id=email1 class=text 
/input type=submit name=form[subscribebutton1] value=Subscribe 
id=subscribebutton1  /
/form
/div

There must be something buried in the styling causing this behaviour.
Chris

From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On 
Behalf Of ja...@flexewebs.com
Sent: Wednesday, 21 October 2009 11:03 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Is pressing Enter to submit (or not) on forms an 
accessability issue? [SEC=UNCLASSIFIED]

Hi Chris,

The submission by pressing enter is a native browser behaviour, hence is not an 
accessibility issue.

You will only be able to submit via enter from an input field and not from a 
textarea, which you have to tab out of and then hit enter.

So I doubt you will find any references to back-up your claim. If you do, send 
it through so we can debunk it. :-D

Best,

Jason

Sent from my BlackBerry(r) wireless device


From: Chris Vickery chris.vick...@privacy.gov.au
Date: Wed, 21 Oct 2009 10:20:51 +1100
To: wsg@webstandardsgroup.orgwsg@webstandardsgroup.org
Subject: [WSG] Is pressing Enter to submit (or not) on forms an accessability 
issue? [SEC=UNCLASSIFIED]

We're accessibility testing at the moment. We've got some email forms (ie. Put 
in your email address to subscribe - submit) that do not currently submit if 
you press enter.
Personally I feel this should be an accessibility issue, but I am finding it 
difficult to locate any solid documentation to back up my claim. I've had the 
argument put to me that a keyboard only user could still tab to the submit 
button, then press enter, but this seems very unintuitive to me to force users 
to do this.

I've also had put to me that some users get confused if they want to put line 
breaks in a field and submit by accident... and so to be consistent pressing 
enter should never submit a form. (data entry people would love that one :P)

Is submitting by pressing enter from a form best practice, or just common 
practice? Is it an accessibility problem? ... and to what degree?

***
WARNING: The information contained in this email may be confidential.
If you are not the intended recipient, any use or copying of any part
of this information is unauthorised. If you have received this email in
error, we apologise for any inconvenience and request that you notify
the sender immediately and delete all copies of this email, together
with any attachments.
***

***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


***
WARNING: The information contained in this email may be confidential.
If you are not the intended recipient, any use or copying of any part
of this information is unauthorised. If you have received this email in
error, we apologise for any inconvenience and request that you notify
the sender immediately and delete all copies of this email, together
with any attachments.
***


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


Re: [WSG] Is pressing Enter to submit (or not) on forms an accessability issue? [SEC=UNCLASSIFIED]

2009-10-20 Thread mark . greed
Return Receipt
   
   Your   Re: [WSG] Is pressing Enter to submit (or not) on forms an   
   document:  accessability issue? [SEC=UNCLASSIFIED]  
   
   wasmark.gr...@centrelink.gov.au 
   received
   by: 
   
   at:21/10/2009 16:21:24  
   





**
IMPORTANT:  This e-mail is intended for the use of the addressee and may 
contain information that is confidential, commercially valuable or subject to 
legal or parliamentary privilege.  If you are not the intended recipient you 
are notified that any review, re-transmission, disclosure, use or dissemination 
of this communication is strictly prohibited by several Commonwealth Acts of 
Parliament.  If you have received this communication in error please notify the 
sender immediately and delete all copies of this transmission together with any 
attachments.
**



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***