Top 10 HTML Warnings in Portugal

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.

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.

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.

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 link role is unnecessary on an <a> element that already has an href attribute, because the browser automatically assigns the link role to such elements. To fix this warning, simply remove the role="link" attribute from your anchor elements.

The <article> element represents a self-contained composition, but when it lacks a heading (<h2>–<h6>), assistive technologies and users have no way to quickly identify its content. Fix this by adding a descriptive heading element inside each <article> to give it a clear, accessible label.

The type attribute on the <style> element is unnecessary in HTML5 and should be removed. Since CSS is the default and only supported styling language for HTML, specifying type="text/css" is redundant. Simply remove the type attribute from your <style> tags to resolve this warning.

The role="button" attribute is unnecessary when applied to a <button> element because the button already has an implicit ARIA role of button. To fix this warning, simply remove the role="button" attribute from any <button> elements in your markup.

The nav element already has an implicit ARIA role of navigation, so adding role="navigation" to it is redundant. The W3C validator flags this as unnecessary because the semantic meaning is already built into the element. To fix this warning, simply remove the role="navigation" attribute from any nav element.