Accessibility

What we are aiming at

We build CarrierNote to meet WCAG 2.2 level AA, the international standard for making a website usable by people with a disability. Aiming at it is not the same as being audited against it, and nobody independent has tested us, so read this page as our own honest account rather than a certificate.

It covers the marketing site you are reading and the app you sign in to.

What is in place

• The app is built to be worked from a keyboard. Menus, tabs, and dialogs follow the standard keys, and the item you are on is visibly outlined.
• Text colours are measured against the contrast standard rather than picked by eye.
• Buttons and picture-only controls have a name a screen reader reads out, and it matches the words printed on the screen.
• Tables keep their column headings on a phone. The heading row is hidden from the eye rather than removed, so a screen reader can still tie a cell to its column.
• Nothing important is signalled by colour alone. A hazardous load, for instance, is marked by a symbol and the word as well as a red chip.
• Animation respects your device setting. If you have asked your phone or computer to reduce motion, the moving parts stop moving.
• Pages are built to reflow when text is enlarged or the window is narrow, so the app works zoomed in and on a phone in a cab.

What we know is not right yet

• No independent audit. Nobody outside the team has tested the app against the standard, and we have not had it checked by a disabled user or a specialist.
• Our own testing is keyboard use plus automated browser checks. We have not run a full test with a screen reader.
• A confirmation message may not be read out when it appears over an open panel, such as the note saying a transfer note has been saved. It is on screen, and the page behind it updates as well, so nothing depends on hearing it.
• The transfer notes and consignment notes we produce are PDFs without the internal tagging a screen reader needs, so they read poorly. Ask us and we will send you the same information in a format that works, within one working day. For an office issuing notes every day that is a poor answer and we know it, so tell us if it affects you: that is what moves it up the list.

How we check

Two things run against the app. The first is the accessibility audit built into Chrome, which we last ran in the summer of 2026 over five of the screens people use most, among them the dashboard, the team page and the form a movement is recorded on. It finished with nothing failing. The second is a check in our own release process that works out the contrast of every text colour we use and stops the release if one falls under the standard.

Neither replaces a person. If something is awkward for you and both of those say it is fine, the checks are wrong and you are right.

The question we cannot answer yet is whether somebody who relies on a screen reader could do a full day's work in the app, because we have not sat with anybody who does. If that is you, or somebody in your office, tell us and we will test it with you rather than guess.

Tell us about a problem

Email support@carriernote.co.uk and say what you were trying to do, which page you were on, and what got in the way. We answer within one working day.

If a fix will take a while, we will tell you and give you a way round it in the meantime, which often means one of us doing the job for you. There are two of us and no separate complaints department, so if our answer is not good enough, say that in as many words: we will treat it as a complaint rather than another support ticket, and answer it in writing.

Our support page has the other ways to reach us.

About this statement

The date at the top is when this page was last gone over. We review it at least once a year, and whenever something on the lists above changes.