Accessibility at Overskill

Our commitment

We want everyone to be able to build and ship an app with Overskill, including people who use a screen reader, navigate by keyboard, rely on magnification, or need reduced motion.

We treat an accessibility barrier that stops someone signing in, building, publishing or paying the same way we treat any other blocker on those paths: it goes to the front of the queue.

The standard we work to

We work to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. WCAG 2.2 AA includes everything in 2.1 AA, which is the version most often cited in accessibility litigation and the one the EU's EN 301 549 incorporates.

We test against both 2.1 AA and 2.2 AA so that a success criterion added in 2.2 cannot quietly go unmeasured.

Conformance status

Overskill is partially conformant with WCAG 2.2 AA. Partially conformant means some parts of the service do not yet fully meet the standard. The specific gaps we know about are listed below.

We have not been independently audited. Everything on this page is our own assessment, and we would rather publish an honest partial status than a claim we cannot hand a customer evidence for.

What this covers

This statement covers the Overskill marketing site at overskill.com and the Overskill builder — signing in, the dashboard, the app editor, publishing, and billing.

It does not cover apps built by Overskill customers. When a creator builds and publishes an app, the pages, content, colours and components in that app are theirs: they choose the words, the images and the design, and they can change them at any time. We give creators accessible defaults and we will help them fix a problem, but we cannot state a conformance level for someone else's site. If you have hit a barrier on an app built with Overskill, the fastest route is the app owner — and you are still welcome to tell us, because a pattern that keeps recurring is usually something we should fix in the defaults.

It also does not cover third-party services embedded in the product, such as the payment provider's own checkout fields.

Known limitations

These are the gaps we have measured and have not fixed yet. The list comes from our own automated and manual testing on the date at the top of this page, not from a template.

Use the Accessibility link in the footer of any page, or in your account menu inside Overskill, to adjust contrast, text size, and navigation.

• Low-contrast small text on a few screens — A few pieces of small text — the schedule chips on the AI Employees page and the badges on the changelog — do not yet meet the 4.5:1 contrast minimum. The muted labels this list used to name — footer headings, pricing labels and the sidebar — were fixed in October 2026. What is left uses one-off colours, and each one is being moved onto our shared colours. Workaround: your browser's or operating system's increase-contrast setting applies to these pages.
• No skip link yet — Pages do not yet have a "Skip to main content" link, and most do not mark their main content area, so a keyboard user has to move through the navigation on every page before reaching the content. Workaround: screen-reader users can jump straight to the page's main heading with their heading shortcut. Status: this touches every page layout, so it is being done as one piece of work.
• The keyboard focus outline is faint in places — The outline that shows which control has keyboard focus does not reach the 3:1 contrast minimum against some page backgrounds. A darker outline fixes those backgrounds but fails against our dark-theme buttons, so the fix is a two-tone outline that shows up on both. Workaround: your operating system's increase-contrast setting makes the outline easier to see.
• Screen reader testing is not yet complete across every flow — We have added announcements to the parts we know matter most, including the builder's streaming conversation, and we have made the publish dialog keyboard-operable. We have not finished a full screen-reader pass of every screen, so there will be screens we have not checked. Workaround: none — if you hit one, please tell us and we will prioritise it.
• Automated testing only catches part of the picture — Our automated checks run several times a day, but automated tools find roughly a third of accessibility problems. Issues that need a human — whether a label actually describes the thing it labels, whether a reading order makes sense — are found by our manual review, which is ongoing rather than finished.
• No published conformance report yet — We have not yet published an Accessibility Conformance Report (VPAT). If you need one for a procurement or accessibility review, write to us at the address below and tell us which product and which standard you need it against.

How we test

On 24 October 2026 we ran a full audit against WCAG 2.2 AA: automated axe-core checks on every page we could reach, in light and dark themes, at desktop and phone sizes, plus hands-on checks of keyboard access, focus handling, dialogs and screen-reader announcements. The known limitations above come from that audit and the fixes we have made since.

Between audits, automated axe-core checks run several times a day against the sign-in, dashboard, editor, publishing and billing screens and the main marketing pages, in both themes, and flag any new serious problem on those screens so we can fix it.

Alongside that we do manual keyboard and screen-reader review. Automated and manual testing answer different questions, and neither one on its own is a conformance assessment.

Tested with recent versions of Chrome, Safari, Firefox and Edge, with VoiceOver on macOS and iOS.

Tell us about a barrier

If something on overskill.com or in the Overskill builder stopped you, please email [email protected]. It reaches our support team and is tracked like any other support request.

It helps if you can tell us the page or screen, what you were trying to do, and what you use to browse — for example "VoiceOver on Safari" or "keyboard only". None of that is required; a sentence is enough.

We aim to reply within 5 business days with either a fix, a date, or an honest answer that we do not have one yet. If a barrier blocks you from signing in, building, publishing or paying, we treat it as a priority bug rather than a feature request.

You can also reach us through the help menu inside the product, or at [email protected] if that is easier.

Keeping this page honest

This statement is reviewed at least every six months, and whenever we make a significant change to the product. The date at the top is the last time it was reviewed, not the last time the page was touched.

If something on this page no longer matches what you experience, that is worth telling us too — a stale accessibility statement is its own kind of barrier.

Contact