NOSCRIPT for SCRIPT called in HEAD

Forum Moderators: open

Message Too Old, No Replies

NOSCRIPT for SCRIPT called in HEAD

accessibility alternatives to script

el_roboto

6:15 pm on Mar 2, 2007 (gmt 0)

Hello

Trying to improve the accessibility of a website I'm working on, at the moment WebXACT is flagging up issues wherever I call javascripts.

None of the script is essential to the operation of the site but I still want to understand how to combat this!

I have 3 scripts called in my head and I know that I can't use the noscript tag here so what would be the best way to sort this out?

pageoneresults

6:27 pm on Mar 2, 2007 (gmt 0)

I think this might help...

18.3.2 Hiding script data from user agents
[w3.org...]

P.S. I don't recall ever seeing the use of a <noscript> element within the <head></head>. I don't think you can do that. ;)

encyclo

6:36 pm on Mar 2, 2007 (gmt 0)

The accessibility validator tools will show warnings for such scripts, but only you can judge the pertinence of those warnings. If as you say the scripts aren't required, and the site works without them, you can safely ignore the validator errors.

Accessibility validators are not like markup validators which offer a true pass/fail result. It is currently not possible for an automated tool to make an accurate assessment, so they just give hints on what to check. So don't fall into the trap of making changes or reducing functionality of an accessible site just to work around the deficiencies in the validator. :)

el_roboto

6:40 pm on Mar 2, 2007 (gmt 0)

thats what I was saying, since I can't use the noscript tag in my head, how do I render these script tags in the head as accessible content, other instances called in the body can be made 'accessible' with the noscript tag.

checking that link now

el_roboto

6:42 pm on Mar 2, 2007 (gmt 0)

thanks encyclo

how would you suggest working around the issue where the scripts we're necessary to functionality?