Re: [WSG] recovering file replace

2009-10-20 Thread akmal adnan
Try System Restore to previous time before the file has been replaced.

Akmal Adnan

On 10/20/09, Luke Hoggett luke.hogg...@gmail.com wrote:
 Hi,

 Sorry you lost your file.

 As a precaution in the future I'd recommend installing some sort of
 version control e.g. svn can seem a bit daunting to install or overkill
 for 1-2 people but in the long run it is well worth it.

 cheers
 L


 Nour Alsafar wrote:
 Hi
 please if anyone can help me i have replaced my current file when
 moving it into the folder with an older one, and i don't know how to
 recover it back, i tried several softwares but none of them are
 helping me out, i'm so streesed i've been working on this flash files
 for day and now it's replaced with a very old old vr. please did
 anyone had the same thing and got their file recoved please help me
 i'm so desperate for a solution ASAP.

 Thanks all in advance

 
 Let us find your next place for you! Need a place to rent, buy or
 share? http://clk.atdmt.com/NMN/go/157631292/direct/01/
 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: memberh...@webstandardsgroup.org
 ***

 --

 Luke Hoggett
 0419 442 807


 ***
 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] Re: More than one H1? - ADMIN

2009-10-20 Thread Andrew Newman

More than one H1 on a page: good or bad?


http://www.youtube.com/watch?v=GIn5qJKU8VM


On 20/10/2009, at 1:09 PM, Russ Weakley wrote:


ADMIN

Hi all,

The conversation has been great, but we are now heading into heated  
discussion and direct attacks - which is unacceptable. Please remain  
civil and receptive or the thread will be closed.


Thanks
Russ
(civility police)




***
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
***

[WSG] Let's stay in touch on LinkedIn

2009-10-20 Thread Dionisis Karampinis
LinkedIn


Dionisis Karampinis requested to add you as a connection on LinkedIn:
--

Nick,

I'd like to add you to my professional network on LinkedIn.

- Dionisis

Accept invitation from Dionisis Karampinis
http://www.linkedin.com/e/7L1XvhOEro1RJ5LtYH3XHbryRcefSR7tSTTS06J/blk/I1519442116_2/pmpxnSRJrSdvj4R5fnhv9ClRsDgZp6lQs6lzoQ5AomZIpn8_cBYScj4Od3gVcjkNiiZzgQVorTFPqOYNczoSejcUc3wLrCBxbOYWrSlI/EML_comm_afe/

View invitation from Dionisis Karampinis
http://www.linkedin.com/e/7L1XvhOEro1RJ5LtYH3XHbryRcefSR7tSTTS06J/blk/I1519442116_2/39vdz4NczgQej4RckALqnpPbOYWrSlI/svi/

--

Why might connecting with Dionisis Karampinis be a good idea?

People Dionisis Karampinis knows can discover your profile:
Connecting to Dionisis Karampinis will attract the attention of LinkedIn users. 
See who's been viewing your profile:

http://www.linkedin.com/e/wvp/inv18_wvmp/

 
--
(c) 2009, LinkedIn Corporation



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

Re: [WSG] Let's stay in touch on LinkedIn

2009-10-20 Thread dionisis karampinis
Sorry to everyone in the group for that!!!this is what happens when
you spend all your day in front the screen :)



2009/10/20 Dionisis Karampinis dkarampi...@gmail.com

  LinkedIn

 Dionisis Karampinis requested to add you as a connection on LinkedIn:

 Nick,

 I'd like to add you to my professional network on LinkedIn.

 - Dionisis

   
 Accepthttp://www.linkedin.com/e/7L1XvhOEro1RJ5LtYH3XHbryRcefSR7tSTTS06J/blk/I1519442116_2/pmpxnSRJrSdvj4R5fnhv9ClRsDgZp6lQs6lzoQ5AomZIpn8_cBYScj4Od3gVcjkNiiZzgQVorTFPqOYNczoSejcUc3wLrCBxbOYWrSlI/EML_comm_afe/
   View
 invitation from Dionisis 
 Karampinishttp://www.linkedin.com/e/7L1XvhOEro1RJ5LtYH3XHbryRcefSR7tSTTS06J/blk/I1519442116_2/39vdz4NczgQej4RckALqnpPbOYWrSlI/S2_svi/


 *WHY MIGHT CONNECTING WITH DIONISIS KARAMPINIS BE A GOOD IDEA?*

 *People Dionisis Karampinis knows can discover your profile*
 Connecting to Dionisis Karampinis will attract the attention of LinkedIn
 users. See who's been viewing your 
 profilehttp://www.linkedin.com/e/wvp/inv18_wvmp/
 .


 © 2009, LinkedIn Corporation

 ***
 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
***


[WSG] Extra space in menu in IE on hover

2009-10-20 Thread Kristine Cummins
Menu on left... on mouseover, the bg color should fill the entire height in
between top and bottom borders and doesn't. There is about a 5 pixel gap. In
FF, it looks fine.

Web: http://esw.sbw.org/
CSS: http://esw.sbw.org/wp-content/plugins/menubar-templates/esw/eswmenu.css

Thanks in advance.


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

Re: [WSG] recovering file replace

2009-10-20 Thread Stuart Foulstone
I'd recommend backing files up.

On Tue, October 20, 2009 2:57 am, Luke Hoggett wrote:
 Hi,

 Sorry you lost your file.

 As a precaution in the future I'd recommend installing some sort of
 version control e.g. svn can seem a bit daunting to install or overkill
 for 1-2 people but in the long run it is well worth it.

 cheers
 L


 Nour Alsafar wrote:
 Hi
 please if anyone can help me i have replaced my current file when
 moving it into the folder with an older one, and i don't know how to
 recover it back, i tried several softwares but none of them are
 helping me out, i'm so streesed i've been working on this flash files
 for day and now it's replaced with a very old old vr. please did
 anyone had the same thing and got their file recoved please help me
 i'm so desperate for a solution ASAP.

 Thanks all in advance

 
 Let us find your next place for you! Need a place to rent, buy or
 share? http://clk.atdmt.com/NMN/go/157631292/direct/01/
 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: memberh...@webstandardsgroup.org
 ***

 --

 Luke Hoggett
 0419 442 807


 ***
 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
***



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

2009-10-20 Thread Chris Vickery
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
***


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] Extra space in menu in IE on hover

2009-10-20 Thread Kepler Gelotte
 Menu on left... on mouseover, the bg color should fill the entire height
in between top and bottom borders and doesn't. There is about a 5 pixel gap.
In FF, it looks fine.



You could try this in eswmenu.css:

 

.eswmenu  li a {

border-bottom: 1px solid #d6dad5;

/* border: 0px solid blue; */

background-color: transparent;

font: bold 13px Palatino Linotype, Garamond, Times New Roman, serif;

color: #8a8989;

display: block;

height: 28px;

line-height: 28px;

margin: 0px auto 0 auto;

padding: 1px 0 14px 0;

text-decoration: none;

vertical-align:top;

}

 

.eswmenu a:visited, .eswmenu a:active {

border-bottom: 1px solid #d6dad5;

color: #8a8989;

}

 

.eswmenu ul li a:hover {

border-bottom: 1px solid #d6dad5;

background: url(bullet-nav.png) no-repeat center 25px;

background-color: #e6f0ed; 

}

 

Best regards,

Kepler Gelotte

Neighbor Webmaster, Inc.

156 Normandy Dr., Piscataway, NJ 08854

 http://www.neighborwebmaster.com www.neighborwebmaster.com

phone/fax: (732) 302-0904

 



***
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
***