Accessibility
Last reviewed: 16 September 2026.
RepairMyVideo is a one-purpose service: you upload a video file that will not play, and we try to rebuild it. We want that to work for everyone, including people using a screen reader, a keyboard without a mouse, magnification, or a browser set to reduce motion.
What we aim for
We are working towards WCAG 2.2 Level AA, the standard referenced by the European Accessibility Act via EN 301 549 and by the accessibility laws of the countries we serve.
Where we actually stand
This site partially conforms to WCAG 2.2 Level AA. “Partially conforms” means most of the standard is met and some of it is not yet. We would rather tell you which parts, than claim a level we have not reached.
What works today, and has been tested
- The whole upload flow can be operated with the keyboard alone. Tab reaches the “Choose your video file” button; Enter or Space opens the file picker.
- Every interactive element shows a visible focus outline.
- Every page starts with a “Skip to content” link and uses landmark regions, so you can jump straight past the header.
- Upload progress, upload failures, and the job status page announce themselves to a screen reader as they change — including the name and size of the file you picked, and the two warning notices about oversized files and stalled connections.
- Every form field has a real label, not just placeholder text that vanishes when you start typing.
- A mistyped or expired link returns a real page that says what happened, in your browser’s language setting, rather than a line of raw data.
- Links inside paragraphs are underlined, not signalled by colour alone, and the upload area’s outline, the separator dots and the status badges all meet the contrast minimums.
- The page reflows down to a 320-pixel-wide window with no sideways scrolling, so browser zoom up to 400% works.
- If your system asks for reduced motion, we remove animations and transitions.
- There are no images without text alternatives, and no time limits anywhere on the site.
What does not work yet, and what we are doing about it
- Everything above was checked with automated tooling and a keyboard, not with a real screen reader. We drive the pages through axe-core and walk them with the Tab key on every release; we have not yet sat down with NVDA or VoiceOver end to end. Until we have, we will not claim full conformance, and if something reads wrongly for you we want to hear about it. Scheduled.
- The recovered-video preview has no captions or audio description. This one is a deliberate limitation, not a backlog item: the preview is your own footage, recovered from your own file. Our recovery is automated and we do not review videos in order to describe them, so we have no transcript of it and would not write one. The preview is never the only way to get your result — the download link sits above it, and every finding the system made about your file is written out in text on the same page.
Tell us if something blocks you
Email [email protected]. A human reads every message. Please say what page you were on, what you were trying to do, and what you were using (browser, screen reader, phone or desktop) — that is usually enough for us to reproduce it.
We answer accessibility reports within 5 working days. If something is blocking you from recovering a file right now, say so in the subject line and we will handle the recovery for you by email while we fix the page.
How we check
We test with automated tooling (axe-core) on every public page at desktop and phone widths, plus keyboard-only walkthroughs of the upload and status pages. We re-run this every three months and update the date at the top of this page. This statement was first published on 16 September 2026 and is based on a self-assessment, not a third-party audit.