Les erreurs du validator ne viennent plus que des referenceurs (Créer un compte)

  • Statut : non résolu
7 sujets de 1 à 7 (sur un total de 7)
  • Auteur
    Messages
  • #460946
    HeleneR
    Participant
    Maître WordPress
    1545 contributions

    Bonjour,

    Ma configuration WP actuelle
    – Version de WordPress : 2.3.3
    – Thème utilisé : ad clerum
    – Plugins en place : statpress, ddgenerator sitemap, sitemap générator…
    – Nom de l’hebergeur : sivit
    – Adresse du site : http://www.jhp-videoproductions.fr/index.php

    Problème(s) rencontré(s) :

    Ca n’a pas été évident de faire les réglages.
    Je voulais afficher des liens, notamment référenceurs plus discrets. Juste dans une plus petits police…. avec taille de police….
    les liens de fin de pages devaient aussi être plus discrets.
    il vaut peut-être mieux que j’utilise les balise

    ?
    non parce que là, j’ai enlevé toutes les balises “font” et le validateur a semble-t-il apprécié…..

    sinon, toutes les erreurs restantes viennent des balises des annuaires sur lequel j’ai référencé le site. là je ne vois pas trop comment me dépatouiller.

    Validation Output:  13 Errors
    
       1. Error Line 134, Column 1119: there is no attribute “alt” .
    
          …e/http://www.refsolution.com’);” alt=”referencement” title=”referencement”>ré
    
          ✉
    
          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.
       2. Error Line 139, Column 285: required attribute “alt” not specified .
    
          …” width=”90″ border=”0″ height=”15″ /></a></td>
    
          ✉
    
          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>.
       3. Error Line 142, Column 25: there is no attribute "scrolldelay" .
    
          <td><marquee scrolldelay="10" scrollamount="1" style="border: 0pt none ; font-we
    
          ✉
    
          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.
       4. Error Line 142, Column 43: there is no attribute "scrollamount" .
    
          …arquee scrolldelay="10" scrollamount="1" style="border: 0pt none ; font-weigh
    
          ✉
    
          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.
       5. Error Line 142, Column 53: there is no attribute "style" .
    
          …olldelay="10" scrollamount="1" style="border: 0pt none ; font-weight: normal;
    
          ✉
    
          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.
       6. Error Line 142, Column 183: element "marquee" undefined .
    
          …ght: 10px; background-color: #655f79"><nobr><font color="#000000"><strong>htt
    
          ✉
    
          You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
              * by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
              * by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
       7. Error Line 142, Column 189: element "nobr" undefined .
    
          …0px; background-color: #655f79"><nobr><font color="#000000"><strong>http://ww
    
          ✉
    
          You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
              * by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
              * by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
       8. Error Line 146, Column 100: required attribute "alt" not specified .
    
          …t none ; width: 80px; height: 15px" /></a><br />
    
          ✉
    
          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>.
       9. Error Line 149, Column 6: required attribute "type" not specified .
    
          <style>.uu a,.uu td,.uu span { font-weight : normal; font-size : 12px; font-fami
    
          ✉
    
          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>.
      10. Error Line 149, Column 6: document type does not allow element "style" here .
    
          <style>.uu a,.uu td,.uu span { font-weight : normal; font-size : 12px; font-fami
    
          ✉
    
          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).
      11. Error Line 151, Column 56: there is no attribute "bordercolor" .
    
          …" width="110" border="0" bordercolor="#c3120c" cellpadding="0" cellspacing="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.
      12. Error Line 151, Column 105: there is no attribute "height" .
    
          …llpadding="0" cellspacing="0" height="22">
    
          ✉
    
          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.
      13. Error Line 153, Column 91: element "marquee" undefined .
    
          …eight="17"><marquee scrolldelay="450">Referencement grauit via l’<a hre
    
          ✉
    
          You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
              * by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
              * by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).

    Merci d'avance de vos aides

    #636141
    Dric
    Participant
    Maître WordPress
    757 contributions

    A priori tu es en XHTML 1.0 Strict, tu devrais peut-être passer en transitional qui est plus permissif.

    #636142
    HeleneR
    Participant
    Maître WordPress
    1545 contributions

    Hum, juste mon incompétence est aussi élevée que les différences entre les navigateurs ont de différences d’affichages….
    Donc, je ne sais pas du tout ce qu’il faudrait que je fasse
    et dans un cas et d’ans l’autre

    #636143
    Dric
    Participant
    Maître WordPress
    757 contributions

    J’avais pas vu, t’es bien en transitional mais pour une raison bizarre ton css ne s’applique pas sous Opera.

    Mmmh, mes maigres compétences ne suffiront pas à résoudre ton souci, désolé…

    #636144
    Lumiere de Lune
    Participant
    Maître WordPress
    19553 contributions

    alt est un attribut valide pour les images, mais pas pour les liens.
    Il est obligatoire pour les images, quitte à être laissé vide, pour des raisons d’accessibilité. Si on ne veut pas mettre d’attribut il faut écrire alt =””

    scrolldelay et scrollamount sont des attributs propréitaires, non reconnus par le w3c

    le “style” doit se définir uniquement à partir des propriétés css, pas dans le code.
    etc… aucune de ces erreurs n’est grave, elles n’empêchent pas un affichage correct.

    Tu ne peux pas vraiment les corriger, sauf à modifier le code fourni par tes partenaires.
    C’est une des raisons pour lesquelles je refuse ce genre de liens, surtout en page d’accueil

    #636145
    HeleneR
    Participant
    Maître WordPress
    1545 contributions

    Tu t’es référencée où Lumière de lune?
    Ton pseudo me fait quelque chose à chaque fois que je le vois. J’avais perso, Lumière du coeur pendant des années sur aol
    🙂 c’était pour l’anecdote

    #636140
    Lumiere de Lune
    Participant
    Maître WordPress
    19553 contributions

    Sur environ 500 annuaires … aucun annuaire ne “vaut” le lien retour sur la page d’accueil 🙂

7 sujets de 1 à 7 (sur un total de 7)
  • Vous devez être connecté pour répondre à ce sujet.