Skip to content
Bifröst Orbit
Sign in

CMS Orbit

Accessible by default: how CMS Orbit checks pages before they go live

Accessibility checks while you type, on the real page and at publish, with a report for the whole website and a task you can hand to an AI agent.

Bifröst Orbit team

5 min read

On this page

Most accessibility problems on a website aren't in the code. They're in the content: a photo without alt text, a link that says 'Read more', a heading that jumps from H2 to H4, white text on a pale photo. They arrive one page at a time, written by people who didn't know, and an audit finds them months later.

CMS Orbit checks for them while people write, again on the rendered page, and once more when they publish. This guide walks through each step.

The A11y panel: two checks in one list

Open a page and choose A11y in the rail on the right. The number on the rail is how many issues block people. The panel checks the page twice and shows one list.

  • The content, as you type: Images without alt text in this page's language, link text that says nothing on its own, links with no text, tables without header cells, long text in capitals, colour fields with too little contrast and headings that skip a level.
  • The rendered page: The live preview is checked with axe-core about two seconds after each change. It finds what the website's design adds, such as text over a photo that's hard to read, buttons without a name or form fields without a label.

When both checks find the same problem, it's listed once. Issues are grouped as Blocks people or Needs review, then by WCAG success criterion, such as 1.1.1 Non-text content. Point at an issue and the preview scrolls to it and outlines it in red. Issues in the website's header or footer are marked as template issues, for a developer.

CMS OrbitAccessibility
The A11y panel beside the Northwilds home page groups the issues found on the rendered page by WCAG criterion, so editors see what to fix and why.

The rendered check needs version 0.10 or later of the JavaScript SDK. Until then, the panel checks the content only and says so.

Fix it where you are

Many issues have a fix right under them, and each one changes the draft, so ⌘Z undoes it.

  • Alt text: Write what the image shows, in the page's language. With AI writing switched on, CMS Orbit can suggest alt text from the image itself, for you to read and change. Alt text is saved on the image, so every page that uses it gets it.
  • Link text: Choose a suggestion, such as the name of the page the link goes to.
  • Contrast: Choose a text colour that passes 4.5 to 1, with the website's own colours first.
  • Heading order: Where a component lets you choose, Make it H3 sets the level that follows the one before.

Some findings are fine as they are, such as a photo that's only decoration. Leave as it is asks for a reason, and the issue stops counting.

The main heading check that trusts the real page

Every page should have one H1. A content check can only see an H1 that the schema says a component prints. Many websites print the page title as an H1 from their own template, and a content-only check would then flag every page.

CMS Orbit trusts the real page. When the rendered check finds an H1, for example a title your template prints, 'No main heading' goes away by itself. The same goes for SEO health when the daily live website check finds one. If the issue stays, the page on your website may really have no H1. Developers can also mark which field of a component is the main heading, as Design components explains.

The publish gate

An administrator chooses what happens at publish, under Accessibility › Settings:

  • Off: Publishing ignores accessibility. The panel and report still show every issue.
  • Warn: The default. CMS Orbit lists issues that block people and asks before going live.
  • Block: A page with issues that block people can't be published until they're fixed or left as they are with a reason.

Issues that only need review never stop a page. An image without alt text in the page's language always does, whatever the setting.

Sometimes a page has to go live anyway. The winter sale opens at 09:00 and the photographer's alt text arrives at 10:00. In Block, administrators can publish with a reason. It's kept in the publishing history and the organisation's audit log, with the rules that failed. Everyone else sees which issues stop the page, and can fix them or ask an administrator.

Which guidelines

The rendered page is checked against the guidelines you tick: WCAG 2.0, 2.1 and 2.2 at levels A and AA, best practice, and WCAG 2.0 AAA for the strictest contrast. The default is A and AA for all three versions, with best practice. The European Accessibility Act points to WCAG 2.1 AA, through the standard EN 301 549.

The accessibility report

The report gives the whole website a score. Each blocking issue takes 15 points off a page and each issue to review takes 4. You see a 90-day trend, issues by rule with their WCAG criterion, and who is fixing what. Issues can be assigned or left with a reason, and the list exports as CSV for an audit or a supplier.

Copy for an AI agent

Beside each issue, in the panel and the report, Copy for an AI agent copies a ready-made task for Claude, ChatGPT, Cursor or another agent. It holds the page and its address, the rule and WCAG criterion, what's wrong, the elements involved with their HTML and where to fix it:

  • In the content: The task names the page and block ids, so an agent connected to CMS Orbit can fix it as a draft for you to check.
  • In the website's code: The task says so, for your developer's agent to fix in the repository.

Fix SEO and accessibility with an AI agent shows the whole workflow.

What checks can't tell

Automatic checks find about half of what matters. They can't tell if alt text is helpful, if a page makes sense read aloud, or if a form works with the keyboard alone. Before a big launch, use the page with the keyboard and listen to it with a screen reader such as VoiceOver or NVDA. CMS Orbit makes the common mistakes hard to publish. It doesn't replace that check.

Where it sits

Accessibility sits beside the SEO checks every page gets, described in SEO built into CMS Orbit, and beside reviews and approvals in reviews, approvals and audit trail. Read the docs on the A11y panel, publishing and the report, explore CMS Orbit, or talk to us.

Fix SEO and accessibility with an AI agent, live preview for a Next.js website and website templates.

Reading path · 3 of 4

Choosing a CMS

The questions to ask, how CMS Orbit compares and what editors get on day one.

  1. How to choose a headless CMS in 2026: the questions to ask
  2. CMS Orbit vs Contentful: how they compare now Contentful is part of Salesforce
  3. Accessible by default: how CMS Orbit checks pages before they go live
  4. Live preview for your website in four steps

CMS Orbit

Fix photos where you use them, and keep the original

The image editor in CMS Orbit and Travel Orbit crops, straightens, adjusts and blurs photos in the media library, and keeps the file you uploaded. Here is what it does and how blurring keeps private details off your website.

5 min read

See it with your own team.

Orbit is free. Try CMS Orbit for 14 days with your own content, no card needed, or ask us anything.

Talk to us