Accessibility
Montage Engine should work however you browse it — with a keyboard, with a screen reader, at a large text size, or with motion turned down. This page says what we have done about that, what we know is still wrong, and how to tell us when we have missed something.
Our standard
We target WCAG 2.2 Level AA. "Target" is the honest word for it: that is the bar we build and test against, not a certificate anyone issued us. We would rather list what is still broken than publish a badge.
This covers this site (montageengine.com) and the signed-in app (app.montageengine.com). Both were audited and fixed in September 2026. What gets tested automatically is narrower than that, and the next two sections say how much narrower.
What we do
We audited both surfaces in September 2026 — every page of this site, every screen of the app — and shipped the fixes. The audit itself is an internal document, so we are not asking you to take it on trust: most of what follows is something you can check yourself in a minute, and the rest is something we say plainly that we have not checked.
Every change to this site is scanned automatically. Our build loads all ten pages in a browser and checks the rendered markup against the WCAG 2.x Level A and AA rules, on every proposed change and on everything that lands on our main branch. The app's interface has a narrower check: a linter reads the app's source on every change for a fixed set of markup and ARIA rules. It reads the source, not the running app, so it catches regressions rather than testing what you actually see.
What that has produced, concretely:
- Keyboard. On this site everything is a link, a button or a form field, and all of it works from the keyboard. In the app, the slide editor's canvas is a single tab stop with arrow-key selection, and every action that used to need a drag — move, resize, rotate, reorder, flip, delete — has a keyboard equivalent.
- A visible focus indicator. Wherever keyboard focus is, there is a ring around it, and on dark backgrounds the ring switches to white so it does not disappear into them.
- A skip link. Every page of this site starts with a "Skip to content" link, so you are not tabbing through the navigation on every page.
- Reduced motion. If your system asks for less motion, we honour it: this site stops scrolling smoothly and the app stops its animations.
- Target sizes. Buttons, the navigation keys and the jump links on long pages are at least 24 by 24 CSS pixels.
- Contrast. We computed every colour pair in the palette rather than trusting our eyes, and retuned two of them, so text clears 4.5:1 and control edges and chart lines clear 3:1.
- Charts that do not depend on colour. Each series on the analytics charts has its own dash pattern and marker shape as well as its own colour, and the legend words are plain text rather than coloured.
- No dragging required. In the slide editor, a "Selected overlay" panel carries numeric position, size and rotation fields, plus opacity, flip, layer order and delete — so an overlay can be placed with single clicks and typing, without ever holding a button down.
Known limitations
We would rather be honest than impressive. These are the things we know about:
- No screen-reader session has happened yet. We have built to the standard and checked the markup, but nobody has sat down with VoiceOver or NVDA and worked through the product end to end. That pass is planned, and this page will say so once it has happened. Automated tools do not stand in for it — they check markup, not whether the result makes sense to listen to.
- The app is not covered by the automated scan. It needs an account to load and our test runner has none, so the scan runs against this site only. The app was reviewed and fixed by hand, and the source linter described above is the only automatic guard on it.
- The editor's keyboard and no-drag controls are new. They follow the standard pattern for this kind of control, but they have not yet been through a hands-on pass with a keyboard and a screen reader. If something there does not respond the way you expect, that is worth telling us about specifically.
- We target Level AA, not Level AAA. Some of what AAA asks for — a 7:1 contrast floor, sign-language alternatives — we have not attempted.
- Long lists are a lot of tab stops. The image library and the TikTok posts table put every row in the tab order. Nothing is unreachable, but getting to the bottom of a long library takes a while. If that is tiring, tell us; it is fixable and we have not prioritised it.
- Image descriptions are supported, not supplied. Every image in your library can carry a description, and we use it everywhere that image appears. Images added before the field existed have none until somebody writes one — we will not invent descriptions for your pictures.
- The account chart has a name, not a text alternative. On the analytics screen, the follower and profile-view chart announces what it shows and over what period, but the numbers behind it are not available as a table anywhere. The per-post chart is fine: the Posts table beside it carries the same figures.
- The support form's error path is not ours. If a message sends you come back here and we confirm it in place; if it fails you land on our form provider's own error page instead of being told about it where you were. Email is unaffected.
- The company name in the footer. "akineticzen" is marked up as an abbreviation of "akineticzen LLC", which a screen reader will expand but a touch user cannot reveal. The full name is written out on the Support, Privacy and Terms pages.
- Automated contrast checking is not full contrast checking. A tool can only judge the colour pairs it can resolve — not text over a photograph, and not a state it never entered. That is why the human pass exists, and why a clean automated run is a floor rather than a ceiling.
- Some screens are not ours. Signing in is Clerk, billing opens the Stripe customer portal, the form on the Support page is Formspree, and publishing hands off to TikTok. We report problems we find in these to their vendors, and we will help you work around one, but we do not control their markup.
Tell us what we missed
If something here stops you, tell us. You do not have to be a customer to report a barrier, and you do not have to know what the standard says — "I cannot get past the theme picker with a keyboard" is a complete report.
Use the support form, or email support@montageengine.com. If you would rather speak to someone, the number is (814) 732-0744.
It helps if you say which page or screen you were on, what you were trying to do, and what you browse with — the browser, and any assistive technology and its version. A screenshot or a short recording is useful and never required.
We reply within five business days, usually much sooner, and we will tell you what we are going to do about it.
About this statement
This statement describes Montage Engine as it is, not as we would like it to be. We review it whenever the checks described above change, whenever we close something listed under Known limitations, and at least once a year regardless.
It was prepared by akineticzen LLC, the company behind Montage Engine, on the basis of our own review of both surfaces. Nobody outside the company has evaluated it.
Last reviewed: