The Cartographer's First Unmarked North: On the Perilous Allure of a Perfectly Centered Page Without a `main` Landmark

We are taught, with the fervor of a sacred creed, that every page must have a single, unambiguous purpose. This purpose is to be enshrined within the <main> landmark, a beacon for assistive technologies and a declaration of intent for our code. It is the 'You Are Here' star on the map of our document. To build without it is considered a cardinal sin of accessibility, a failure of semantic duty. But I want to posit a quietly heretical thought: what if, in our dogmatic adherence to this rule, we are sometimes building a beautifully labeled map that leads to a featureless plain?

The argument for <main> is unimpeachable on its surface. It provides a direct navigational shortcut, allowing screen reader users to bypass the ubiquitous header and navigation to find the primary content. It is, in theory, an act of profound respect. Yet, this very act of labeling can become a perfunctory gesture, a checkbox we tick after we have already designed the entire experience. We center our design and our development process around the visual narrative—the hero image, the captivating animation, the seamless scroll—and then, as an afterthought, we wrap the biggest block of text in a <main> tag and call it a day.

The Tyranny of the Single Landmark

This is where the counterintuitive danger lies. By providing a single, powerful skip link, we can inadvertently validate a flawed information hierarchy. A page might be visually stunning and performantly flawless, scoring a 100 on all the synthetic metrics, but if its conceptual 'main' content is a scattered, disjointed affair, the <main> tag doesn't fix that. It merely points to the mess with greater efficiency. It confirms to the user that, yes, this sprawling collection of marketing copy, tangential testimonials, and a half-hidden contact form is indeed the primary offering. We have given them a compass that points unerringly to a confusing destination.

Perhaps a more radical, and ultimately more respectful, approach is to occasionally question the very need for a <main> element. Not out of neglect, but out of a different philosophy. Consider a richly interactive application, a canvas for creation like a design tool or a collaborative document. Its entire surface is the content; its functionality is distributed. To designate one area as 'main' might be to misunderstand its holistic nature. In such cases, a suite of more granular, descriptive ARIA landmarks—navigation, form, region—might paint a far more accurate and useful map than a single, reductive <main> could ever provide.

This is not an argument against accessibility. It is an argument for a deeper, more thoughtful accessibility—one that moves beyond the compliance checklist. The true landmark is not a tag we insert, but the clarity of purpose we build into the page itself. Before we reach for the <main> tag, we must first ask: does my page have a true north? Or am I simply putting a signpost on a winding path because the style guide told me to? Sometimes, the most accessible thing we can do is to design a page so intuitively structured that the formal landmark becomes almost superfluous, a graceful confirmation of a truth the user has already discovered.

Notes & further reading

A few pages I came back to while writing this: