Foros del Web - Ver Mensaje Individual

osaka80 · #1 (**permalink**) 27/03/2013, 11:30

Hola muy buenas a todos, estoy realizando una página HTML modo básico, al validar mi página con este programa "Total Validator" (es la primera vez que lo hago) obtengo una información que detallo abajo y me pregunto tengo que solventar los errores o fallos que me aparecen con este validador ??? gracias de antemano

More Information
HTML Errors
E600 - 16 instance(s): This error is often raised when a browser-specific tag has been used such as <embed>. Alternatively you may have misspelled the name or tried to use a tag that is not valid with the HTML specification you are validating against.

E609 - 6 instance(s): If this error is preceded by an E604 error (missing end tag) then correcting the earlier E604 error may correct this one. Otherwise note that there are strict rules as to what tags may be nested within others, as well as the order and number of tags allowed. Try removing the item marked with this error or nesting it within one of the tags listed. Note that in rare cases it is possible that a tag in the list provided also may not be allowed, but a simple test should quickly resolve this.

E620 - 12 instance(s): The most common reason for this error is the use of a browser-specific attribute (such as 'leftmargin' in the <body> tag), which is not part of the official HTML specification being tested against. If the attribute is for purely for layout then consider using CSS instead.

E622 - 1 instance(s): The HTML specification being validated against defines certain valid values for each attribute. Usually a list of valid values will be displayed when you see this message. Note that many values must be in lower case in XHTML, including the 'x' in numeric hex entity references. Note also that what values are allowed varies from standard to standard.

WCAG 2.0 A Errors
E860 - 1 instance(s): If there is no 'alt' attribute, then assistive technologies are not able to identify the image or to convey its purpose to the userSee http://www.w3.org/TR/WCAG20-TECHS/F65.html (displayed in new window)

E879 - 2 instance(s): Provide either a <caption>, 'title' or 'summary' attributes to describe the table. This must be a proper description and not a terse one. Seehttp://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html (displayed in new window). If this is not a data table and it is an HTML5 page then this is an HTML5 error as layout tables should not be used in HTML5. Or this is an accessibility error as there is structural markup present. See http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/F46 (displayed in new window).

WCAG 2.0 AA Errors
E910 - 5 instance(s): Using relative units helps the page to be rendered correctly at different resolutions and allows people with sight difficulties to 'zoom in' to pages to read them. Seehttp://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-scale.html (displayed in new window)

WCAG 2.0 A Errors
P883 - 4 instance(s): Heading elements must be ordered properly. For example, H2 elements should follow H1 elements, H3 elements should follow H2 elements, etc. Developers should not skip levels or use headings for presentation effects. See http://www.w3.org/TR/WCAG20-TECHS/F43.html (displayed in new window)

P892 - 16 instance(s): Tags that are being used purely to create a visual presentation effect should not be used. You should use CSS to control layout and presentation so that users and their aids may control it. See http://www.w3.org/TR/WCAG20-TECHS/G140.html (displayed in new window)