Accessibility is a
first-principles design
question here.

Aevum Foundry AI aims to meet WCAG 2.2 Level AA across this website. Accessibility is not a compliance bolt-on for us — it is a design question we ask first, because the people our tools are built for include SEND pupils and the staff who support them. We keep what we have done separate from what we have only promised, and we say plainly when something is still in progress.

Where a standard is not yet met, this statement says so, rather than claiming conformance we cannot evidence.

The following features are in place across the site today:

• —A skip-to-main-content link is the first focusable element on every page, letting keyboard and screen-reader users bypass the navigation.
• —Pages use a single <main> landmark and a logical heading order, so screen readers can navigate by structure.
• —All interactive elements — links, buttons, forms, the navigation toggle and the theme switch — are reachable and operable by keyboard, with a visible focus indicator.
• —Form fields carry visible labels and inline error messages, so a mistake is explained in words, not by colour alone.
• —Site text reflows and can be enlarged to 200% in the browser without content being cut off or overlapping.
• —A light and dark theme is available, remembering your choice, and following your system preference the first time you visit.
• —Content images that carry meaning have descriptive alt text; decorative images are marked so assistive technology skips them.
• —Respects your operating-system reduced-motion setting, and keeps transitions short and never auto-playing.

We test in two ways. Automated checks catch structural and contrast problems as we build. We then walk through key journeys — the homepage, the Trust Hub, a blog post and the contact form — by keyboard and with a screen reader, in both light and dark themes, at desktop, tablet and mobile widths.

An independent third-party audit is not yet complete. We list this under known barriers below rather than implying a verdict we do not have.

These are the accessibility problems we know about. If you find one we have missed, please tell us — the route is in the next section.

• —We have not yet had an independent third-party accessibility audit. The findings on this page are our own, from manual and automated testing, and we treat that honestly as a limitation rather than a verdict.
• —Some longer paragraphs can leave a single word stranded on its own line. We are correcting these as we find them.
• —The AI-generated imagery used on some pages is purely decorative; we are reviewing its alt text and contrast as part of normal content work.
• —Automated, real-time captions are not provided on this site because it does not host video. When we publish video elsewhere, we commit to human-checked captions.

If part of this site is hard or impossible for you to use, we want to know. Email us at accessibility@aevumfoundry.ai and tell us:

• the page address (URL) where you hit the problem,
• what you were trying to do,
• what happened instead, and
• the browser and, if you use one, the assistive technology you were using.

We read every message. We will reply to confirm we have your report, tell you what we plan to do, and follow up when it is fixed. We do not set a fixed response time, because this is a small company and we will not promise a deadline we cannot keep — but you will hear back from a person, not an auto-reply.

The site is built to work in the current and previous major versions of Chrome, Firefox, Safari and Edge, on desktop and mobile. It is designed to be usable with common screen readers (NVDA, JAWS and VoiceOver) and with keyboard-only navigation.

Older browsers or uncommon assistive technology may not render every visual detail, but the content should remain readable and operable. If it does not, please report it using the route above.

This statement covers the Aevum Foundry AI public website at www.aevumfoundry.ai. It does not cover the in-school applications themselves, which are assessed separately and have their own accessibility work as part of product development.

It was last reviewed on 23 September 2026. We review it when accessibility work completes, or at least once a year, and we keep a public record of what changed and when in the changelog.

Questions about anything on this page: hello@aevumfoundry.ai. Related commitments are collected on the Trust Hub.