Accessibility Statement

Last updated: 2 October 2026

1. Our commitment

Corvo aims to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the standard most commonly referenced in UK and EU accessibility law. This is an ongoing goal we're actively working towards, not a certification we're claiming to have already achieved.

2. Current conformance status

Partially conformant. Partially conformant means some parts of the site don't yet fully meet the standard. We haven't commissioned an independent WCAG audit — this statement is based on our own internal review, not third-party testing with real assistive technology users.

3. What we've built in

• Semantic HTML throughout, so headings, lists, tables and form controls are structured for screen readers, not just visually
• Keyboard-operable buttons, links, menus, and forms across the dashboard and onboarding flow
• A dark and light theme, so you can use whichever has better contrast for you
• Respect for your operating system's "reduce motion" setting, for anyone sensitive to animation
• Text that resizes with your browser's zoom and font-size settings, rather than being fixed to a pixel size
• Visible focus states on interactive elements, so keyboard navigation shows you where you are

4. Known limitations

We're aware these areas need more work, and we're actively improving them:

• Some interactive dashboard components (flashcard review, the folder/drag-and-drop interface) haven't been tested with screen readers and may not announce state changes correctly
• Payment forms are built and hosted by Stripe inside our pages — their accessibility depends on Stripe's own implementation, which is outside our direct control
• Some data visualisations (progress charts, readiness scores) convey information primarily through colour and position, without a full text-equivalent alternative yet
• We haven't tested extensively across every combination of screen reader and browser — our testing so far has been informal, not systematic

5. Third-party content

Lecture notes, slides and files are generated from material you or your university provides. We can't guarantee the accessibility of content inside your original Canvas or Moodle files, or of embedded images and diagrams carried over from your lecture slides.

6. Reporting an accessibility problem

If you use assistive technology and something on Corvo doesn't work the way it should, we want to know — and we'll prioritise genuine accessibility blockers over general feature requests. Email support@itscorvo.com with:

• The page or feature you were trying to use
• What assistive technology and browser you were using (e.g. VoiceOver + Safari, NVDA + Chrome)
• What happened, and what you expected to happen instead

We aim to acknowledge accessibility reports within 2 working days and will let you know what we plan to do about it.

7. Enforcement

If you're not happy with our response, UK users can contact the Equality Advisory and Support Service (EASS). Corvo is a privately-run study tool rather than a public sector body, so the Public Sector Bodies Accessibility Regulations don't formally apply to us — we're choosing to hold ourselves to the same WCAG 2.1 AA standard regardless.

8. Technical specification

Corvo relies on HTML, CSS and JavaScript, and is built to work with up-to-date versions of major browsers (Safari, Chrome, Firefox, Edge) and their built-in zoom and reader modes. We don't require any particular assistive technology, but haven't verified compatibility with every combination that exists.

Questions? Email support@itscorvo.com  ·  Privacy Policy  ·  Terms of Service