Accessibility
Our accessibility statement Made to work for everyone who uses it.
People sign in to Bifröst Orbit to do their job, with a mouse, a keyboard, a screen reader, a magnifier or their voice. We want every one of them to get it done. This page says how close we are, how we check, and what we still have to fix.
Our target
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA everywhere we build, in light and dark mode, in every language the apps speak. WCAG 2.2 AA is also what the European standard EN 301 549 builds on.
This statement covers:
- bifrostorbit.com, our website
- docs.bifrostorbit.com, our documentation
- Orbit and its satellites in the browser: CMS Orbit, Travel Orbit, Commerce Orbit, Booking Orbit, Presence Orbit, Careers Orbit and Insights Orbit
The Orbit app for iPhone isn't released yet and will get its own statement when it is. Websites our customers build with CMS Orbit are theirs; we give them the tools to make them accessible, which you can read about below.
Where we are
Partially conformant. Some parts may not yet fully meet WCAG 2.2 AA. We have tested every screen of the website, the docs' main pages and the apps with automated checks, and fixed everything they found, but we haven't yet checked every page by hand or had an independent audit.
On 9 November 2026 we ran axe-core against the WCAG 2.0, 2.1 and 2.2 A and AA rules on more than 80 screens, each in light and dark mode: every page of bifrostorbit.com, the main pages of the docs, Orbit's own screens, and every screen of CMS Orbit including the page editor. It found 5 kinds of problem in 12 places, from controls whose spoken name didn't match their label to buttons smaller than the 24 by 24 pixels WCAG 2.2 asks for. We fixed all of them the same day, and the same checks now pass.
Automated checks find only part of what can go wrong, so they are where we start, not where we stop.
How we build it
Accessibility is part of the work, not a review at the end
What we know still needs work
Screen reader testing: we haven't yet tested every task from start to finish with VoiceOver, NVDA and JAWS. Some status changes may not be announced.
Drag and drop: the page editor, menus and pipelines let you drag things into order. Most also have Move up and Move down buttons or menu items; we are checking that every one does.
Charts: reports in Insights Orbit, Booking Orbit, Presence Orbit and CMS Orbit show figures as charts. Most also show the numbers in a table or as text; we are checking that every chart does.
Maps: trip itineraries in Travel Orbit show the route on a map. The days and places are also listed as text.
Documents: PDFs we create, such as legal documents and invoices, may not be fully tagged for screen readers. Every legal document is also a web page on this site.
Third-party pages: card payments are taken on Stripe's pages and some sign-ins happen at Microsoft or Google. Their accessibility is theirs, though we choose providers that publish their own commitments.
If you meet a barrier that isn't on this list, please tell us. It helps us more than anything else.
For the websites you build
CMS Orbit helps your editors publish accessible pages
Your own website is yours to make accessible, and CMS Orbit helps on every page:
- Checked as you type: missing alt text, unclear link text, skipped heading levels and more, in the fields where you write them.
- Checked on the real page: the A11y panel runs axe-core on the rendered page in the live preview and points at each problem.
- Fixes you approve: suggested alt text, link text and contrast fixes, only applied when an editor says yes.
- A gate before publishing: warn about, or block, pages with serious problems.
- A report for the whole site: a score, a trend and every open problem, with someone assigned to each.
- Handed to an AI agent: any issue can be copied as a ready-made task for an AI coding agent, with the page, the elements involved and where to fix it.
Tell us about a barrier
If something on our website, in our docs or in the apps is hard or impossible for you to use, email hello@bifrostorbit.com. Tell us the page or screen, what you were trying to do and, if you like, the browser and assistive technology you use. A person on our team will reply, and if we can't fix it straight away we will help you get the task done another way.
If you are in the EU and not happy with our answer, you can contact the body that enforces accessibility law in your country.
About this statement
We wrote this statement on 9 November 2026, from our own testing as described above. We review it whenever we change how something works and at least once a year, and the date here changes when we do.