Legal · Accessibility
Accessibility statement
How accessible this site is, as measured on the date below — what passes, what does not yet, and how to tell us about a problem.
What this statement covers
This statement covers the public pages of ondlingua.com — the pages you can read without signing in. The client, interpreter and officer portals sit behind a login and are not covered by the test described here. We will extend the statement to them once they have been tested the same way.
How accessible the site is
On the automated test described below, every public page passes every check for WCAG 2.2 level A and AA, at desktop and phone width, including both forms while they are showing errors. On 2 October 2026 we also went through the public pages by keyboard alone. We do not call the site fully conformant on that basis, because neither test covers everything the guidelines ask for; the limits of what we have tested are set out below. What is in place: every page declares its language, so screen readers read it in the right voice; the first thing a keyboard reaches on every page is a link that skips to the content; every control can be reached and worked by keyboard, and shows where the focus is; the menus say whether they are open, keep the focus where it should be, and close on Escape; a form that cannot be sent says so aloud, marks each field that needs attention and takes you to the first; animation and other movement is switched off for readers who have asked their device to reduce motion; pages are built from headings, lists and landmarks rather than layout tables; every image carries a text description; nothing scrolls sideways at the narrowest phone width, which is what a page looks like at four times zoom; and body text, headings, labels, links and buttons all meet the minimum contrast the guidelines require.
What is not yet accessible
Nothing we know of. That is a statement about what we have found, not a promise that nothing is there. The keyboard pass on 2 October 2026 found six things the automated test cannot see, and all six were fixed the same day and tested again: there was no link to skip past the header; the Log in menu was announced as a menu but did not behave like one, and closing it with Escape lost your place on the page; the phone menu opened without taking the keyboard focus, so the focus wandered the page hidden behind it; both forms showed their errors as coloured words only, with nothing announced and no link between a field and its message; the error text on the interpreter application form was too faint against its dark background; and one group of choices on the quote form was labelled as a single field. The first automated run, on 24 September 2026, found two things: the small grey labels used for section markers, captions and footnotes, and a few coloured status words, sat just below the minimum contrast the guidelines require (WCAG success criterion 1.4.3), and one list on the home page was built from the wrong elements. Both were fixed that day. If you find something these tests cannot see, the section at the end says how to tell us.
What we have not tested
We have not yet listened to the site with a screen reader: the keyboard pass checked what a screen reader is told (names, roles, states and announcements), not how it sounds in use. We have not tested with voice control or a screen magnifier, we have not tested with disabled people, and we have not commissioned an external audit. When any of those is done, this page will say what was found.
How this was tested
Automated: the public pages were tested on 24 September 2026 and again on 2 October 2026 with an automated accessibility checker (axe-core 4.11) against the WCAG 2.0, 2.1 and 2.2 level A and AA rules and the checker's best-practice rules, at desktop width and at phone width, on the site as published that day. By keyboard: on 2 October 2026 every public page was gone through with the Tab, Enter and Escape keys only, checking the order of the stops, that each one shows the focus, the two menus, both forms sent empty, the questions on the FAQ page, the heading structure of each page, the size of each link and button, and the page at the narrowest phone width. The tests were carried out by OndLingua, not by a third party.
Tell us about a problem
If you find something on the site you cannot use, or you need any of our information in a different format, write to [email protected] and tell us which page and what happened. We will reply, tell you what we will do about it, and fix what we can.
Last updated · 2026-10-02 · Questions: [email protected]