Accessibility Statement

We want this website to be usable by everyone, including people who navigate with a keyboard, a screen reader, magnification or reduced motion. This page records what we have done, what we know is imperfect, and how to tell us when we get it wrong.

Conformance target

We aim to meet WCAG 2.2 Level AA. Parts of this site are assessed automatically on every change and parts are reviewed by hand; because an automated check cannot prove conformance on its own, we hold that standard as a target rather than a statement of full conformance. Where we know we fall short, it is listed below rather than left for you to discover.

What is in place

• A skip-to-content link as the first focusable element on every page.
• A visible focus outline on every interactive element, never removed.
• Motion respects prefers-reduced-motion: scroll behaviour and entrance animations stop.
• High-contrast and forced-colours modes are handled, including for text rendered as a gradient.
• The FAQ accordion on the home page is a native disclosure element, so it works with the keyboard and without JavaScript.
• The mobile menu moves focus into the panel, traps Tab within it, and returns focus to the button on Escape.
• Every contact form control has a real label; icon-only buttons and links carry an accessible name.
• Decorative graphics and icons are inline SVG, hidden from assistive technology, and contain nothing focusable.
• The font is self-hosted and subset, so text renders without waiting on a third party.
• Tables that are wider than a phone screen — the cookie register and any table in an engineering note — scroll sideways inside a container that can be reached and scrolled from the keyboard.

Known limitations

• The chat widget is a third-party component assessed by its vendor, Crisp, not by us. If it blocks you, email us and we will answer the same question another way.
• Booking a call takes you to Cal.com, a separate site with its own accessibility properties. If the scheduler does not work for you, email us and we will arrange the call by hand.
• Engineering notes ship no images, so nothing in them depends on alternative text — but a wide code block or table in a note still has to be scrolled sideways on a small screen rather than reflowed.

How this is assessed

Self-evaluation, plus an automated accessibility scan that runs against the built site on every change and blocks a release on any serious or critical issue. Automated testing catches a minority of possible barriers, so it supplements manual review rather than replacing it.

Reporting a barrier

If something on this site prevents you from doing what you came to do, please tell us — it is the fastest way for us to fix it. Email contact@devkart.com with the page address and what happened. We reply to every message, and we will tell you what we are doing about it and when.

This statement covers this website. Accessibility of the software we build for clients is scoped per engagement, and the two products we operate publish their own statements at supaorder.com/accessibility and superapphq.com/accessibility.