Back to ace

legal

Accessibility

Every student should be able to use ace. This page says what we have done, what is honestly not right yet, and how to tell us when we have got it wrong.

effective 2 august 2026 · last updated 2 august 2026

1. What we are aiming for

We are working towards WCAG 2.2 Level AA. We are not claiming to have got there. A statement that claims full conformance without an audit is worth nothing, so this page describes where we actually are.

ace is a small team building in the open. When a barrier is reported to us, fixing it goes to the top of the list rather than into a backlog.

2. What we have done

3. Known problems

These are real and we would rather say so than let you find out yourself.

4. If something is unusable

If any part of ace stops you getting an answer you need, email us and we will answer your question directly, by email, while we fix the underlying problem. You should not have to wait for a release to get help.

Write to access@acecollege.app.

5. Telling us about a problem

Email access@acecollege.app. It helps if you can tell us:

We aim to acknowledge within 5 working days and to tell you what we are doing about it within 15 working days. If a fix will take longer, we will say so and offer a way around it in the meantime.

6. Scope and limits

This statement covers acecollege.app and the ace application at app.acecollege.app.

It does not cover university systems, third-party sites we link to, or documents published by an institution. Where ace points you to a university office or form, that page's accessibility is that institution's responsibility, not ours.

ace is independent and is not affiliated with, endorsed by, or sponsored by any university.