HTML Guide

HTML start tag “img” in a foreign namespace context.

An img tag placed inside an SVG or MathML element creates a namespace error because img is an HTML element, not an SVG or MathML element.

SVG and MathML use their own XML-based namespaces, and HTML elements like img cannot be directly inserted inside them. To include raster images within SVG, the SVG image element should be used instead, and external math images must be handled outside MathML.

Explanation:

The HTML img element is only allowed in the HTML namespace.
Placing <img> inside an <svg> or <math> tag triggers a namespace conflict, as img is not a valid child of these elements.
The SVG standard provides the <image> element for embedding bitmap images within SVG.

Incorrect:

<svg width="100" height="100">
  <img src="picture.png" alt="Example" width="100" height="100">
</svg>

Correct:

<svg width="100" height="100">
  <image href="picture.png" x="0" y="0" width="100" height="100" />
</svg>

Use the SVG image element instead of HTML img whenever embedding images inside SVG.

Learn more:

Related W3C validator issues

A “source” element that has a following sibling “source” element or “img” element with a “srcset” attribute must have a “media” attribute and/or “type” attribute.

A <source> element inside a <picture> that is followed by another <source> or an <img> with srcset must include a media and/or type attribute.

The <source> element is used inside <picture> for responsive images, allowing different resources to be loaded based on conditions such as viewport width (media) or image format (type). According to the HTML standard, when multiple <source> elements are present (or a following <img> with srcset), each <source> must provide a media and/or type attribute so the browser can choose the appropriate resource based on those hints.

Without media or type, the browser cannot distinguish when to use each source, which can lead to validation errors and unexpected rendering behavior.

Incorrect example (causes the validator error):

<picture>
  <source srcset="image1.webp">
  <source srcset="image2.jpg">
  <img alt="" src="fallback.jpg" srcset="fallback2x.jpg 2x">
</picture>

Correct examples (fixing the error):

<picture>
  <source srcset="image1.webp" type="image/webp">
  <source srcset="image2.jpg" type="image/jpeg">
  <img alt="" src="fallback.jpg" srcset="fallback2x.jpg 2x">
</picture>

<picture>
  <source srcset="image-small.jpg" media="(max-width: 600px)">
  <source srcset="image-large.jpg" media="(min-width: 601px)">
  <img alt="" src="fallback.jpg" srcset="fallback2x.jpg 2x">
</picture>

By specifying the media and/or type attributes for each <source>, you satisfy the HTML standard and resolve the W3C validator issue.

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

<img> tags, used to include images on a document, require an alt attribute to describe the contents of the image. This is essential for users that cannot see the image (like screen reader users), or as an alternate text when the image cannot be displayed. Example:

<img src="photo.jpg" alt="Person holding a cat" />

An “img” element which has an “alt” attribute whose value is the empty string must not have a “role” attribute.

Bad start tag in “img” in “noscript” in “head”.

A start tag for <img> has been found inside a <noscript> section within the <head>, where it’s not allowed. Consider moving it to the <body> section.

The HTML <noscript> element defines a section of HTML to be inserted if a script type on the page is unsupported or if scripting is currently turned off in the browser.

When JavaScript is disabled, the content inside <noscript> will be used instead, so this content must fit within its parent section. As an <img> tag is not allowed inside <head>, this will raise an issue. Instead, consider moving the <noscript> part to the <body> section.

This issue is often related to 3rd party tracking pixels like the Facebook or LinkedIn conversion tracking pixels. For example, the Facebook pixel instructions tell you to insert it like this:

<html>
  <head>
    <script>
       ...some script...
    </script>
    <noscript>
       <img src="..." />
     </noscript>
  </head>
  <body>
     ...
  </body>
</html>

Instead, consider moving the <noscript> part inside the <body>, where the <img> makes sense to be inserted:

<html>
  <head>
    <script>
       ...some script...
    </script>
  </head>
  <body>
     ...
     <noscript>
       <img src="..." />
     </noscript>
  </body>
</html>

Bad value “100%” for attribute “height” on element “img”: Expected a digit but saw “%” instead.

img
height

The W3C HTML Validator issue you encountered indicates that the value of the height attribute for an <img> element is set to “100%”, which is not allowed in HTML. The height attribute must be a specific digit that represents the height in pixels (e.g., “150”), rather than a percentage or any other unit.

How to Fix the Issue

To resolve this issue, you need to specify a numeric value for the height attribute instead. If you want the image to occupy a certain percentage of the container, use CSS instead of the height attribute.

Example of Incorrect HTML

Here is an example that causes the validation issue:

<img src="image.jpg" height="100%" alt="Example Image">

Corrected HTML Using Pixel Values

To correct the issue, replace the percentage with a pixel value:

<img src="image.jpg" height="200" alt="Example Image">

Alternative: Using CSS for Responsive Design

If you want the image to scale responsively and occupy 100% of the width of its container, consider using CSS:

<style>
  .responsive-img {
      width: 100%;
      height: auto; /* Maintains aspect ratio */
  }
</style>

<img src="image.jpg" class="responsive-img" alt="Example Image">

Summary

Do not use percentage values for the height attribute of <img> tags.
Use pixel values for fixed dimensions.
For responsive design, use CSS to set the dimensions instead.

Bad value “auto” for attribute “sizes” on element “img”: Bad CSS number token: Expected a minus sign or a digit but saw “a” instead at “auto”.

The sizes attribute specifies the size of the image when it is displayed on different devices.

The error message is saying that the value auto is not a valid value for the sizes attribute.

To fix this issue, you need to replace the value auto with a valid size. You can use a width descriptor or a media query to specify the size for different device widths.

Here’s an example of using a width descriptor:

<img src="example.jpg" sizes="(max-width: 600px) 100vw, 50vw" />

This example sets the size of the image to 100% of the viewport width when the device width is less than or equal to 600px, and 50% of the viewport width for larger device widths.

Alternatively, you can remove the sizes attribute altogether and let the browser decide the best size for the image based on the viewport size.

<img src="example.jpg" />

If you do this, the browser will use the default sizes value of 100vw and will scale the image accordingly.

Bad value “auto” for attribute “width” on element “img”: Expected a digit but saw “a” instead.

The width attribute on the img element must be a positive integer representing the number of pixels.

The HTML img element’s width and height attributes are expected to specify image dimensions in pixels. According to the HTML Living Standard, these attributes accept only non-negative integers. These integers define the rendered dimension of the image, overriding the actual image size based on its native resolution. The value “auto” is not a valid integer, which leads to the validation error you’ve encountered.

Here is a correct usage example of the img element:

<!DOCTYPE html>
<html lang="en">
<head>
  <title>Valid Image Width</title>
</head>
<body>
  <img src="example.jpg" alt="Example image" width="200" height="100">
</body>
</html>

In the example above, the width is set to 200, and the height is set to 100. Both values are non-negative integers representing pixel dimensions. If you intend to maintain the image’s aspect ratio while adjusting another dimension, you can omit one of the attributes, and modern browsers will automatically adjust the aspect ratio based on the given dimension.

Bad value “” for attribute “sizes” on element “img”: Must not be empty.

sizes
img

An empty sizes attribute on an img element is invalid; the attribute must contain a valid value or be omitted.

The sizes attribute specifies the slot width that the browser should use for selecting the appropriate image from those available in srcset. It should only be used when the srcset attribute is present. An empty string is not a valid value—if you do not have any sizes to specify, the attribute should be removed entirely.

Correct usage:

Remove the empty sizes and srcset attributes if not needed.
If specifying, provide valid values such as "100vw" or "(max-width: 600px) 100vw, 50vw".

Incorrect example:

<img src="photo.jpg" srcset="photo-small.jpg 480w, photo-large.jpg 1200w" sizes="" alt="">

Corrected example (with a valid sizes value):

<img src="photo.jpg" srcset="photo-small.jpg 480w, photo-large.jpg 1200w" sizes="100vw" alt="">

Bad value for attribute “src” on element “img”: Illegal character in scheme data: “<” is not allowed.

Bad value “” for attribute “src” on element “img”: Must be non-empty.