Legal
Accessibility
Ninja SMS should work for everyone, including people who use a screen reader, a keyboard instead of a mouse, magnification or reduced-motion settings.
Last updated 24 October 2026
The standard we aim for
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA across the website and the signed-in dashboard.
What we have done
- Every public page and every dashboard page was checked with automated WCAG 2.2 AA testing (axe-core) on 24 October 2026, and the issues found were fixed.
- Text and buttons meet the AA contrast ratios, form fields have labels, and controls have names a screen reader can read.
- Links, buttons and form fields show a visible focus outline, and the public pages and sign-in were checked with a keyboard alone.
- Animations stop when your device asks for reduced motion.
- Pages use headings and landmarks, so a screen reader can jump between sections.
Known limitations
- The interactive API reference for staff is a third-party component and may not be fully accessible; the same information is on the public API documentation page.
- The sign-up and recovery forms use a bot check from Cloudflare. If it does not work with your assistive technology, contact us and we will help you open the account.
- Automated testing does not catch everything. We have not yet completed a full review with a screen reader, or a keyboard-only run through every step of buying and topping up.
Report a barrier
If something on Ninja SMS is hard or impossible to use with your setup, use our contact form and tell us the page and what happened. We aim to reply within 5 working days and to fix what we can; until then we will help you get done what you came to do.