Accessibility Statement

We build to WCAG 2.2 Level AA. This page says what that means here, what has actually been tested, and what has not yet.

What is built in

• Contrast is enforced automatically. Our brand purple fails AA for body text on our background at 3.71:1, so text uses a lighter tint at 5.55:1. A build check asserts every colour pairing on every commit and fails the build if one regresses
• Visible focus indicators on every interactive element
• Full keyboard operability, including the navigation menus, which open on focus and not only on hover
• A skip link to jump past navigation
• Semantic landmarks and headings, in order
• Reduced motion respected. Animation is suppressed for anyone whose system asks for that
• Colour is never the only signal. Severity indicators carry text labels as well as colour
• The contact form works without JavaScript, apart from the bot check, and offers two alternative routes when that is unavailable

What has been tested

Every one of these runs on every change, and a failure stops the change reaching this site rather than producing a ticket.

• axe against WCAG 2.0, 2.1 and 2.2 A and AA rules, across every page template at a mobile viewport
• Keyboard operability. The skip link is the first stop and targets the main content. Every focusable element gets a visible focus indicator, nothing traps focus, and no stop is an element you cannot see
• Colour contrast asserted across the whole palette at body text size, not only at large sizes
• Reduced motion. With the operating system preference set, every diagram renders its finished state rather than an empty box
• Touch. The menu that opens on hover for a mouse also opens on a tap, checked at tablet sizes

Two of those found real problems on this site rather than confirming it was fine. Every field on the contact form was suppressing its own focus indicator, so a keyboard user could not see where they were. And a colour used for dates and labels failed contrast at the size it was actually used, while passing the check it had been given. Both are fixed.

Known gaps

A full screen reader pass has not been completed. Automated checks catch roughly a third of real barriers. They cannot tell you whether an announcement makes sense in the order it arrives, and we would rather say that than claim conformance we have not verified.

• Screen reader testing across NVDA, JAWS and VoiceOver is outstanding
• Whether form errors are announced, as distinct from being present in the markup, has not been verified with a screen reader
• The Cloudflare Turnstile challenge on our forms is third-party markup we do not control. It is excluded from our automated checks because we cannot fix what it reports, and we have not audited it separately
• The free tools on our subdomains predate this site and have not been audited to the same standard

Telling us about a problem

Email sales@aptsecuritymanagement.com with what you were trying to do, the page, and what got in the way. We will acknowledge within two business days.

If something on this site is blocking you from reaching us, that is our failure and we will fix it. Meanwhile our booking page and email both work as alternatives.