W3C errors and warnings

  • Resolved andreabk

    (@andreabk)


    8 years, 9 months ago

    Hallo,

    using the SEO services of onpage.org, I found out that it seems that the CSS stylesheet (or me, I actually don’t know) is generating several warnings and errors. These errors have been found the W3C Validator. Here you are some examples:

    Warning: The banner role is unnecessary for element header.
    From line 413, column 9; to line 413, column 66
    ?? <header id=”header” class=”header_wrap row” role=”banner”>??

    Error: Bad value 2 for attribute rel on element a: The string 2 is not a registered keyword.
    From line 676, column 58; to line 676, column 77
    =”1″>12<

    The clear attribute on the br element is obsolete. Use CSS instead.
    Code: ipt></div><br clear=’all’ /><p sty

    Could you please give me some suggesstions?

    Thanks,

    Andrew

Viewing 2 replies - 1 through 2 (of 2 total)
  • Theme Author ThemeAWESOME

    (@tsquez)

    Hi there,

    Not sure exactly what kind of suggestions you are looking for.

    I know one you can take care of yourself which is to remove role="banner" from the header.

    For Bad value 2 for attribute rel on element a: this means you do not have a proper rel value for a link, such as rel="Home". The only links that are in WP-Forge are the links in the footer and those have the proper values.

    I did a search for <br clear='all' /> and nothing was found in the theme so this is something that you added or a plugin has added.

    All of these errors, with the exception of the header, that you are experiencing seem to be user generated and not theme related.

    My only suggestion would be to look into these errors and correct them, find theme and address each one accordingly.

    Hope this helps.

    Thread Starter andreabk

    (@andreabk)

    Thanks for your support, I’ll check these issues, alhough I realize now that such alarms from onpage.org are probably neglectable. I also need your help for CSS, but I’ll start a new thread ??

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘W3C errors and warnings’ is closed to new replies.

Tags