1. Our aim
We want every student, instructor and school leader to be able to use C3NTR, whatever assistive technology they rely on. Our target is WCAG 2.2 level AA for the C3NTR mobile app (iOS and Android) and for this website. We are not there yet on every point, and this page says plainly where we are. It is kept in step with our internal accessibility audit and will be updated as work lands.
2. Where we are today
The mobile app has had a full static audit of its code and one on-device VoiceOver walkthrough (build 84, 20 May 2026). Every issue found in that walkthrough has been fixed in the code, and those fixes are waiting for a second on-device check on the next TestFlight build. This website has not yet had a formal accessibility audit.
3. What we have done in the app
- VoiceOver labels. Every user-facing reading and browsing surface exposes labelled controls to VoiceOver and TalkBack: the navigation bar, search, the video and audio players, the Me drawer, Home, content browsing, content reading and the media picker. Some admin and editor screens still have unlabelled controls (see section 4).
- Reduce Motion. Every animation we wrote respects the system Reduce Motion setting, using a shared helper that jumps to the end state instead of animating. This still needs a final on-device check.
- Tap targets. Our automated tests check that controls in the tested widgets meet the 44 pt (iOS) and 48 dp (Android) minimum. Three controls that failed were fixed: the audio play button, the plan card button, and the discipline filter chips.
- Contrast. When a school sets its brand colour, the app picks the button text colour by measuring the WCAG contrast ratio, rather than guessing. Our tests assert AA contrast on the tested widgets, in both light and dark mode, and three text colours that failed were corrected. A check across real school brand colours on a device is still to do.
- Captions and transcripts. The video player can show a captions track and has a captions toggle that announces its state. Audio items can carry a transcript, shown under a "Show transcript" control. Schools cannot yet attach a captions file from the web portal, so video captions depend on that work.
- Differentiate without colour. The favourite heart changes shape (outline to filled) and its spoken label changes, so its state does not rely on colour alone. The unread badge shows a number.
- Image descriptions. Alt text written by a school on an inline image is read by the screen reader, and images with no alt text are skipped as decorative.
- Form fields. Text fields use platform labels, which screen readers announce by default.
- Light and dark. Every tested widget is checked in both light and dark themes.
4. What is not done yet
We would rather tell you than let you find out. The following are known gaps.
- Larger Text (Dynamic Type). Not started. Around 150 text sizes in the app are fixed rather than scaling with the system text size. This is planned as its own piece of work after launch.
- Audio descriptions. Not started. The data model has a field for an audio description track, but the player cannot play one yet.
- VoiceOver re-check on a device. The seven fixes from the May walkthrough (verification code field, tab order, reading-progress bars, Today announcement cards, the Home "more" menu, the navigation bar hiding on scroll, and the audio transcript control) are in the code but have not yet been re-tested on a device. One known gap remains: the items inside the Home "more" menu come from a third-party component that has no screen-reader support of its own.
- Captions upload. The web portal does not yet let a school attach a captions file to a video.
- Admin and editor screens. The setup wizard, media editor, editor toolbar and term editor still contain controls without screen-reader labels.
- Some cover images. A number of listing and cover images do not yet carry a description or a decorative marker.
- Compact controls. Some controls, mostly on admin screens, use a compact layout that may fall below the minimum tap size. Each is being reviewed.
- Voice Control and dark mode have not had a dedicated on-device walkthrough.
- This website has not had a formal audit.
5. How we test
The app has an automated accessibility test suite: a suite covering the shared widgets, each run in light and dark mode, checking four things: that every tap target has a label, that targets meet the iOS 44 pt minimum, that they meet the Android 48 dp minimum, and that text contrast meets WCAG AA. The suite runs in continuous integration on every change and is being made a required check before code can be merged. Alongside it we do manual walkthroughs on a physical iPhone with VoiceOver and Reduce Motion turned on, and we keep a dated record of each one.
6. Report a barrier
If something in the app or on this website is hard or impossible for you to use, please tell us. Email info@c3ntr.app with the subject "Accessibility". We respond within 5 working days.
It helps if you can tell us:
- what you were trying to do
- which device and operating system version you were using
- which assistive technology, if any, you were using
- what happened, and what you expected
If you cannot use email, ask your school leader to contact us on your behalf.
7. Contact
C3NTR is developed and operated by andBeyond.digital Ltd (registered as ANDBEYOND.DIGITAL LTD), company no. 17260951, 71–75 Shelton Street, Covent Garden, London WC2H 9JQ. Previous versions of this page are available on request.