Accessibility

1Our commitment

We treat accessibility as part of building the site, not as a pass at the end. Accessibility issues are logged and fixed alongside other defects, and the automated check runs against both colour themes because a fix in one can break the other.

We are a supplier to government and to enterprise, and both ask about this. That is a reason to measure honestly, not a reason to claim more than we can show.

2The standard we work to

In short: WCAG 2.1 Level AA. We are partially conformant: some content does not yet fully meet it.

The Web Content Accessibility Guidelines define how to make web content more accessible. WCAG 2.1 Level AA is the level most commonly referenced in procurement and in law, and it is what we build against.

"Partially conformant" is the honest description of where we are: most of the site meets the standard, and the parts that do not are named in section 4.

3How we test, and what the last test found

We run axe-core against eight pages chosen to cover every kind of page on the site — the homepage, a service landing, an industry landing, the editorial hub, the product page, About, Contact and a legal page. Each is tested in both the light and dark themes, because they use different colour tokens.

Standard tested

WCAG 2.1 Level A and AA

Tool

axe-core

Coverage

8 representative pages, both themes — 16 page renders

Issues before this pass

91

Issues after this pass

4

Last run

28 August 2026

What that pass fixed

• The primary button on every page. White text on the brand blue measured 2.93:1, below the 4.5:1 required — on the most important control on the site. Light mode now uses a darker blue already in our palette at 4.64:1; dark mode keeps the bright brand fill, where its dark text clears 6.45:1.
• Star ratings on client reviews carried a text label on an element that is not permitted to have one, so assistive technology was required to ignore it. They are now marked as images with an accessible name.
• Small labels across the site — eyebrows, kickers, category tags — used the brand blue as text at sizes where it measured between 2.7:1 and 3.7:1. They now use the darker text blue, which meets AA on both themes.
• Links inside body text on the privacy notice relied on colour alone to be distinguishable. They are now underlined.

What automated testing does not cover

Automated tools find roughly a third of WCAG issues. They cannot judge whether alt text is meaningful, whether a reading order makes sense, or whether a keyboard journey through a complex menu is workable. Anything not listed in section 4 is untested rather than confirmed passing, and we say so deliberately.

4Known issues

In short: Four automated issues remain, on two pages. All are low-contrast small text.

• About — a short uppercase label in the principles section uses the brand blue at roughly 2.9:1 against white, below the 4.5:1 required at that size.
• About — a small numeric marker uses the brand blue at roughly 2.7:1 against a pale ground.
• WorkNotes Plus — a category label on the light card variant falls below the required ratio.

These are scheduled for the next accessibility pass. None of them prevents a page being read or a task being completed; they make small labels harder to read than they should be.

Areas we have not fully assessed

• A full manual screen reader pass across every page, with NVDA, JAWS and VoiceOver.
• Third-party components we embed, including the chat widget and the Salesforce web-to-lead form, which we do not control.
• Video content, which does not currently carry captions or audio description. Our videos are ambient background footage with no spoken content or information conveyed only in audio.
• PDF documents, such as the ISO certificates. These are scans provided by the certifying body; the certificate details are also stated in the page text.

5What the site already does

• Semantic HTML with real headings, landmarks and lists, so structure is available to assistive technology rather than implied by styling.
• A visible focus indicator on interactive elements, so keyboard users can see where they are.
• Reduced motion is respected: where you have asked your system for less motion, the smooth scrolling and entrance animations do not run.
• Both a light and a dark theme, with colours defined as tokens so contrast is managed in one place.
• Text that reflows and remains readable when zoomed or when the window is narrow, without horizontal scrolling.
• A plain-Markdown version of every page, which is often the easiest thing for a text-based or assistive tool to read.

6Tell us about a barrier

In short: If something on this site stops you doing what you came to do, we want to hear about it.

Email Contact@synconai.com. It helps if you can tell us the page, what you were trying to do, and what happened — and, if you know it, the browser and any assistive technology you were using.

We aim to acknowledge accessibility reports within 5 business days and to tell you what we can fix and when. If something will take time, we will say so rather than leave you waiting.

If you need information from this site in another format — a document read to you, or content supplied another way — ask and we will arrange it.

You can also write to us:

7If you are not satisfied with our response

Tell us, and we will escalate it internally rather than leave it in the same queue.

You may also raise the matter with the relevant body in your jurisdiction. In Australia that is the Australian Human Rights Commission. In the United States, complaints about accessibility may be directed to the relevant federal or state agency.

8About this statement

This statement was last updated on 28 August 2026, using the results of an audit run on the same day.

It is reviewed whenever we make a substantial change to the site, and the numbers in section 3 are regenerated from an actual audit rather than edited by hand. If those numbers look stale, they probably are — please tell us.