Accessibility
Accessibility statement
We want as many people as possible to be able to use code2box.com. This statement explains how accessible the site is, what we know is not right yet and how to tell us about a problem.
Prepared 7 October 2026. Next review by 7 April 2027.
At a glance
- Standard
- WCAG 2.2, level AA
- Web Content Accessibility Guidelines
- Status
- No known failures on the pages we tested
- Not yet tested with screen reader users
- Last tested
- 7 October 2026
- Automated and keyboard checks
Using this website
This statement covers code2box.com, the website of Code2Box, a trading name of Lingo Service Translations Ltd. It does not cover the client portal or the websites of our own products (LingoVoice, Lingo Service and Arabic Translation UK), which are separate websites.
You should be able to:
- use the site with a keyboard alone, with a visible outline showing where you are
- zoom in up to 400% without having to scroll sideways or losing any text
- increase the spacing between letters, words and lines without text being cut off
- use a screen reader: every page has one main heading, clear headings, labelled form fields, and links and buttons that say what they do
- stop the animations by turning on reduced motion in your device settings
- read our councils page in Welsh, with the page marked as Welsh for screen readers
How accessible this website is
We check code2box.com against the Web Content Accessibility Guidelines (WCAG) version 2.2, level AA, the standard we build public-sector services to. On 7 October 2026 every page we tested passed our automated checks at laptop and phone sizes, and our keyboard checks found no remaining failures.
We have not yet tested the site with people who use screen readers, speech recognition or other assistive technology, on real phones or in Firefox, so we do not yet describe it as fully compliant. We are a private company, so the Public Sector Bodies Accessibility Regulations do not apply to this website, but we hold it to the same standard we use for the systems on our public sector page.
What is not right yet
We know about these things and plan to improve them:
- The outlines of form fields, such as the boxes on the contact form and the newsletter sign-up, are faint against their background. Each field has a label for screen readers and a visible label or hint text, so you can still find it.
- Text sizes are set in pixels, so changing only the text size in your browser settings does not make the text bigger. Zooming the page does.
- On the Welsh councils page, the menu, the footer, the cookie bar and the chat assistant are in English. They are marked as English, so a screen reader reads them with an English voice.
- The contact form shows the browser's own message when a required field is empty or an email address is not valid, not a message written into the page.
- Some small text inside the homepage's animated product demos has low contrast. These demos are pictures of other software and are hidden from screen readers.
How we tested
We prepared this statement on 7 October 2026 from our own testing of every page on code2box.com, in Chromium (the engine behind Chrome and Edge) and, at phone sizes, also in WebKit (the engine behind Safari):
- automated checks with axe-core against WCAG 2.2 A and AA, on every page at a laptop width (1536 pixels) and a phone width (390 pixels)
- a check of every page at five screen sizes for content that runs off the side of the screen
- checks by hand with a keyboard: the order in which items take focus, that the focus outline is visible and is not hidden behind the cookie bar or the chat button, the cookie bar, the chat assistant, the contact form and the phone menu
- reduced motion, 200% zoom, a 320 pixel wide screen and increased text spacing
No testing with screen reader users, speech recognition users or disabled people has been done yet.
Reporting a problem
If you find a problem we have not listed, or you cannot use part of this website, email hello@code2box.com and tell us the page and what went wrong. If you need something on this website in a different format, ask in the same way.
Preparation of this statement
This statement was prepared on 7 October 2026. We will review it by 7 April 2027, and sooner if we change the website in a way that affects it.