Tool Testing Methodology
The checks each tool goes through before launch and again after changes.
Updated
Each tool is tested with typical and edge-case inputs, checked in current Chrome, Firefox, Safari and Edge and on mobile, and watched in the browser's network panel to confirm your data stays on your device.
Functional testing
Each tool is run on typical files and on edge cases, including very large and very small inputs, to confirm the results are correct and repeatable and that bad input produces a clear error.
Privacy check
We open the browser's network inspector while using each interactive tool to confirm it works locally and sends none of your file's contents. The only outside requests load code, such as a library from a CDN, and never carry your data.
Browsers and devices
Tools are checked in current Chrome, Firefox, Safari and Edge, and on mobile, to make sure they behave the same and the layout fits each screen size.
Speed
We keep an eye on page weight and run time. A tool's code loads only on its own page, and outside libraries load when the tool needs them rather than up front.
Accessibility
We test keyboard navigation, visible focus, labels and colour contrast. Details are in the Accessibility Statement.