Back to HTML

The aside Element and Complementary Content

Coding Tutorials Team 20 June 2026

The aside element is widely misunderstood as meaning sidebar, which is a layout description rather than a meaning. A sidebar is where something appears on screen. An aside is what the content is, and the two frequently do not coincide.

The definition

An aside contains content tangentially related to what surrounds it, which could be removed without the main content becoming incomplete.

The relationship is the point. Content that is entirely unrelated does not belong in an aside, and content the reader needs is not tangential and belongs in the main flow.

What qualifies

At page level, an aside might hold related articles, a category list, an author biography, a newsletter signup, or advertising. Each relates to the page without being part of its main content.

Inside an article, an aside might hold a pull quote, a definition of a term used nearby, a footnote, or a box of background context. Each supplements the surrounding text.

<article> <h2>How specificity is calculated</h2> <p>...</p> <aside> <h3>A note on inline styles</h3> <p>Inline styles sit outside the usual calculation entirely.</p> </aside> <p>...</p> </article>

Position is irrelevant

An aside can be visually anywhere: beside the content, below it, inline within it, or above it on a narrow screen. The element describes the relationship rather than the placement, and the placement is a CSS decision that may change at every breakpoint.

The converse also holds. A column beside the main content is not automatically an aside. If it contains the site navigation, it is a nav. If it contains a second stream of primary content, it is not tangential and does not belong in an aside at all.

The landmark only applies at page level

This is the behaviour worth knowing. An aside that is not inside an article, section, nav or main is exposed as a complementary landmark, which users can navigate to. An aside inside one of those elements is not a landmark.

That is deliberate. A pull quote within an article is not a region anyone wants to jump to, whereas a related content panel at page level might be. The element adapts to context in the same way header and footer do.

Where a page has several page level asides, label each one so they can be told apart.

Give it a heading where it is a landmark

A complementary region with no accessible name is announced only by its role, which tells the user nothing about what it holds. A heading inside it, referenced with an aria-labelledby attribute, solves this and also helps sighted readers understand what the panel is.

Do not use it as a generic container

The common misuse is reaching for aside whenever content sits to one side, or using it as a slightly more meaningful looking div. Both produce landmarks and relationships the content does not have.

Where a container is purely structural, a div is correct and carries no false implication. Where the content is genuinely part of the main argument, it belongs in the main flow even if the design places it in a narrow column.

Pull quotes need care

A pull quote repeats a sentence from the article in larger type. Marking it as an aside is reasonable, and there is a second problem: the text appears twice, so a screen reader reads the same sentence in the pull quote and again in the body.

The usual solution hides the duplicate from assistive technology with an aria-hidden attribute, since the original will be encountered in place. Note that a blockquote is the wrong element here, because the text is not a quotation from another source.

Advertising and third party panels

Advertising is a legitimate aside, and a labelled one is better than an unlabelled one, since a user navigating landmarks can then choose to skip it rather than discovering what it is by listening.

Where the panel is an iframe, it needs a title attribute of its own, since the frame is a separate document and the surrounding label does not describe what is inside it.

Related content panels

A block of related articles at the end of a post is a common aside. It relates to what the reader has just finished, it is not part of the article itself, and removing it would leave the article intact.

Where such a block sits inside the article element, it will not be a landmark. Placing it after the article, as a sibling, makes it a complementary region a user can navigate to, which is usually the better structure for something the reader may deliberately want to reach.

The test

Delete the content mentally. If the main content is still complete and comprehensible, an aside is right. If something essential has gone, the content was never tangential and belongs in the flow.