Cookies & analytics

We only use essential cookies to run ReviseBase. Anonymous usage analytics are off unless you accept — see our Cookie Policy.

revisebase

Accessibility Statement

Version 1.0 · effective 18 September 2026 · last reviewed 18 September 2026 · next review 18 March 2027

In short

  • We aim for WCAG 2.1 AA in spirit: responsive layouts, keyboard navigation, visible focus, labelled forms and high-contrast themes.
  • We have not had a formal accessibility audit yet — we do not claim a conformance level, and we fix issues as users report them.
  • Known limits: we cannot control the accessibility of files you upload, and some interactive study modes may be harder with assistive tech.
  • If something is hard to use, tell us via the contact page and we will help and fix what we can.

Read the full policy below.

ReviseBase wants to be usable by every learner, including those using assistive technology.

1. Our commitment

We aim to meet the spirit of the WCAG 2.1 AA guidelines across the student app and public pages. Our conformance against the full standard has not yet been formally audited — UNVERIFIED — HUMAN CONFIRMATION REQUIRED: no formal WCAG audit or third-party certification has been carried out, so we do not claim a conformance level. If you need a specific adjustment, contact us and we will help directly.

2. What we do now

  • Responsive design: the app works on phones, tablets and desktops, including with system font sizes.
  • Keyboard support: our interface components (dialogs, tabs, menus, forms) are built on accessible foundations that support keyboard navigation, visible focus states and screen-reader roles.
  • Colour and contrast: we use a high-contrast dark theme by default and a light theme option.
  • Labels and structure: forms are labelled, headings follow a structure, and interactive elements carry accessible names.
  • Reduced motion: core reading flows avoid large autoplaying motion; animations are short transitions.

3. Known limitations

  • AI-generated study content is produced as plain text from your materials — its quality, structure and alt-text are not controlled by us.
  • Uploaded documents (e.g. scanned PDFs) may themselves be inaccessible; we cannot fix the accessibility of files users upload.
  • Some complex interactive areas (drag-and-drop study modes, data charts) may be harder to use with some assistive technologies.

4. Tell us about a barrier

If anything on ReviseBase is hard or impossible for you to use, tell us via the contact page. Describe the page and what happened — we will respond, help you find a workaround, and fix the issue where we can. Serious complaints can also be raised with your institution's support services if they introduced you to the platform.

5. Review

This statement was last reviewed on the date shown at the top; we review it alongside each major app update.