RRizzume

Accessibility Statement

Version 1.0 · Last updated 2026-04-23 · Last tested 2026-04-23

This statement applies to the Rizzume web application at rizzume.co.uk, operated by Augustova Limited.

We want Rizzume to work for everybody: people who use screen readers, people who navigate by keyboard only, people with motor, cognitive, or visual differences, and people using phones in bright sunlight or with gloves on. Accessibility isn't a feature we bolt on; it's a constraint we design to.

What we aim for

We aim to meet the Web Content Accessibility Guidelines 2.1 Level AA. This is the standard required by the UK Public Sector Bodies Accessibility Regulations 2018 (which does not apply to us directly, but we use it as our benchmark) and the EU Accessibility Act 2025 (which does apply to digital services marketed to EU consumers).

Current conformance

The website is largely compliant with WCAG 2.1 AA, with the exceptions listed below. "Largely compliant" means we've addressed the substantive criteria but some edge-case issues remain, documented and being actively worked on.

What works well

  • Every page can be completed using only a keyboard, no mouse required.
  • Focus is always visible; order is logical.
  • The AI interview coach announces new messages to screen readers as they arrive.
  • Errors and toasts are announced via live regions.
  • Every icon-only button has a text label for screen readers.
  • Colour is never the sole way information is conveyed.
  • The design respects the system "reduce motion" setting.
  • Tap targets meet the 44×44 pixel minimum on touch devices.
  • We support 200% zoom without layout breaking.

Known limitations

The following are currently non-conformant and under active remediation:

  • CV template PDFs rendered by @react-pdf/renderer do not currently expose a fully tagged PDF structure. Screen readers can read a CV's text but not semantic headings. We're tracking @react-pdf/renderer#1234 for tagged-PDF support.
  • The interview radar chart on the session summary page is decorative. The same scores are also presented as a plain text list immediately below.
  • Admin portal keyboard shortcuts (g d, g u, etc.) use single letters and aren't surfaced to screen-reader users until they open the ⌘K palette.

None of these prevent core tasks from being completed; they reduce fluency for some users.

How we test

  • Automated: axe DevTools, Pa11y, and Lighthouse accessibility audits run on every pull request as a CI check.
  • Manual keyboard pass on every new feature before release.
  • Manual VoiceOver pass on critical flows (signup, onboarding, CV build, interview, ATS scan, settings/data) every sprint.
  • Usability testing with real users including at least one assistive-tech user per round.

If something's broken for you

If you find a part of Rizzume you can't use, we want to know. Email accessibility@rizzume.co.uk (or use privacy@rizzume.co.uk if that's easier). Please include:

  • What you were trying to do
  • What happened
  • Which browser and assistive technology you use (if any)

We aim to reply within one working day. If the issue is a WCAG 2.1 AA barrier we can fix, we aim to release a fix within 10 working days. If the fix is bigger, we'll tell you our plan and timeline.

Enforcement

If you're not happy with our response, you can contact the Information Commissioner's Office (which does not regulate accessibility directly but does take complaints seriously under the Equality Act 2010 framework where appropriate), or the Equality and Human Rights Commission via their advisory service.

Preparation of this statement

This statement was prepared on 23 April 2026. It was last reviewed by the Augustova engineering team against WCAG 2.1 AA on the same date using axe DevTools, manual keyboard navigation, and a VoiceOver walkthrough of the signup-to-first-CV flow.

It is reviewed at least every 12 months, or sooner if a significant change is made to the product.