Top 10 HTML Warnings in Spain

Trailing slashes on void elements like <br/>, <img/>, or <hr/> serve no purpose in HTML and are ignored by browsers. However, they can cause subtle bugs when combined with unquoted attribute values, because the slash may be parsed as part of the last attribute’s value rather than as a self-closing indicator. The simplest fix is to remove trailing slashes from all void elements.

Attribute names containing certain characters — such as curly braces, template syntax markers, or control characters — cannot be represented in XML 1.0 and will trigger this validation error. This commonly happens when template placeholders (e.g., {{variable}}) or special characters are accidentally left in the rendered HTML output. To fix it, ensure all dynamic expressions are properly resolved before the HTML is served, and that attribute names only contain valid characters.

Duplicate id attributes in an HTML document cause validation errors, accessibility problems, and unpredictable JavaScript behavior. The W3C validator flags this message to point you back to the first element that uses a given id, helping you locate where the duplication begins. To fix it, ensure every id value appears only once per page by renaming or removing the duplicates.

Since HTML5, the default scripting language for <script> elements is JavaScript, making type="text/javascript" redundant. The W3C validator flags this as an unnecessary attribute. Simply remove the type attribute from any <script> tag that loads or contains JavaScript.

The W3C HTML Validator warns when a <section> element does not contain a heading (<h2>–<h6>). The <section> element is intended to represent a thematic grouping of content that typically has its own heading. To fix this, either add a heading element inside each <section>, or consider using a different element like <div> if the content doesn’t represent a distinct, named section.

The <li> element already has an implicit ARIA role of listitem, so explicitly adding role="listitem" to it is redundant. Remove the unnecessary role attribute from your <li> elements, as the browser and assistive technologies already understand their purpose from the semantic HTML alone.

The W3C validator warns about possible misuse of aria-label when the attribute is applied to an element where it has no effect or is not permitted by the ARIA specification. To fix this, ensure aria-label is only used on elements that have an interactive role, a landmark role, or a role that supports naming — and remove it from generic elements like <div>, <span>, <p>, or other elements where it will be ignored by assistive technologies.

The ul element already has an implicit ARIA role of list, so explicitly adding role="list" is redundant. The W3C validator flags this as unnecessary because native HTML semantics should be relied upon instead of duplicating them with ARIA attributes. Simply remove the role="list" attribute from your ul element to resolve this warning.

The charset attribute on the <script> element is obsolete in HTML5 and will trigger a validation warning. Scripts are required to use the same character encoding as the document, so the attribute is unnecessary and should be removed.

` delimiters of your comments.