Aktays.
Legal

What we target, what we have actually done, and what we know is still imperfect.

Last updated:

Our commitment

We design accessible products for our clients, so it would be difficult to justify not holding our own site to the same standard. This statement describes where it currently stands — including the parts that are not finished.

Conformance target

We target WCAG 2.2 Level AA. We believe the site substantially conforms, based on our own testing rather than a third-party audit. "Substantially" is doing real work in that sentence: it means we have tested thoroughly and have not commissioned an independent assessment.

What we have done

  • Semantic HTML with a single logical heading order on every page.
  • All content reachable and operable by keyboard, with a visible focus indicator that is never removed.
  • Text contrast meeting or exceeding AA against every background used on the site.
  • Animation and smooth scrolling disabled entirely for visitors whose system requests reduced motion.
  • Text that animates into view is present in the page from the start, so it is available to screen readers and search engines regardless of whether the animation runs.
  • Full right-to-left support in Arabic, using logical CSS properties rather than a mirrored stylesheet.
  • Form fields with real associated labels, errors announced to assistive technology, and no reliance on placeholder text as a label.
  • Typography that scales with the viewport and respects browser zoom up to 200% without loss of content.

Known limitations

We would rather list these than claim they do not exist.

  • The case-study artwork is decorative and carries no text alternative, because it conveys no information. If we replace it with real photography, that will need revisiting.
  • The custom cursor is decorative and appears only on fine-pointer devices; it is hidden under reduced-motion preferences, but it has not been tested against every assistive technology combination.
  • We have not commissioned an independent accessibility audit. Our testing is thorough but it is our own.

How we test

Keyboard-only navigation on every page, automated checks during development, colour contrast verified against the design tokens, and manual testing at 200% zoom and on small screens. Screen-reader testing is periodic rather than continuous.

Tell us if something is broken

If you hit a barrier on this site, please email us and describe what happened and what you were using. We treat accessibility reports as bugs, not as feature requests, and we will tell you when it is fixed.