Blog / Framer & site building /

Accessible headings in framer components

A reusable card component looks simple. A picture, a title, a link. What could go wrong?

Then you drop it on a page and every card title becomes a top-level heading. The design looks fine. The document outline is a mess.

In Framer, heading choices should reflect the content structure of the page, not just the font size in the design. Reusable components need extra care because they turn up in different contexts.

Use headings to organise content

A page should have a clear main heading and a sensible sequence of section headings beneath it. A card title may be a heading when the card is a distinct section or item in a list, but its level should fit the page around it.

Don’t pick heading tags just to make text bigger. It’s one of the habits I’d most like designers to drop. Typography controls handle appearance; heading levels communicate relationships to assistive technology and help people scan.

Consider the component’s context

A component used on a homepage, a category page and a related-content section may sit under different heading levels. If the component hard-codes a single level, it may not fit every use.

Where appropriate, expose the heading tag as a component property or create variants with clear use cases. Add a short note for editors explaining when to use each. Avoid a pile of options that makes a simple component harder to use than a one-off page.

Test the published page

Preview the component in context, then inspect the published page’s HTML or use an accessibility checker. Confirm that headings appear in a logical order, link text makes sense out of context and images have appropriate alternative text.

A heading like “Read more” is not a useful substitute for a descriptive link. If the whole card is clickable, check that keyboard users can reach it and understand its destination. Visual focus should be visible too.

Keep SEO and accessibility aligned

Search optimisation and accessibility share a useful principle: make the page structure clear. A heading hierarchy can help both people and machines understand sections, but there is no magic sequence that guarantees rankings. The page still needs useful content and a clear purpose.

Review a handful of templates after changing a component. One reusable fix can improve many pages; one bad default can also spread quickly.

Here’s how it usually shows up. A component looks balanced in the Framer canvas, but when it appears on a real page the heading sequence jumps from the page title to a smaller section heading, then back up again. Visitors may still read the words, yet people navigating by headings lose a useful outline of the page. Heading levels are about structure as well as appearance.

A reusable component should not assume that it always sits at the same level. A card title might be a heading on one page and a link label inside a section on another. If the component hard-codes a heading level, editors may create a document structure that does not match the page hierarchy.

Separate visual style from structure

Decide what role the component plays in context. The page should have a clear main heading, followed by headings for its major sections and subheadings where needed. A heading should describe the section that follows, not just make text look larger. Use styling controls for visual size, and choose the semantic element according to the content hierarchy.

In a component library, make the intended use visible to designers and editors. Document whether the component title is configurable and how to choose the right level. Avoid a complicated set of options if most editors will not know what they mean; instead design components that naturally fit a defined role.

Test the published page

Inspect a real page that uses the component, not only the component in isolation. When I check heading structure, I pull out just the list of headings and read it like a table of contents. If it doesn’t make sense on its own, something’s wrong. Read the heading list in order and ask whether it forms a useful outline. Check whether decorative labels have been marked as headings unnecessarily and whether links have meaningful accessible names. Use a screen reader or accessibility inspection tool where available, then also read the page visually.

Test the component with a long title, a missing optional heading and nested sections. Ensure the component does not create empty headings or repeat the same label in a way that confuses navigation. If a component is used in several contexts, test each context because its correct heading level may change.

Keep the system maintainable

When a shared component changes, review a sample of pages that use it. A small edit to a reusable block can affect many pages at once. Keep notes about the component’s intended role and have an editor check the result before publishing a site-wide change. Do not assume that a visual redesign automatically fixes heading structure.

Headings also help editors maintain a page. A clear outline makes it easier to spot a section that has been moved, duplicated or left without an introduction. When a component is reused, its title should fit the section around it rather than forcing the page to follow the component’s visual layout. Keep that relationship in the component notes so the next designer knows why the heading is configurable.

Your next step: pick the Framer component you reuse most, open a live page that uses it, and list the headings in order. Would that outline make sense to someone who can’t see the design?