Accessibility statement

How accessible the website and the CallCamIT application are, what is not yet, and how to tell us — in the form public sector bodies use, so that theirs can rely on it.

This accessibility statement applies to the website callcamit.com and to the CallCamIT Windows application in all three of its editions: the User edition (the chat window everybody on an estate gets), the IT edition (the desk's console) and the Domain edition (the server that keeps everyone's tickets). Both are made by CALLCAMIT LTD.

This is our statement about our own website and software. It is not the statement CallCamIT generates for your organisation from the Controller (Compliance, then Accessibility statement): that one is about your use of it and is yours to publish. The two are different documents.

We want as many people as possible to be able to use this website and this application. That means you should be able to:

change colours, contrast levels and fonts in your browser, and on Windows use display scaling of 100% to 200% without text or controls being lost;
zoom the website in to 300% without the text spilling off the screen;
navigate the website and the application using just a keyboard;
navigate the website and the application using a screen reader such as Windows Narrator or NVDA;
read the website with text-to-speech software.

We have also made the text as simple as we can. AbilityNet has advice on making your device easier to use if you have a disability: mcmw.abilitynet.org.uk.

How accessible this website and application are

The website. Every page declares its language as British English, has one heading structure, and uses native links, buttons and form controls, so browser and assistive-technology behaviour is the standard one. The front page has a "skip to content" link that appears when it receives keyboard focus. Tabbed controls carry their state in aria-pressed and aria-selected, so the state is announced as well as shown. Animations on the site are switched off when the operating system's "reduce motion" setting is on. Colours are chosen against the WCAG 2.2 AA contrast thresholds.

The application. CallCamIT is built on Microsoft's Fluent 2 design language with Qt, which exposes every control to Windows UI Automation, the interface screen readers use.

Keyboard operation. Every control is a standard Qt control reachable with Tab and Shift+Tab and operable with Space, Enter and the arrow keys. Menus open from the keyboard and dialogs close with Escape.
Visible focus. Text boxes show a two-pixel underline in the brand colour when they hold focus. Buttons, the Controller's commands and navigation rail, lists and tables draw the application's own focus ring, in the text colour rather than the brand blue so that it is never mistaken for a selection, when they take focus from the keyboard; a mouse click leaves no ring, as on the web. An automated test (tests/test_app_chrome.py) fails the build if a kind of control looks the same with keyboard focus as without it.
Contrast, measured rather than eyeballed. An automated test (tests/test_contrast.py) runs on every build and measures the contrast ratio of every foreground-and-background pair the interface actually renders, in the light theme and the dark theme, against the 4.5:1 threshold WCAG 1.4.3 sets for body text, and the focus ring, the text-box underline and the theme's chart colours against the 3:1 WCAG 1.4.11 sets for non-text marks. The light theme is also held to the stricter APCA thresholds. A build whose colours fall below them does not ship. The dark theme's primary button was found this way at 2.81:1 and corrected.
Names a screen reader can say. Buttons with a picture and no text (the settings cog, the app launcher, the permissions shield, the "show details" control on each step Cam takes) each carry an accessible name describing what they do rather than what they look like. An automated test (tests/test_accessibility.py) fails the build if one is added without a name.
Display scaling. The interface is drawn in scalable units and follows the Windows display scaling setting (100%, 125%, 150% and above), so text and controls grow together.
State by more than colour. In the ticket list a ticket's status is shown as an icon beside the status in words, never as a colour alone, and a chart's legend names each colour it uses.
Charts that say their numbers. Each chart on the Controller's overview carries an accessible name and a description with the figures it plots, which a screen reader reads, and pointing at a bar shows its value. An automated test (tests/test_controller_ux.py) checks both.

How accessible this website and application are not

We know some parts are not fully accessible. Each item here is a defect we intend to fix, and the list is kept short by fixing things rather than by leaving them out.

In the application:

New messages are not announced. When Cam replies in the conversation, a screen reader is not told; you have to move into the transcript to hear the new message. The interface has no live region. We intend to announce new replies.
Windows high-contrast themes are not honoured. The application draws its own two palettes, the light theme it starts in and a midnight (dark) theme, and does not switch to the colours a Windows high-contrast theme sets. (WCAG 1.4.11, Non-text contrast, in forced-colours mode.)

On the website:

The site assistant in the corner of the front page and the walkthrough time picker have had an automated check and a keyboard pass, but no screen-reader pass; we do not yet claim them as conformant.
The generated document pages (this one, the security assessment, the data processing agreement and the compliance page) have a main landmark but no "skip to content" link; their content starts directly after one link, so the cost is small, but a skip link is still owed.

Nothing on the website or in the application is excluded from the scope of this statement, and neither relies on content we do not control.

What we are doing to improve accessibility

The two automated tests named above run on every build and stop a regression from shipping. Each item in the list of known defects is a tracked piece of work, and this statement is regenerated from the same text the application carries, so a fix appears here and in the application at once. We review this statement whenever a listed defect is fixed and at least once a year.

Feedback and contact information

If you find something you cannot use, or you need any part of the website or the application in a different format (large print, plain text, or a walkthrough by phone), email support@callcamit.com. We reply within one working day, and we will tell you what we are going to do about it and when.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the "accessibility regulations"). We say plainly that CallCamIT is a private company and not a public sector body under those Regulations; we publish this statement in their form anyway, so that a public sector body using CallCamIT can rely on it when writing its own statement, and because the Equality Act 2010 duty to make reasonable adjustments applies to us whatever our sector. If you are not happy with how we respond to a complaint, contact the Equality Advisory and Support Service (EASS): equalityadvisoryservice.com.

Technical information about this website and application's accessibility

We are committed to making our website and application accessible, and we publish this statement in the form the accessibility regulations ask of public sector bodies.

Compliance status

The website callcamit.com and the CallCamIT application are partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed above. We have not had a third-party audit, and we do not claim one.

Preparation of this accessibility statement

This statement was prepared on 14 September 2026. It was last reviewed on 28 September 2026.

The website and the application were last tested on 14 September 2026. The testing was carried out by us, CALLCAMIT LTD, and consisted of the automated tests that run on every build (contrast ratios, accessible names on icon-only controls, keyboard operation of the window that shows this statement, and the checks over the website's generated pages) together with our own keyboard pass through the application's windows. We have not yet made a manual pass with a screen reader (Windows Narrator or NVDA) through the website or the application; that is the next test we owe, and this statement will say so when it has been done. No external organisation has audited either.