Home›Accessibility
Accessibility statement.
Potentially is used by students and staff with a wide range of needs. This sets out the standard we hold ourselves to, what we have tested, and where we fall short.
The standard we work to.
Potentially is built to the W3C Web Content Accessibility Guidelines, WCAG 2.2, at level AA, and we assess it against those criteria ourselves. The platform is a responsive, mobile-first application that renders correctly on desktop, tablet and mobile, and is operable by keyboard and screen reader throughout.
How we check. Our conformance is self-assessed, two ways: automated scanning on every release, and a manual checklist review in staging against each WCAG 2.2 AA criterion. We have not commissioned an external audit. The conformance report below sets out what we assessed and what we found.
What we work on.
- Navigation that works with a screen reader and with a keyboard alone
- Clear visual cues and sufficient colour contrast
- Accessible authentication, and alternative controls where a standard control would exclude someone
We run regular reviews and user feedback sessions, and they set what we fix next.
What we have tested on.
Fully tested
- Windows 11 and 10 — current Edge, Chrome and Firefox
- macOS, current and previous release — current Safari, Chrome and Firefox
- iOS, current and previous release — Safari
- Android, current and previous release — Chrome
- NVDA and JAWS screen readers on Windows
Spot-checked only
- VoiceOver on macOS and iOS
- TalkBack on Android
- Browser zoom to 400% and Windows high-contrast themes
- Older operating system releases, when someone reports a problem on one
Where we fall short.
Some pages and sections are not fully accessible, or are in the process of becoming so. The most common cause is content delivered from an external source — tools such as Genially, Padlet or Panopto — where the accessibility of the embedded content is not ours to control.
The platform is also actively developed, and new features can introduce new problems. We would rather tell you that than claim a finished state we have not reached.
The conformance report.
We maintain a conformance report setting out what we have assessed and what we found. It is the document to send to a procurement or accessibility team.
Accessibility conformance report, 2026, self-assessed (PDF, opens in a new tab)
Tell us what we have missed.
If something on the platform or this site is not working for you, we want to know. Email hello@potential.ly and tell us what you were trying to do and what got in the way.
Making your own setup easier.
AbilityNet publishes guidance on adjusting your computer to suit you. We link to it because people have found it useful, not because we can vouch for any particular article.