Discuss a project
Legal

Accessibility Statement

What we have tested, what passes, what does not, and how to tell us when something gets in your way.

ASTRI DEVS LTD is the controller of personal data described in this document, unless it says otherwise.

Effective from 19 August 2026. Last reviewed 19 August 2026. Review cycle: every six months, and after any significant change to the website.

Our commitment

We build accessible services for clients, so it would be difficult to justify an inaccessible website of our own. We want everyone to be able to use this site, including people using screen readers, magnification, speech recognition, keyboard-only navigation, or a browser configured to reduce motion or increase text size.

Standard we work to

We build this website to meet WCAG 2.2 level AA. We apply the same standard to the services we deliver for clients, whether or not a specific accessibility regulation applies to that service, because it produces a better result than treating accessibility as a compliance exercise.

Compliance status

Based on the testing described below, we believe this website conforms to WCAG 2.2 level AA, with the exceptions listed under known limitations.

We have deliberately not written that this website is "fully compliant" or "certified". No automated tool can establish full conformance, and there is no certification scheme that would make such a claim meaningful. What we can tell you is exactly what we tested and what we found.

How we tested

Testing was last carried out on 19 August 2026 by us, covering every page on the site.

  • Automated testing. An axe-core accessibility scan runs against every page as part of our automated test suite, at both mobile and desktop widths. The build fails if a violation is introduced.
  • Keyboard testing. Automated keyboard testing of every interactive element, including the navigation drawer, the privacy preferences dialog and the contact form — driving the page with the keyboard alone and asserting focus order, visible focus, focus trapping, focus restoration and Escape behaviour. These run in our test suite on every change.
  • Structure. Heading order, landmark regions, form labelling, link text and the accessible names of controls were checked page by page.
  • Contrast. Every text and interface colour pair in the design system is asserted against the WCAG contrast minimums by an automated test, so a colour cannot be changed to a failing value without the build failing.
  • Reflow and zoom. Every page was tested from 320 px to 1920 px wide, and at 200% zoom, with an automated check that no page scrolls horizontally.
  • Reduced motion. Tested with the reduce-motion preference enabled, which stops the background animation and all transitions.

Accessibility features

  • A skip link to the main content, as the first thing in the tab order.
  • Semantic landmarks, one h1 per page, and headings in a logical order.
  • Visible focus indicators on everything focusable, at a contrast above 3:1.
  • Every form control has a visible label, errors are announced, the first error receives focus, and what you typed is preserved when validation fails.
  • All text meets at least 4.5:1 contrast against its background; large text and interface components meet at least 3:1.
  • Touch targets are at least 44 px in the smaller dimension.
  • Form inputs use a 16 px minimum font size, which stops iOS Safari zooming the page when a field receives focus.
  • The background animation is decorative, hidden from assistive technology, and stops entirely when reduced motion is requested. No content depends on it.
  • No content flashes, auto-plays, moves without your input, or times out.
  • Colour is never the only way information is conveyed.
  • Text can be resized to 200% without loss of content or functionality.

Known limitations

We are aware of the following.

  • Dark theme only. The site is presented in a single dark theme. A light theme is not offered, because a partially designed second theme with untested contrast would be worse than one carefully built theme. Browser and operating system tools that invert or adjust colours work with the site, and the print stylesheet produces black text on white for anyone who prefers to read on paper or save a page as a PDF. We will keep this under review.
  • Screen reader testing. Our testing to date is automated plus manual keyboard and structural testing. We have not yet completed a full test pass with JAWS, NVDA and VoiceOver. That is scheduled, and this statement will be updated with the results.

If you find something that is not on this list, we would genuinely like to know. We have not listed problems we are unaware of, and we are not going to pretend the list is exhaustive.

Getting information another way

If any information on this site is not accessible to you, email info@astridevs.co.uk and tell us what you need and the format that works for you. We will provide it another way — plain text, a document in a format your software reads, large print, or simply the answer in an email. There is no charge and you do not need to explain why.

Reporting a problem

Email info@astridevs.co.uk. Please tell us the page, what you were trying to do, and what got in the way. It helps if you can say what browser and assistive technology you were using, but do not let that stop you reporting something.

We aim to acknowledge within five working days and to tell you what we are going to do about it and when. Issues that block someone from using the site are fixed as a priority rather than added to a backlog.

Preparation and review

This statement was prepared on 19 August 2026 and last reviewed on 19 August 2026. It is reviewed every six months, and after any significant change to the website.