Accessibility Not audited

Accessibility statement.

Our target is WCAG 2.2 Level AA. This page sets out what is implemented today, what has not been tested, and how to tell us when something does not work for you.

This page is not finished.

No independent accessibility audit has taken place, and no VPAT or conformance report exists. The features described below as implemented were checked in this site's own source code, which is not the same thing as being tested with real assistive technology. The formal conformance claim and the audit date are shown as placeholders because there is nothing yet to put in them.

Our target

WCAG 2.2 Level AA

We are building this site to meet the Web Content Accessibility Guidelines version 2.2 at Level AA.

That is a target, not a completed claim. Nobody independent has assessed this site against it.

A formal conformance claim will appear here only when there is an assessment behind it: the claim at [[CONFORMANCE_CLAIM]], assessed on [[AUDIT_DATE]] by [[AUDIT_ORGANISATION]].

There is no VPAT or Accessibility Conformance Report, because no audit has been carried out to produce one. If you need one for a procurement process, tell us and we will say honestly where we are.

Verified in the source

Each item below was checked by reading this site's own code before it was written down. Verified in code is not the same as tested with a real user, and the limitations section says so.

Skip link

Every page starts with a link that jumps past the navigation straight to the content. It stays off screen until it receives keyboard focus, then appears at the top left.

A real main landmark

Page content sits inside a single main element, which is what the skip link targets. Screen reader users can jump to it directly.

Visible focus

Keyboard focus draws a three-pixel outline with an offset, applied globally through focus-visible. No component removes it.

Navigation announced correctly

Menu triggers are buttons carrying aria-expanded and aria-controls, so assistive technology announces whether a menu is open and what it controls. The mobile trigger's label changes between Open menu and Close menu.

Reduced motion honoured

The stylesheet cuts animation and transition durations and disables scroll reveals when the reduce preference is set, and the script driving those reveals checks the same preference and shows content immediately instead of animating it.

Declared language

The document declares English as its language on the root element, so screen readers use the right pronunciation rules.

What is implemented, in detail

The same ground as the summary above, set out fully. Anything that has not been verified is in the limitations section instead.

Structure and navigation

Content sits inside one main landmark per page, and a skip link at the top of every page jumps to it.

Headings follow a single order per page: one page title, then section headings beneath it, without skipping a level.

Menus are buttons rather than links pretending to be buttons, and they carry the state and relationship attributes assistive technology needs to announce them.

Breadcrumb trails are marked as a navigation landmark with a label, and the current page is marked as current.

Keyboard and focus

Everything interactive on the site is reachable and operable with a keyboard.

Focus is always visible: a three-pixel outline with an offset, defined once and never removed by an individual component.

The skip link is the first focusable element on the page and becomes visible as soon as it receives focus.

Motion, images, and status messages

The reduced motion preference is honoured in two places, not one. The stylesheet disables the reveal and stagger animations and reduces every transition to effectively nothing, and the script that drives scroll reveals checks the preference and marks content visible straight away instead of animating it in.

Decorative images carry an empty alt attribute and are hidden from assistive technology, so they are not announced as unlabelled graphics.

Where the site shows a status message, such as a count of search results or the outcome of a form submission, it is placed in a live region so it is announced rather than only appearing on screen.

The tutorial marks the chapter you are on as current, and its progress indicator exposes a minimum, a maximum, and a current value rather than being a decorative bar.

Known limitations

These are the honest gaps. None of them is a placeholder, because each is a thing that has not happened rather than a value we are withholding.

What has not been tested

No independent audit. Nothing on this site has been assessed by a third party against WCAG 2.2 or any other standard.

No recorded testing with screen readers or other assistive technology. What is listed above was verified in code, which is not the same as watching someone use it. The plan for that testing is at [[ASSISTIVE_TECHNOLOGY_TESTING]].

Colour contrast has not been measured across every component and every state. We believe body text and headings meet the ratio, and we are not going to dress that belief up as a conformance claim.

Some controls use custom patterns, such as toggle buttons for choosing a download platform and a button list for tutorial chapters. They work with a keyboard, but they have not been checked against the full set of behaviours a screen reader user would expect.

What is out of scope today

This statement covers this website only. The Autom desktop application is pre-release, downloads are not open, and its accessibility has not been assessed. That assessment is at [[APPLICATION_ACCESSIBILITY_STATUS]].

The site is published in English only, and there is no translation.

There is no audio or video on this site, so captions, transcripts, and audio description do not currently apply. If media is added, they will.

Feedback

Tell us when something does not work

If you cannot use part of this site, we want to hear about it. Tell us what you were trying to do, which page you were on, and which browser or assistive technology you were using. That is enough for us to start.

Write to [[ACCESSIBILITY_CONTACT_EMAIL]]. We aim to reply within [[ACCESSIBILITY_RESPONSE_TIME]].

Until that mailbox is confirmed, the Contact Sales form is the only route this site can offer you. Be aware of what that means: the form forwards to whatever destination has been configured for it, that destination is a deployment setting rather than something visible in this site's code, and where enquiries actually land is at [[CONTACT_FORM_DESTINATION]]. If nothing is configured, the form will tell you plainly that your message was not sent.

If you need something published here in another format, ask and we will try to provide it.

If you are not satisfied with our response, the escalation route that applies in your jurisdiction is at [[ACCESSIBILITY_ENFORCEMENT_ROUTE]].

About this statement

This statement is published by [[LEGAL_ENTITY_NAME]] and was last reviewed on [[STATEMENT_REVIEW_DATE]].

It was written by inspecting this site's own source code. It was not produced by an audit, and it should not be cited as one.

We will update it when the site changes and when an assessment is carried out.

Get in touch

Until the accessibility mailbox is confirmed, Contact Sales is the only route this site offers. Say that your message is about accessibility.

Contact Sales Security overview

Neoteric's promise, including human control and transparency