Erreurs validator w3c

Question

cochi

2 Apr 2015 à 19:53

Bonjour,
j'ai voulu voir si mes codes étaient valide avec w3c et j'obtiens des messages d'erreurs, seulement c'est en anglais et je n'arrive pas à comprendre...
Voilà les messages d'erreurs : (16 Errors, 12 warning(s))

Notes and Potential Issues

The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.

Warning No Character Encoding Found! Falling back to UTF-8.

None of the standards sources gave any information on the character encoding labeling for this document. Without encoding information it is impossible to reliably validate the document. As a fallback solution, the "UTF-8" encoding was used to read the content and attempt to perform the validation, but this is likely to fail for all non-trivial documents.

Warning Unable to Determine Parse Mode!

The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:
-the MIME Media Type (text/html) can be used for XML or SGML document types
-No known Document Type could be detected
-No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document.
-No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.

As a default, the validator is falling back to SGML mode.

Warning No DOCTYPE found! Checking with default HTML 4.01 Transitional Document Type.

No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax.

The document was checked using a default "fallback" Document Type Definition that closely resembles “HTML 4.01 Transitional”.
Learn how to add a doctype to your document from our FAQ.

No Character encoding declared at document level

No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.
See this tutorial on character encoding for techniques and explanations.

Validation Output: 16 Errors

Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"

<html lang="fr"> The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

Error Line 3, Column 17: there is no attribute "CHARSET"

<meta charset="utf-8"> 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.

Error Line 3, Column 24: required attribute "CONTENT" not specified

<meta charset="utf-8"> 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>.

Warning Line 11, Column 32: NET-enabling start-tag requires SHORTTAG YES

<img src=Images/logo-header.png alt="Logo Coralie" /> For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Error Line 11, Column 32: required attribute "ALT" not specified

<img src=Images/logo-header.png alt="Logo Coralie" /> 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>.

Warning Line 27, Column 16: NET-enabling start-tag requires SHORTTAG YES

<hr/> For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Warning Line 35, Column 77: NET-enabling start-tag requires SHORTTAG YES

…g" class="affiche_fdl"><img src=Images/affcihe-foire.png alt=" " title="Affic…
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Error Line 35, Column 77: required attribute "ALT" not specified

…g" class="affiche_fdl"><img src=Images/affcihe-foire.png alt=" " title="Affic…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>.

Error Line 40, Column 18: ID "BLOC_PAGE" already defined

<div id="bloc_page"> An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

Info Line 9, Column 18: ID "BLOC_PAGE" first defined here

<div id="bloc_page">

Error Line 41, Column 23: value of attribute "ID" must be a single token
<div id="a propos"> This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

Warning Line 43, Column 36: NET-enabling start-tag requires SHORTTAG YES

<img src=Images/Logo-a-propos.png alt="Mon Logo" title="Log…
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Error Line 43, Column 36: required attribute "ALT" not specified

<img src=Images/Logo-a-propos.png alt="Mon Logo" title="Log… 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>.

Error Line 52, Column 66: document type does not allow element "H1" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag

… <a href="" accesskey="h" class="montages"><h1>Les montages</h1></a> The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

Warning Line 54, Column 51: NET-enabling start-tag requires SHORTTAG YES

… <div id="imac"><img src=Images/Imac.png alt="" title="Les montages"/><…
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Error Line 54, Column 51: required attribute "ALT" not specified

… <div id="imac"><img src=Images/Imac.png alt="" title="Les montages"/><…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>.

Error Line 57, Column 68: document type does not allow element "H1" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag

… <a href="" accesskey="i" class="publicites"><h1>Les publicités</h1></a>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

Warning Line 59, Column 54: NET-enabling start-tag requires SHORTTAG YES

… <div id="macbook"><img src=Images/Macbook.png alt="" title="Les publicité…
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Error Line 59, Column 54: required attribute "ALT" not specified

… <div id="macbook"><img src=Images/Macbook.png alt="" title="Les publicité…
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>.

Error Line 64, Column 22: ID "BLOC_PAGE" already defined

<div id="bloc_page">
An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Info Line 9, Column 18: ID "BLOC_PAGE" first defined here

<div id="bloc_page">

Warning Line 66, Column 32: NET-enabling start-tag requires SHORTTAG YES

<img src=Images/logo-footer.png alt="Logo Coralie" /> For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Error Line 66, Column 32: required attribute "ALT" not specified

<img src=Images/logo-footer.png alt="Logo Coralie" />
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>.

Warning Line 78, Column 100: NET-enabling start-tag requires SHORTTAG YES

…ass="fb" accesskey="j"><img src=Images/facebook.png alt="" title="logo Faceboo…
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Error Line 78, Column 100: required attribute "ALT" not specified

…ass="fb" accesskey="j"><img src=Images/facebook.png alt="" title="logo Faceboo…
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>.

Error Line 82, Column 7: end tag for "DIV" omitted, but its declaration does not permit this

</body>
You forgot to close a tag, or you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Info Line 39, Column 5: start tag was here

<div id="container">

Donc voilà je comprends absolument rien, si quelqu'un peut me dire ce que ça signifie et ce qu'il faut que je fasse ça serait gentil svp ?

Merci Smiley smile

cochi

2 Apr 2015 à 19:54

Pardon j'ai oublié le code

HTML :

<html lang="fr">
<head>
  <meta charset="utf-8">
  <title>Site Coralie</title>
  <link rel="stylesheet" href="styles.css">
</head>
<body>
    <div id="header">
        <div id="bloc_page">
            <div id="logo">
                <img src=Images/logo-header.png alt="Logo Coralie" />
            </div>
            <div id="nav">
                <ul>
                    <li><a href="index.html" accesskey="a" >Accueil</a></li>
                    <li><a href="apropos.html" accesskey="b" >À propos</a></li>
                    <li><a href="http://cnoyer.e-monsite.com/album-photos/" accesskey="c" title="lien provisoire">Portfolio</a>
                    </li>
                    <li><a href="" accesskey="d" >Blog</a></li>
                    <li><a href="" accesskey="e" >Contact</a></li>
                </ul>
            </div>
            <hr/>
            <div id="banniere">
                <h1>Affiche Foire de Lyon 2015</h1>
                <h2>Crée pour DG Automobiles</h2>
                    <div id="banniere_description">
                        <p>Affiche réalisée sous Illustrator pour DG<br> Automobiles à Meyzieu(69)</p>
                        <a href="" accesskey="f" class="lire_plus" >Lire plus</a>
                    </div>
                <a href="" accesskey="g" class="affiche_fdl"><img src=Images/affcihe-foire.png alt="  " title="Affiche de la Foire De Lyon 2015"/></a>
            </div>
        </div>
    </div>
    <div id="container">
        <div id="bloc_page">
            <div id="a propos">
                <div id="logo2">
                    <img src=Images/Logo-a-propos.png alt="Mon Logo" title="Logo Coralie"/>
                </div>
                <div id="presentation">
                    <h1>À propos</h1>
                    <p>Je m'appelle Coralie, j'ai 19 ans. Je suis passionnée par tout ce<br>qui touche au graphisme, au web et au multimédia. Je pratique<br>diverses activités dans ces domaines notamment grâce à la<br>Suite Adobe.</p> 
                </div>
            </div>
            <div id="articles">
                <div id="bordures">
                    <a href="" accesskey="h" class="montages"><h1>Les montages</h1></a>
                    <p>Les montages sont pour la plupart réalisés <br> avec Photoshop.</p>
                    <div id="imac"><img src=Images/Imac.png alt="" title="Les montages"/></div>
                    </div>
                <div id="bordures2">
                    <a href="" accesskey="i" class="publicites"><h1>Les publicités</h1></a>
                    <p>Les publicités sont réalisées soit grâce à <br>Illustrator soit avec InDesign.</p>
                    <div id="macbook"><img src=Images/Macbook.png alt="" title="Les publicités"/></div>
                </div>                 
            </div>
        </div>
        <div id="footer">
            <div id="bloc_page">
                <div id="logo_f">
                <img src=Images/logo-footer.png alt="Logo Coralie" />
                </div>
            <div id="nav_f">
                <ul>
                    <li><a href="index.html" accesskey="a" title="Retour accueil">Accueil/</a></li>
                    <li><a href="apropos.html" accesskey="b" title="A propos">À propos/</a></li>
                    <li><a href="http://cnoyer.e-monsite.com/album-photos/" accesskey="c" title="Lien provisoire">Portfolio/</a></li>
                    <li><a href="" accesskey="d" title="Blog">Blog/</a></li>
                    <li><a href="" accesskey="e" title="Contact">Contact/</a></li>
                </ul>
            </div>
            <div id="logo_fb">
                <a href="https://www.facebook.com/CNoyerD" class="fb" accesskey="j"><img src=Images/facebook.png alt="" title="logo Facebook"/></a>
            </div>
            </div>
        </div>
</body>
</html>

Et CSS :

/*Police fontsquirrel*/

@font-face {
    font-family: 'caviar_dreams';
    src: url('Police/CaviarDreams-webfont.eot');
    src: url('Police/CaviarDreams-webfont.eot?#iefix') format('embedded-opentype'),
         url('Police/CaviarDreams-webfont.woff2') format('woff2'),
         url('Police/CaviarDreams-webfont.woff') format('woff'),
         url('Police/CaviarDreams-webfont.ttf') format('truetype'),
         url('Police/CaviarDreams-webfont.svg#caviar_dreamsregular') format('svg');
    font-weight: normal;
    font-style: normal;

}




@font-face {
    font-family: 'caviar_dreamsbold';
    src: url('Police/CaviarDreams_Bold-webfont.eot');
    src: url('Police/CaviarDreams_Bold-webfont.eot?#iefix') format('embedded-opentype'),
         url('Police/CaviarDreams_Bold-webfont.woff2') format('woff2'),
         url('Police/CaviarDreams_Bold-webfont.woff') format('woff'),
         url('Police/CaviarDreams_Bold-webfont.ttf') format('truetype'),
         url('Police/CaviarDreams_Bold-webfont.svg#caviar_dreamsbold') format('svg');
    font-weight: normal;
    font-style: normal;

}




@font-face {
    font-family: 'caviar_dreamsbold_italic';
    src: url('CaviarDreams_BoldItalic-webfont.eot');
    src: url('CaviarDreams_BoldItalic-webfont.eot?#iefix') format('embedded-opentype'),
         url('CaviarDreams_BoldItalic-webfont.woff2') format('woff2'),
         url('CaviarDreams_BoldItalic-webfont.woff') format('woff'),
         url('CaviarDreams_BoldItalic-webfont.ttf') format('truetype'),
         url('CaviarDreams_BoldItalic-webfont.svg#caviar_dreamsbold_italic') format('svg');
    font-weight: normal;
    font-style: normal;

}




@font-face {
    font-family: 'caviar_dreamsitalic';
    src: url('Police/CaviarDreams_Italic-webfont.eot');
    src: url('Police/CaviarDreams_Italic-webfont.eot?#iefix') format('embedded-opentype'),
         url('Police/CaviarDreams_Italic-webfont.woff2') format('woff2'),
         url('Police/CaviarDreams_Italic-webfont.woff') format('woff'),
         url('Police/CaviarDreams_Italic-webfont.ttf') format('truetype'),
         url('Police/CaviarDreams_Italic-webfont.svg#caviar_dreamsitalic') format('svg');
    font-weight: normal;
    font-style: normal;

}

/*Element principaux de la page*/

body{
    background-color: #82848d;
    font-family: Arial, sans-serif, caviar_dreams;
    color:#fff;
    margin: 0;
    padding:0;
    font-size: 22px;
}

#bloc_page{                 /*Limite de la page entiere 900px*/
    width:900px;
    margin: auto;
}




/*Header*/

#header{
    background: url('Images/Header.png') repeat-x top left;
    width: 100%;
    height: 593px;
}

#logo{
    display:inline-block;
    margin-bottom: 0px;
    margin-top: 15px;
    
}

/*Menu*/

#nav{
    position:absolute;
    witdh: 740px;
    text-align:right;
    margin-left:155px;
    margin-top:-100px;
}

#nav ul{
    list-style-type: none;
}

#nav li{
    display: inline-block;
    margin-right:15px;
}

#nav li a{
    font-family: caviar_dreamsbold;
    font-size: 1.5em;
    color: #fff;
    padding-bottom: 3px;
    text-decoration: none;
    display:block;
}

#nav li a:hover{
    color: #a6a5a5;
    border-bottom: 3px solid #a6a5a5;
}


hr{
    color:black;
}




/*Banniere*/

#banniere{
    height: 322px;
    background-color: rgba(16,16,16,0.5) ;
    margin-top: 15px;
    position: relative;
}



h1{
    font-family: caviar_dreamsbold;
    font-size:2em;
    color:#fff;
    letter-spacing: 2px;
    text-transform: uppercase;
    margin-left: 65px;
}

h2{
    font-family:caviar_dreamsbold;
    font-size:1.5em;
    color:#fff;                                     
    margin-left: 65px;
}

#banniere_description{
    font-family:caviar_dreams;
    display: inline-block;

    margin-left: 65px;
}

.lire_plus{
    font-family:caviar_dreamsbold;
    color:#fff;
    text-decoration: none;
    display: inline-block;
    height: 40px;
    position: absolute;
    bottom: 5px;
    font-size: 1.2em;
    text-align: center;
    margin-bottom:20px;
}



.affiche_fdl{
    margin-left:140px;
    box-shadow: 0px 4px 4px #070a13;
    position: absolute;
    margin-top: -105px;
}

/*manque les fleches directionnelles du slider*/


/*Presentation*/

#logo2{
    display:inline-block;
    margin-bottom: 0px;
    margin-top: 15px;
    
}

#presentation {
    font-family:caviar_dreams;
    display: inline-block;
    color:#fff;
    margin-left: 258px;
    margin-top:-190px;
}

#presentation h1{
    font-family:caviar_dreamsbold;
    color: #4e4c4c;
    font-size: 1.5em;
    text-align:center
}

/*Articles*/

#articles{
    
    height:500px;
}

#bordures{
    border: 5px solid #4e4c4c;
    border-radius: 0;
    height: 460px;
    width: 440px;
    display:inline-block;
}

.montages{
    text-decoration: none;
    font-family: caviar_dreamsbold;
    text-transformation: uppercase;
}

.montages h1{
    color:#4e4c4c;
    display: inline-block;
    margin-left:40px;    
}

#bordures p{
    font-family: caviar_dreams;
    display: inline-block;
    margin-left: 5px;
}

#imac{
    diplay:inline-block;
    margin-left:67.5px;
    margin-top:-18px;
}

#bordures2{
    border: 5px solid #4e4c4c;
    border-radius: 0;
    height: 460px;
    width: 440px;
    display:inline-block;
    margin-left:5px;
    
}

.publicites{
    text-decoration: none;
    font-family: caviar_dreamsbold;
    text-transformation: uppercase;
}

.publicites h1{
    color:#4e4c4c;
    display: inline-block;
    margin-left:40px;    
}

#bordures2 p{
    font-family: caviar_dreams;
    display: inline-block;
    margin-left: 5px;

}

#macbook{
    diplay:inline-block;
    margin-left:18.5px;
    margin-top:-15px;
}

/*Footer*/

#footer{
    background: url('Images/Footer.jpg') repeat-x bottom left;
    width: 100%;
    height: auto;
    display:inline-block;
}

#logo_f{
    display:inline-block;
    margin-top:30px;
}

#nav_f{
    display:inline-block;
    witdh: 740px;
    text-align:right;
    margin-top: 55px;
    position: absolute;
}

#nav_f ul{
    list-style-type: none;
    
}

#nav_f li{
    display:inline-block;
    margin-right:0px;
    
}

#nav_f a{
    font-family: caviar_dreamsbold;
    font-size: 0.8em;
    color: #fff;
    padding-bottom: 3px;
    text-decoration: none;
    
}

#nav_f a:hover{
    color: #a6a5a5;
}

#logo_fb{
    display: inline-block;
    position: absolute;
    margin-left: 470px;
    margin-top: 67px;
}

~~supprimé~~

2 Apr 2015 à 21:09

Une grande partie des erreurs devrait être comblé en ajoutant un doctype tout au début de ton code :

<!DOCTYPE html>

Autrement, tu as un id bloc_page en double, ce n'est pas correct. Utilise des classes lorsque tu veux faire des styles réutilisables. Généralement, on utilise les id pour les grandes parties du site, header, footer, nav ou pour les éléments qui vont devoir être ciblé par javascript.

Évite les alt="Mon Logo" ou alt="Logo Coralie", si ton image n'apporte pas d'info utile sur le contenu laisse un alt vide (comme pour le logo dans le footer par exemple). Pour le logo dans ton header tu peux mettre simplement ce qu'il y a écrit dans ton image comme "Coralie".

Sujet clos

Questions générales et questions de débutants

Erreurs validator w3c