Legal

Accessibility

Last reviewed: August 26, 2026

We want this site to be usable by everyone, including people who browse with a screen reader, navigate by keyboard alone, use magnification, or need higher contrast. This page says plainly what we have checked, what we have not checked yet, and how to tell us when we have got something wrong.

The standard we aim at

We target the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. That is the benchmark used under the Americans with Disabilities Act and the one the Department of Justice adopted for public entities in 2024.

What we have checked on this site

Verified directly, not assumed:

Colour contrast. Measured against real usage. Body text sits at 16.4:1 against its background, secondary text at 6.0:1, and the accent colours on the dark hero at 6.9:1 and above. AA asks for 4.5:1 on body text and 3:1 on interface borders.
Keyboard access. Every page opens with a "Skip to content" link, and focused elements draw a visible outline rather than relying on the browser default being present.
Form labels. Every field on the contact form has a real, programmatically associated label, and each field declares its purpose so a browser or assistive tool can fill it in for you.
Errors and confirmations. When a form fails or succeeds, the message is announced to screen readers rather than only appearing on screen.
Structure. Each page has one main heading and a heading order that does not skip levels, so a screen reader's outline matches the visible one.
Images. Product screenshots carry descriptive alternative text that says what the screen shows. Purely decorative images are hidden from assistive technology rather than announced as noise.
Language. The page language is declared, so screen readers use the right pronunciation.

What we have not done yet

We have not yet completed a full manual audit with assistive technology. Automated checking catches somewhere around a third of real accessibility problems; the rest need a person using a screen reader and a keyboard. Until we have done that, we are not claiming full WCAG 2.1 AA conformance, and we would rather say so than post a badge we cannot back.

We also do not use an accessibility overlay widget. Overlays do not fix the underlying page, and people who rely on assistive technology frequently report that they interfere with the tools they already use.

Tell us about a barrier

If any part of this site stops you doing something, please email info@aegisregistrar.com with the page address and what happened. You do not need to know the technical cause, and you do not need to phrase it in any particular way.

We aim to reply within five business days, and to tell you either how we have fixed it or when we will. If something blocks you from reaching us, say so by any route that does work and we will find another way.

This site and our product

This statement covers the marketing site at aegisregistrar.com. The Aegis Registrar application used by schools and their students is a separate product with its own accessibility work in progress. If you are a student or a school staff member using the application and you hit a barrier, contact us at the address above and tell us which one you were using.