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. :)
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.