Aide urgente des experts svp

Services63000 · 19 Novembre 2009

Bonsoir j'ai été sur le validator w3c, j'ai 27 erreurs et 3 warning. J'ai activé l'option Clean up Markup with HTML Tidy.

Après m'indiquer les erreurs que je comprend pas très bien, html tidy me reproduit le code source propre.

Dans ce code propre le </head> se situe bien après les balises méta ??? je ne comprend pas pourquoi??

D'autre part dans le code propre il y a le symbole ? sur de lettres des mots.

Je donne donc une copie de ce que w3c validator me dit avec à la fin le code source "propre" pour savoir ce que vous pensez de celui-ci en rapport notamment à ce que j'ai émis ci-dessus.

Voici mon site : http://www.services-informatiques-63.fr

Merci bien de vos éclaircissements.

Attention c'est un peut long lol

Code:

↑ Top
Validation Output: 27 Errors

   1. Warning Line 7, Column 93: NET-enabling start-tag requires SHORTTAG YES

      …gzjeocBfj-CR68bX_y_F9XLjm28s-XKCfo" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
   2. Error Line 7, Column 94: character data is not allowed here

      …zjeocBfj-CR68bX_y_F9XLjm28s-XKCfo" />

      ✉

      You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
          * putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
          * forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
          * using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
   3. Warning Line 19, Column 65: NET-enabling start-tag requires SHORTTAG YES

      …enerator" Content="IziSpot 4.31 (http://www.izispot.com)" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
   4. Error Line 19, Column 65: document type does not allow element "META" here

      …enerator" Content="IziSpot 4.31 (http://www.izispot.com)" />

      ✉

      The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

      One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
   5. Warning Line 20, Column 73: NET-enabling start-tag requires SHORTTAG YES

      …e" content="text/html; charset=iso-8859-1" />

      ✉

      The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
   6. Error Line 20, Column 73: document type does not allow element "META" here

      …e" content="text/html; charset=iso-8859-1" />

      ✉

      The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

      One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
   7. Error Line 24, Column 46: invalid comment declaration: found name character outside comment but inside comment declaration

      <!-----------les plugin----------------------->

      ✉
   8. Info Line 24: comment declaration started here

      ><!-----------les plugin----------------------->

   9. Error Line 38, Column 46: invalid comment declaration: found name character outside comment but inside comment declaration

      <!-----------les plugin----------------------->

      ✉
  10. Info Line 38: comment declaration started here

      ><!-----------les plugin----------------------->

  11. Error Line 41, Column 23: document type does not allow element "STYLE" here

      <style type="text/css">

      ✉

      The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

      One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
  12. Error Line 92, Column 7: end tag for element "HEAD" which is not open

      </head>

      ✉

      The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

      If this error occurred in a script section of your document, you should probably read this FAQ entry.
  13. Error Line 99, Column 16: Attribute "ONRESIZE" is not a valid attribute. Did you mean "noresize" or "onreset"?

      <body onresize='LockNegPosCharte()' onload=' initialise_traduction();'>

      ✉

      You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

      This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

      How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
  14. Error Line 99, Column 71: document type does not allow element "BODY" here

      …sCharte()' onload=' initialise_traduction();'>

      ✉

      The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

      One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
  15. Error Line 118, Column 28: Attribute "HEIGHT" is not a valid attribute. Did you mean "height"?

      <table width="100%" height="100%" cellpadding="0" cellspacing="0" border="0">

      ✉

      You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

      This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

      How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
  16. Error Line 119, Column 69: required attribute "ALT" not specified

      …valign="top"><img src='image_003.jpg' id='logo'></td></tr>

      ✉

      The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

      Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
  17. Error Line 127, Column 16: an attribute value must be a literal unless it contains only name characters

      <P><FONT color=#333333><FONT size=3><FONT color=#cccccc><STRONG>Services Informa

      ✉

      You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
  18. Error Line 127, Column 49: an attribute value must be a literal unless it contains only name characters

      …or=#333333><FONT size=3><FONT color=#cccccc><STRONG>Services Informatiques 63

      ✉

      You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
  19. Error Line 128, Column 16: an attribute value must be a literal unless it contains only name characters

      <P><FONT color=#333333></FONT></P>

      ✉

      You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
  20. Error Line 129, Column 16: an attribute value must be a literal unless it contains only name characters

      <P><FONT color=#333333><FONT color=#cccccc><FONT size=3>I</FONT><FONT size=3>nit

      ✉

      You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
  21. Error Line 129, Column 36: an attribute value must be a literal unless it contains only name characters

      <P><FONT color=#333333><FONT color=#cccccc><FONT size=3>I</FONT><FONT size=3>nit

      ✉

      You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
  22. Error Line 131, Column 16: an attribute value must be a literal unless it contains only name characters

      <P><FONT color=#333333><FONT color=#cccccc size=3>La création de <STRONG>sites</

      ✉

      You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
  23. Error Line 131, Column 36: an attribute value must be a literal unless it contains only name characters

      <P><FONT color=#333333><FONT color=#cccccc size=3>La création de <STRONG>sites</

      ✉

      You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
  24. Error Line 133, Column 16: an attribute value must be a literal unless it contains only name characters

      <P><FONT color=#333333></FONT></P>

      ✉

      You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
  25. Error Line 134, Column 16: an attribute value must be a literal unless it contains only name characters

      <P><FONT color=#333333><FONT color=#cccccc size=3>Nous avons décidez de vous pro

      ✉

      You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
  26. Error Line 134, Column 36: an attribute value must be a literal unless it contains only name characters

      <P><FONT color=#333333><FONT color=#cccccc size=3>Nous avons décidez de vous pro

      ✉

      You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
  27. Error Line 136, Column 67: an attribute value must be a literal unless it contains only name characters

      … auto 0cm" class=mcecontentbodygreen><FONT color=#333333></FONT></P>

      ✉

      You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
  28. Error Line 137, Column 67: an attribute value must be a literal unless it contains only name characters

      …ass=mcecontentbodygreen><FONT color=#333333><FONT size=2><FONT size=3><FONT c

      ✉

      You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
  29. Error Line 137, Column 113: an attribute value must be a literal unless it contains only name characters

      …ONT size=2><FONT size=3><FONT color=#cccccc>Vous pouvez nous contacter au&nbs

      ✉

      You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
  30. Error Line 146, Column 162: required attribute "ALT" not specified

      … width='960' height='560' border='0'></div>

      ✉

      The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

      Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
  31. Error Line 150, Column 153: required attribute "ALT" not specified

      …jpg' width='0' height='0' border='0'></div>

      ✉

      The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

      Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
  32. Error Line 152, Column 30: required attribute "TYPE" not specified

      <script language="javascript">

      ✉

      The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

      Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

↑ Top
Cleaned-up Source Listing with "Tidy"

Below is the cleaned up markup for your document, as processed through HTML Tidy.

Tidy is a third-party software not developed at W3C, and its output is provided without any guarantee.

    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content="HTML Tidy for Linux (vers 6 November 2007), see http://www.w3.org">
<meta name="google-site-verification" content="mxIYJXQglgzjeocBfj-CR68bX_y_F9XLjm28s-XKCfo">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<meta http-equiv="content-langage" content="fr">
<title>services informatiques 63 - services informatiques clermont ferrand - depannage informatique</title>
<meta name="description" content="Informatique � domicile sur Clermont Ferrand et son agglom�ration. Assistance, Formations, D�pannage, Cr�ations de sites... Le tout � votre domicile o� bureau. Les services informatiques en Auvergne.">
<meta name="keywords" content="informatique � domicile, services informatiques, services informatiques clermont ferrand, services informatiques 63, depannage informatique, depannage informatique clermont ferrand, aide � domicile, formations informatiques, formations informatiques clermont ferrand, creations de sites, creations de sites clermont ferrand, assistance informatique, installation mat�riel informatique, optimisation">
<meta name="identifier-url" content="http://www.services-informatiques-63.fr">
<meta name="author" content="Anthony Dechappe">
<meta name="reply-to" content="servicesinformatiques63@yahoo.fr">
<meta name="copyright" content="� 2009">
<meta name="robots" content="index,follow,all">
<meta name="generator" content="IziSpot 4.31 (http://www.izispot.com)">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<script type="text/JavaScript" src="global_006.js">
</script>
<script type="text/JavaScript" src="language_007.js">
</script>
<script type="text/JavaScript">
var AjaxImgLoading="<img src='loading_002.gif' border='0'>";
</script>
<script type="text/JavaScript" src="Ajax_008.js">
</script>
<script type="text/JavaScript">
var dmWorkPath=""
</script>
<script type="text/JavaScript" src="dmenu_009.js">
</script>
<script type="text/JavaScript" src="dmenu_dyn_010.js">
</script>
<script type="text/JavaScript" src="dmenu_popup_011.js">
</script>
<script type="text/JavaScript" src="dmenu_add_012.js">
</script>
<style type="text/css">
<!--

td {color:#FFFFFF;font-family:Arial;font-size:9pt;text-decoration:none;}
a:link {color:#FFFFFF;font-family:Arial;font-size:9pt;text-decoration:none;}
a:visited {color:#FFFFFF;font-family:Arial;font-size:9pt;text-decoration:none;}
a:active {color:#FFFFFF;font-family:Arial;font-size:9pt;text-decoration:none;}
a:hover {color:#FFFFFF;font-family:Arial;font-size:9pt;text-decoration:none;}
body {background-color:#FFFFFF;background-image: url(image_030.jpg);}
.champ {color: #FFFFFF;font-family:Arial;font-size:9pt;text-decoration:none;;background-color: #000000;border: 1px solid #FFFFFF;}
Lcourant{100%}
Edition{color:#000000;background-color:#FFFFFF;font-family:Arial;font-size:9pt;text-decoration:none;} 

-->
</style>

<script type="text/JavaScript">
<!--
function OpenWindow(URL,nom_win,parametres,largeur,hauteur)
{
var gauche = (screen.width - largeur)/2;
var haut =  (screen.height - hauteur)/2;
if (screen.width - largeur<1) {gauche=0}
if (screen.height - hauteur<1) {hauteur=0}
if (hauteur!="" || largeur!="") {parametres=parametres+',left='+gauche+',top='+haut}
try
        {w.close()}
catch (ex)
        {
        }
w=window.open(URL,nom_win,parametres);  
}

function JumpMenu(cible,selectObj,restore)
{ 
eval(cible+".location='"+selectObj.options[selectObj.selectedIndex].value+"'");
if (restore){selectObj.selectedIndex=0};
}




//-->
</script>
<style type="text/css">
 div.c14 {position:absolute;width:960px;height:560px;left:50%;margin-left:-480px;top:50%;margin-top:-280px;}
 div.c13 {position:absolute; left:0px; top:0px; width:0px; height:0px; z-index:1}
 div.c12 {position:absolute; left:120px; top:145px; width:825px; height:17px; z-index:67; overflow:visible;}
 div.c11 {position:absolute; left:0px; top:0px; width:960px; height:560px; z-index:65}
 div.c10 {position:absolute; left:911px; top:1px; width:45px; height:15px; z-index:70; overflow:visible;}
 span.c9 {color: #000000; font-family: Arial; font-size: 9pt; text-decoration: none}
 div.c8 {position:absolute; left:27px; top:189px; width:908px; height:350px; z-index:69; overflow:auto;}
 p.c7 {MARGIN: auto 0cm; color: #333333}
 span.c6 {color: #CCCCCC; font-size: 80%}
 span.c5 {font-size: 120%}
 p.c4 {MARGIN: auto 0cm}
 p.c3 {color: #333333}
 span.c2 {color: #CCCCCC}
 div.c1 {position:absolute; left:775px; top:26px; width:162px; height:75px; z-index:68; overflow:visible;}
</style>
</head>
<!--=========les plugin=====================-->
<!--=========les plugin=====================-->
<!--ACTUA91|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||-->
<body>
<noscript><!--Javascript Menu Link for no script browser-->
<br>
<a href='accueil_019.htm'>Accueil |</a><br>
<a href='contact_020.htm'>Contact |</a><br>
<a href='depannage_021.htm'>D�pannage |</a><br>
<a href='formation_023.htm'>Formation |</a><br>
<a href='lexique_025.htm'>Lexique |</a><br>
<a href='tarifs_027.htm'>Tarifs |</a><br>
<a href='nos_engagements_028.htm'>Nos engagements |</a><br>
<a href='qui_sommes_nous_029.htm'>Qui sommes nous</a></noscript>
<div id='PosCharte' class='c14'>
<div id='obj_88' class='c1'>
<table width="100%" cellpadding="0" cellspacing="0" border="0">
<tr>
<td align="left" valign="top"><img src='image_003.jpg' id='logo' alt="** PLEASE DESCRIBE THIS IMAGE **"></td>
</tr>
</table>
</div>
<div id='obj_89' class='c8'>
<table border='0' cellpadding='0' cellspacing='0' width='100%' align='center'>
<tr>
<td><!--ACTUA14||||||||||||||-->
<p class="c3"><span class="c2"><strong>Services Informatiques 63  </strong>propose diff�rents services informatiques sur Clermont-Ferrand et son agglom�ration :</span></p>
<p class="c3"><span class="c2"><span>I</span><span>nitation � l'informatique ( <strong>tout niveaux</strong> ), Assistance, D�pannage, Formations, Maintenance des syst�mes, Optimisation, Installation de votre mat�riel et configuration, R�cup�ration de donn�es...</span><span> </span></span></p>
<p> </p>
<p class="c3"><span class="c2">La cr�ation de <strong>sites</strong> dynamiques pour <strong>TPE</strong>, <strong>Ind�pendants</strong>, <strong>Commer�ants</strong>, <strong>Artisans</strong> fait partie de nos domaines de comp�tences, avec contrats de mise � jours mensuelles ou annuelles.</span></p>
<p> </p>
<p class="c3"><span class="c2">Nous avons d�cidez de vous proposer des <strong>prix bas</strong> pour permettre � l'ensemble de la population d'acc�der � nos prestations.</span></p>
<p> </p>
<p class="mcecontentbodygreen c4"></p>
<p class="mcecontentbodygreen c7"><span class="c6">Vous pouvez nous contacter au   <span class="c5"><strong>04.73.78.95.33</strong></span></span></p>
</td>
</tr>
</table>
</div>
<div id='obj_90' class='c10'>
<table width="100%" cellpadding="0" cellspacing="0" border="0">
<tr>
<td align="left" valign="top"><span class="copyright c9"><a href='http://www.izispot.com' target='_blank'>�</a> 2009</span></td>
</tr>
</table>
</div>
<div id='obj_91' class='c11'><img src='image_004.htm' width='960' height='560' border='0' alt="** PLEASE DESCRIBE THIS IMAGE **"></div>
<div id='obj_92' class='c12'><script type="text/javascript" src="config_menu_013.js">
</script></div>
<div id='obj_94' class='c13'><img src='image_005.jpg' width='0' height='0' border='0' alt="** PLEASE DESCRIBE THIS IMAGE **"></div>
</div>
<script language="javascript" type="text/javascript">

initialise_traduction();
</script>
</body>
</html>

    

↑ Top

    * Home |
    * About... |
    * News |
    * Docs |
    * Help & FAQ |
    * Feedback |
    * Contribute |

W3COpen-Source

I heart Validator logo

This service runs the W3C Markup Validator, v0.8.5.

Copyright © 1994-2009 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member priv

jcaron · 19 Novembre 2009

Sérieusement, c'était pas la peine de copier-coller tout ça, tu peux éditer ton message et virer tout ça, ça ne sert à rien.

Quelques-unes des erreurs:
- ton code est indiqué comme étant du HTML 4.01, et tu utilises des tags "auto-fermants" XML (<truc .../>). En HTML ça n'existe pas. Pour les tags qui doivent être fermés, c'est <truc...></truc>, pour ceux qui se ferment tous-seuls c'est <truc...>

- tu finis ton head, puis tu mets des styles, des scripts, et tu finis de nouveau ton head

- il est fortement conseillé de toujours mettre les valeurs des attributs entre guillemets. Dans certains cas c'est obligatoire, comme dans le cas où tu as un "#". D'ailleurs les tags <font color...> c'est un peu passé, et le mélange de ça et du CSS c'est quand même pas terrible. Passe tout en CSS.

- il te manque des attributs "alt" sur tes images

- il te manque un attribut "type" sur un script

Corrige déjà tout ça, dans certains cas certaines erreurs sont juste une conséquence d'une autre, ça devrait s'améliorer.

Jacques.

tryan · 19 Novembre 2009

Salut,
Sans être mesquin, ce qui fait le plus peur se trouve quand même dans la partie Nos engagements de votre site :

Nous sommes spécialisés dans différents domaines :
* Création de sites Internet pour commercants, Independants, TPE..

ok je :arrow:

Services63000 · 19 Novembre 2009

Tryan lol je créer des petits sites et j'ai pas l'ambition d'être un pro en développement c'est ce qui me manque à mon panel, cela dit sa serait utiles si tu as des capacités dedans de m'aider je suis paumé dans mon code source.

Bonne soirée

jcaron · 19 Novembre 2009

@tryan: +1, j'ai failli le dire, mais je dois être de bonne humeur aujourd'hui...

Jacques.

Leonick · 20 Novembre 2009

Services63000 a dit:
Tryan lol je créer des petits sites et j'ai pas l'ambition d'être un pro en développement c'est ce qui me manque à mon panel

et pourquoi ne pas utiliser un CMS ? le code serait ainsi beaucoup plus propre (et plus pro)

bproductiv · 20 Novembre 2009

Services63000 a dit:
je créer des petits sites et j'ai pas l'ambition d'être un pro en développement c'est ce qui me manque à mon panel

Dans ce cas là ne le met pas du tout.

Furtif · 20 Novembre 2009

si tu as des capacités dedans de m'aider je suis paumé dans mon code source.

Tu as un code source generé par izispot, qui est une daube sans nom.... Sans compter les 8 .js dont on se demande ce qu'ils foutent la...

Ce n'est pas un code source, c'est de la soupe...

Trouve un etudiant en informatique qui te fasse une site simple et propre ou passe par un CMS....

mais arrete le massacre...

tryan · 20 Novembre 2009

Services63000, pour commencer, tu pourrais peut être séparé ton style css de ta présentation. Ensuite attribué justement un style aux balises que tu utilises et viré celles qui ne servent à rien:

Code:

<p><font color="#333333"><font size="3"><font color="#CCCCCC"><strong>Services Informatiques 63&nbsp;&nbsp;</strong>propose diff&#233;rents services informatiques sur Clermont-Ferrand et
            son agglom&#233;ration :</font></font></font></p>

Code:

/*style css*/
.toto {color:333333; font-size:12px;}
<!--html-->
<p class="toto"><strong>Services Informatiques 63</strong> propose différents services informatiques sur Clermont-Ferrand et son agglomération :</p>

Éventuellement viré les métatags inutiles (Titre, description voir keywords sont suffisant).
Si tes fichiers .js servent à kedal .. les virer aussi.

Une fois que tu auras fait le tour, il te sera nettement plus facile de voir et comprendre d'où proviennent tes erreurs de validation W3C.

Et puis, change de logiciel :mrgreen: