Accessibility
The site is built to work with a keyboard, a screen reader, a magnifier, or none of the above.
Our target
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA across the site. Accessibility is treated as part of building a tool, not a later fix.
What is in place
- Keyboard first. Every control is reachable and operable by keyboard, focus is always visible, and a skip link jumps straight to the main content.
- Works without JavaScript. Calculators submit as ordinary forms and render results server-side; JavaScript only adds live recalculation and convenience buttons.
- Screen-reader labelling. Every field has a real label, results announce themselves through a live region, and charts carry text alternatives with the same numbers available in a table.
- Contrast and colour. Text and interface colours are chosen against WCAG contrast thresholds in both light and dark themes, and colour is never the only way information is conveyed.
- Respects your settings. Dark mode follows your operating system, and animation is disabled when you ask for reduced motion.
- Scales. Layout and type use relative units, so the site reflows cleanly at 200% zoom and on narrow screens.
Known limitations
- Long amortisation and schedule tables are wide; on small screens they scroll horizontally.
- Advertising is supplied by a third party, so we cannot guarantee the accessibility of an individual ad unit.
- Some data tables are dense; we are progressively adding row and column headers to improve screen-reader navigation.
Full conformance cannot be established by automated checks alone: it requires manual testing with assistive technologies and expert accessibility review. We use automated checks continuously and are extending manual testing across the tool catalogue.
Tell us about a barrier
If something on Ayduke is hard or impossible to use, email support@ayduke.com with the page and what happened. Accessibility reports are prioritised, and we will tell you what we can fix and when.