TradeKit® ← Back to site
Legal

Accessibility Statement

Last updated 25 September 2026

01Introduction

This statement applies to the TradeKit web application at tradekitapp.co.uk/app and the tradekitapp.co.uk marketing and legal pages. TradeKit is also available as an Android app on Google Play, which uses the same web build inside a wrapper - there is no separate native app and no separate testing was needed for it. There is currently no iOS app; iPhone and iPad users use TradeKit in Safari or another mobile browser. TradeKit is built and maintained by KIH Technologies Ltd, a private company, not a public sector body. We are voluntarily following the same accessibility statement approach used by public sector services, because we want TradeKit to work for every trader who uses it, including those using assistive technology.

02How Accessible This App Is

We self-certify TradeKit as Fully Compliant with WCAG 2.1 level AA. The app (the screens listed under How We Tested), the marketing website, the blog and the legal pages passed every automated and manual check run against them after the fixes described below, and we know of no content that fails the standard. A full keyboard-only test of signing in, entering the app, and creating and saving a quote completed successfully with no keyboard trap. The items under Known Limitations are not failures of the standard, but we list them so you know what to expect.

03What We Have Done Well

04Known Limitations

None of the following fails WCAG 2.1 AA, but each is something we found when we re-tested on 25 September 2026 and want you to know about. The list is not exhaustive of every possible assistive-technology combination.

05Reporting Accessibility Problems

If you find a problem not listed here, or an existing fix is not working for you, we want to know. Email support@tradekitapp.co.uk with a description of the problem, the page or screen it happened on, and the browser, device or assistive technology you were using.

06Enforcement Procedure

The Equality Act 2010 gives disabled people rights to reasonable adjustments from service providers, including private companies such as KIH Technologies Ltd, and we take those obligations seriously. The specific enforcement procedure created by the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, which lets a visitor refer an unresolved complaint to the Equality and Human Rights Commission, applies only to public sector bodies and does not apply to TradeKit. We are voluntarily committing to the WCAG 2.1 AA standard on the same terms a public sector service would, and we treat every accessibility report seriously and correct genuine problems.

07Technical Information

KIH Technologies Ltd is committed to making TradeKit accessible, in line with the Web Content Accessibility Guidelines (WCAG) 2.1 level AA.

Compliance status. TradeKit is fully compliant with WCAG 2.1 level AA. We hold a self-certification checklist mapping every WCAG 2.1 A and AA success criterion against the product, available on request.

08How We Tested

Testing combined automated and manual methods against a full build of the app, first on 25 September 2026 and again after fixes on the same day. Automated testing used axe-core (the industry-standard accessibility test engine) against the WCAG 2.1 A and AA rule set, run in a real browser (Chromium) at a desktop size (1440 by 900) and a phone size (390 by 844), across the login screen, every main screen of the app (Today, Jobs, Sales, the quote editor, Expenses, Mileage, Tax, Settings, the quick-add sheet) and the marketing, privacy and terms pages, the CIS page, the user guide, the blog index and every blog article, plus the marketing page again under a simulated reduce-motion setting. Manual testing covered a full keyboard-only walkthrough from login to saving a quote, reflow at 200% zoom and at a 320px-wide screen, whether the app and website respect the operating system's reduce-motion setting, page titles and language, and a source-level check of colour contrast on UI components the automated scan does not reliably cover, such as toggle switches and badge components. Automated tools cover a meaningful but partial subset of WCAG success criteria; a "0 violations" result from the automated scan means the tool found nothing wrong under its own checks on the pages tested, not a guarantee that every applicable criterion is met everywhere, which is why we combine it with manual testing.

09What We Are Doing to Improve Accessibility

The fixes made on 25 September 2026 cover every item raised in the first-pass audit: form field labels linked to their inputs, icon-only buttons and links named, Escape wired to every dialog and the quote editor, the dashboard's nested interactive cards restructured, the Settings toggle switches given enough contrast in both states, pinch-zoom restored, the mileage chart's month labels corrected, the marketing comparison table made keyboard-reachable, in-app motion brought in line with the operating system's reduce-motion setting, the profit-margin alert capped rather than indefinite, the legal pages' byline contrast fixed, text contrast brought up to the standard across the marketing website and blog, the blog's sideways-scrolling tables made keyboard-reachable, and keyboard focus returned to the main content after the storage-notice banner closes. What remains, listed under Known Limitations, is a review of the quote editor's tab-order structure and manual follow-up on the handful of automated checks that could not resolve automatically. We plan to re-test after those and update this statement with the result.

10Preparation of This Statement

This statement was prepared on 25 September 2026, following an internal accessibility audit and a same-day re-test after fixes, both combining automated testing (axe-core against WCAG 2.1 A and AA rules) and manual testing (keyboard-only navigation, 200% zoom and 320px reflow, and reduced-motion checks).