Accessibility

We aim to meet WCAG 2.1 Level AA. We have not commissioned a formal audit, so this page describes what we have actually done and what we know is still short, rather than claiming conformance we cannot evidence.

What works

• A skip link to the main content is the first thing keyboard focus reaches on every page.
• Form controls in the tools have programmatic labels, so a screen reader announces what each field is for rather than reading a placeholder.
• Results update in a live region, so recalculating a value or finishing a conversion is announced instead of changing silently.
• Errors are announced as alerts and are tied to the field that caused them.
• Focus is always visible, with an indicator that meets the 3:1 contrast the guidelines ask for.
• Page text can be selected and copied, including formulas, worked examples and FAQ answers.
• Layouts reflow to a phone-width screen without horizontal scrolling.

Where it is still weak

• The image tools that use a canvas — cropping and colour picking — are easier with a pointer than with a keyboard, even though numeric fields now provide a non-pointer path.
• Some secondary interface text is smaller than we would like. We are raising it as we touch each component.
• We test with keyboard navigation and browser tooling. We do not have regular testing with real assistive-technology users, which means we will miss things that only they would notice.

Tell us what breaks

If something here is unusable for you, that is a bug and we want it. Email kligtechnologies@gmail.com with the page address, what you were trying to do, and the browser and assistive technology you use. Accessibility reports go to the front of the queue alongside wrong-answer reports — see the contact page.