Re[2]: [WSG] E649 The default scripting language must be specified for an intrinsic event:

2008-12-31 Thread Martin Heiden
Tee,

Wednesday, December 31, 2008, 8:52:02 AM, you wrote:

t OK, finally got it working this time. All I needed is adding this :
t meta http-equiv=content-script-type content=text/tcl /

Do you really use TCL in your page? I guess you want to change it to

meta http-equiv=content-script-type content=text/javascript /

Happy New Year!

Martin



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



[WSG] E649 The default scripting language must be specified for an intrinsic event:

2008-12-30 Thread tee
I remember I asked this before, still I am unable to figure out how to  
fix it. It disturbs me not able to fix it as it shows up as an error  
in WAI AA validation; it's not a warning so I am curious to know if  
this will cause accessible difficulty to screen readers.


I have this script in a file

script type=text/javascript
//![CDATA[
function validatePollAnswerIsSelected()
{
var options = $$('input.poll_vote');

for( i in options ) {
if( options[i].checked == true ) {
return true;
}
}
return false;
}
//]]
/script


and the form:

 form id=pollForm action=?php echo $action ? method=post  
onsubmit=return validatePollAnswerIsSelected();



According to W3C:
http://www.w3.org/TR/html401/interact/scripts.html#h-18.2.2.1
The onsubmit event occurs when a form is submitted. It only  
applies to the FORM element.


CT: Consult the type definition for details about case-sensitivity.
If an attribute value is a list, the keys apply to every value in the  
list, unless otherwise indicated.



So vague that I understand every english word yet I haven't a clue  
what it means.


tee


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



Re: [WSG] E649 The default scripting language must be specified for an intrinsic event:

2008-12-30 Thread David Dorward
tee wrote:
 I remember I asked this before, still I am unable to figure out how to
 fix it. 

I spent ages reading and rereading this until I spotted the error
message hiding away in the subject line :)

http://www.w3.org/TR/html4/interact/scripts.html#h-18.2.2.1 is the bit
of the spec that you need.


-- 
David Dorward   http://dorward.me.uk/


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



Re: [WSG] E649 The default scripting language must be specified for an intrinsic event:

2008-12-30 Thread David Dorward
David Dorward wrote:
 tee wrote:
 I remember I asked this before, still I am unable to figure out how to
 fix it. 
 
 I spent ages reading and rereading this until I spotted the error
 message hiding away in the subject line :)
 
 http://www.w3.org/TR/html4/interact/scripts.html#h-18.2.2.1 is the bit
 of the spec that you need.

And upon rereading, I see you've already found that bit of the spec.
Forgive me for responding before I'm properly awake.

If you have a script element, you specify the scripting language it
uses with a type attribute.

You can't do that for an onsubmit attribute, so you need to use meta
data to do it:

META http-equiv=Content-Script-Type content=text/javascript

... or you could use unobtrusive JavaScript and attach the event handler
programatically, which eliminates the need for this.


-- 
David Dorward   http://dorward.me.uk/


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



Re: [WSG] E649 The default scripting language must be specified for an intrinsic event:

2008-12-30 Thread tee


On Dec 30, 2008, at 2:03 AM, David Dorward wrote:


tee wrote:
I remember I asked this before, still I am unable to figure out how  
to

fix it.


I spent ages reading and rereading this until I spotted the error
message hiding away in the subject line :)

http://www.w3.org/TR/html4/interact/scripts.html#h-18.2.2.1 is the bit
of the spec that you need.




Thanks David and sorry for the confusion :-)

OK, finally got it working this time. All I needed is adding this :
meta http-equiv=content-script-type content=text/tcl /

to the head section. I thought I did that last time and the validator  
gave me extra errors. Therefor was looking at the 'onsubmit' example  
this time.


Also, just realized it's not for priority 2  requirement but 1.   
Cynthia Says section 508 passed the checkpoint but  Total Validator  
didn't.


tee




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



RE: [WSG] E649: The default scripting language must be specified for an intrinsic event:

2008-09-01 Thread michael.brockington
I think you will find that this has no direct effect on accessibility.
As I am sure you know, if you rely on these methods for navigation, or
if that select isn't made keyboard-friendly, then that is a problem, but
inline JavaScript on its own is fine. In some circumstances it is better
to have it as an external script file, but only for management reasons,
not for operational reasons, if that makes sense?

Similarly, I think you can afford to ignore that validation warning - I
have yet to come across a browser that tries to run JavaScript as
anything else.

Regards,
Mike

Mike Brockington
Web Development Specialist

www.calcResult.com
www.stephanieBlakey.me.uk
www.edinburgh.gov.uk

This message does not reflect the opinions of any entity other than the
author alone.

-Original Message-
From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of tee
Sent: Sunday, August 31, 2008 1:07 AM
To: wsg@webstandardsgroup.org
Subject: [WSG] E649: The default scripting language must be 
specified for an intrinsic event:

I looked up the reference from W3C, but all I got is a blurry 
picture that makes my head spins.

I added a meta tag:
meta http-equiv=Content-Script-Type content=text/javascript

No effect.


Example of offenders.

   select id=select-language  
onchange=window.location.href=this.value

   li onmouseover=toggleMenu(this,1) 
onmouseout=toggleMenu(this, 0)/li


So my question, what fatal effect it has for accessibility if I can't  
get rid of them?

Thanks!

tee





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



RE: [WSG] E649: The default scripting language must be specified for an intrinsic event:

2008-08-31 Thread Essential eBiz Solutions Ltd
Magento is great in practice, but I've found that the only big thing about
it for my customers is the admin facilities. But for a designer it's a lot
of hard work. I've seen some fantastic examples of what can be done with
Magento and there have been some great features that use jQuery (by far the
easiest javascript ever!). Now that Magento is completely released the main
updates will come from people like us who will develop something for a
client and share it with the community. If you'd like someone to bounce
ideas around with please feel free to contact me off list.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of tee
Sent: 31 August 2008 03:41
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] E649: The default scripting language must be specified
for an intrinsic event:

Hi Anthony,

Thanks for the advice - I know all these by theory :) Problem is in  
reality there are limitation as to how much I can do or if I am  
capable of doing.

I failed to mention, it's for Magento project, which inline scripting  
and prototype are heavily used. I'd been working on various Magento  
themes that I have made lots of effort to make the markup more  
semantically sounds, and stripped out all inline styles, but  
eliminating inline scripting and prototype (magento has written its  
own scripts that also rely on prototype script) isn't something that  
can be easily done even for a proficient js programmer - I guess it  
needs a full house of web developers. There were talk about developing  
jQuery extension for Magento in the Magento community, and that  
hopefully one day those who are favor for jQuery will have alternative  
choice - it dies immediately as nobody wants to make effort but expect  
someone else do it for them, for free. Can't blame them, it's just  
human nature.

Anyway, I'd been learning jQuery for a while and have implemented a  
few jQuery features to my themes. Also, just now I was very please to  
see jQuery launches a new site.

I am however, would like to hear from other members who have been  
working on Magento to give some feedback how/if they have made  
improvement on accessibility.

tee

On Aug 30, 2008, at 6:37 PM, Anthony wrote:

 First of all try to avoid in-line scripting. You could make great  
 use of jquery, mootools or any other library.

 Make sure to provide an alternative method (buttons, links, etc) to  
 make things accessible for javascript disabled browsers, screen  
 readers, etc.

 Regards,
 Anthony.

 Sent from my iPhone!

 On 31/08/2008, at 10:06 AM, tee [EMAIL PROTECTED] wrote:

 I looked up the reference from W3C, but all I got is a blurry  
 picture that makes my head spins.

 I added a meta tag:
 meta http-equiv=Content-Script-Type content=text/javascript

 No effect.


 Example of offenders.

 select id=select-language  
 onchange=window.location.href=this.value

 li onmouseover=toggleMenu(this,1) onmouseout=toggleMenu(this, 
 0)/li


 So my question, what fatal effect it has for accessibility if I  
 can't get rid of them?

 Thanks!

 tee





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



-- 
No virus found in this incoming message.
Checked by AVG. 
Version: 7.5.524 / Virus Database: 270.6.13/1642 - Release Date: 29/08/2008
18:12




***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



[WSG] E649: The default scripting language must be specified for an intrinsic event:

2008-08-30 Thread tee
I looked up the reference from W3C, but all I got is a blurry picture  
that makes my head spins.


I added a meta tag:
meta http-equiv=Content-Script-Type content=text/javascript

No effect.


Example of offenders.

  select id=select-language  
onchange=window.location.href=this.value


  li onmouseover=toggleMenu(this,1) onmouseout=toggleMenu(this, 
0)/li



So my question, what fatal effect it has for accessibility if I can't  
get rid of them?


Thanks!

tee





***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] E649: The default scripting language must be specified for an intrinsic event:

2008-08-30 Thread Anthony
First of all try to avoid in-line scripting. You could make great use  
of jquery, mootools or any other library.


Make sure to provide an alternative method (buttons, links, etc) to  
make things accessible for javascript disabled browsers, screen  
readers, etc.


Regards,
Anthony.

Sent from my iPhone!

On 31/08/2008, at 10:06 AM, tee [EMAIL PROTECTED] wrote:

I looked up the reference from W3C, but all I got is a blurry  
picture that makes my head spins.


I added a meta tag:
meta http-equiv=Content-Script-Type content=text/javascript

No effect.


Example of offenders.

 select id=select-language  
onchange=window.location.href=this.value


 li onmouseover=toggleMenu(this,1) onmouseout=toggleMenu(this, 
0)/li



So my question, what fatal effect it has for accessibility if I  
can't get rid of them?


Thanks!

tee





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



Re: [WSG] E649: The default scripting language must be specified for an intrinsic event:

2008-08-30 Thread tee

Hi Anthony,

Thanks for the advice - I know all these by theory :) Problem is in  
reality there are limitation as to how much I can do or if I am  
capable of doing.


I failed to mention, it's for Magento project, which inline scripting  
and prototype are heavily used. I'd been working on various Magento  
themes that I have made lots of effort to make the markup more  
semantically sounds, and stripped out all inline styles, but  
eliminating inline scripting and prototype (magento has written its  
own scripts that also rely on prototype script) isn't something that  
can be easily done even for a proficient js programmer - I guess it  
needs a full house of web developers. There were talk about developing  
jQuery extension for Magento in the Magento community, and that  
hopefully one day those who are favor for jQuery will have alternative  
choice - it dies immediately as nobody wants to make effort but expect  
someone else do it for them, for free. Can't blame them, it's just  
human nature.


Anyway, I'd been learning jQuery for a while and have implemented a  
few jQuery features to my themes. Also, just now I was very please to  
see jQuery launches a new site.


I am however, would like to hear from other members who have been  
working on Magento to give some feedback how/if they have made  
improvement on accessibility.


tee

On Aug 30, 2008, at 6:37 PM, Anthony wrote:

First of all try to avoid in-line scripting. You could make great  
use of jquery, mootools or any other library.


Make sure to provide an alternative method (buttons, links, etc) to  
make things accessible for javascript disabled browsers, screen  
readers, etc.


Regards,
Anthony.

Sent from my iPhone!

On 31/08/2008, at 10:06 AM, tee [EMAIL PROTECTED] wrote:

I looked up the reference from W3C, but all I got is a blurry  
picture that makes my head spins.


I added a meta tag:
meta http-equiv=Content-Script-Type content=text/javascript

No effect.


Example of offenders.

select id=select-language  
onchange=window.location.href=this.value


li onmouseover=toggleMenu(this,1) onmouseout=toggleMenu(this, 
0)/li



So my question, what fatal effect it has for accessibility if I  
can't get rid of them?


Thanks!

tee





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