Accessibility

We build to WCAG 2.2 Level AA, and we hold client work to the same standard — accessibility is an acceptance criterion on our engineering engagements, not a cleanup task at the end.

Specifically, this website:

• Uses semantic HTML — one h1 per page, headings in order, and landmark elements, so screen readers can navigate by structure.
• Is fully keyboard operable. The navigation and FAQ disclosures are native HTML elements rather than scripted widgets, so they work without JavaScript.
• Provides a visible focus indicator on every interactive element, and a skip link as the first focusable item on the page.
• Meets AA contrast ratios for body text. Muted copy sits at 4.8:1 or better against its background.
• Respects prefers-reduced-motion — all animation, including the footer waves and hero entrance, stops for users who ask their system to reduce motion.
• Labels every icon-only control, including the social links and the mobile navigation trigger.

Brand red (#e40014) measures 4.87:1 against white, which passes AA for normal text. Against black it measures 4.31:1, which passes AA for large text but falls below the 4.5:1 threshold for normal text. It is therefore used on dark backgrounds only at large sizes or for non-essential decoration, never for body copy.

Long-form article content is rendered from an editor, so a contributor can introduce a heading level out of order or an image without alternative text. The editor prompts for alternative text and does not enforce it, which means individual posts may contain issues this statement does not cover.

Where a page embeds a third-party service in future — a video player, a map, a scheduling widget — its accessibility is determined by that provider rather than by us. None are embedded at present.

This is a self-assessment. No independent audit has been commissioned, and a self-assessed statement carries less weight than an external one. Several procurement processes require an independent audit, and if yours does we will say plainly that we do not currently have one rather than implying otherwise.

If any part of this site is difficult to use, email hello@akshintelligence.com with the page and what happened. We treat accessibility reports as bugs, not feedback, and will confirm receipt within one business day.