Accessibility statement.

01What this statement covers

This statement is about presentor.io:

• the website (the home page, Features, Pricing, Security, the legal pages and this statement);
• signing up and logging in (/start, /aanmelden and /inloggen);
• the app: the overview, the editor, Help and Admin;
• presentations that someone shares with a link (the viewing page), and the print page that makes a PDF or handout.

Not covered are the content of presentations themselves (the maker creates that, see What the maker of a presentation does), the payment pages of our payment provider and websites of others that we link to. What we did not test is listed under How we tested.

02Status

Presentor partly conforms to WCAG 2.2 level AA. That is the international W3C guideline for accessible websites and apps. WCAG 2.2 builds on 2.1, which the European standard EN 301 549 refers to.

Partly, because we know of problems (see Known problems) and because part of Presentor was not tested. This is our own assessment. There has been no external audit.

03How we tested

On 25 October 2026 we tested presentor.io ourselves, automatically and by hand, in Chromium (the browser under Chrome and Edge). We did not test Safari or Firefox.

• Automatically, with axe-core 4.14 and the rules for WCAG 2.0, 2.1 and 2.2 levels A and AA, in light and dark and at 1280 and 390 pixels wide: the home page, Pricing, Features, Security, Privacy and this statement; signing up, /start and logging in; a shared presentation through a link, with the slide overview and the keyboard shortcuts open; the print page; the overview, Help and Admin in the app; and the editor, also with menus open, the Share window, the settings and the tour. We also ran the editor on every slide of two presentations with 54 slides between them (in light), and the viewing page on 12 slides with many different elements.
• By hand, with the keyboard (Tab, arrow keys, space, Escape, Home and End) through the site, the editor and a shared presentation: is everything reachable and is the focus visible everywhere. With Reduce motion on, on the site, in the app and in a shared presentation, in light and dark, on a screen 320 pixels wide (the page reflows without scrolling sideways, zooming is not blocked) and with text over a gradient or image, whose contrast we measured on the page because the automatic check cannot judge it.

What we did not do: an external audit, and testing with people who use a screen reader, voice control or another assistive technology. So we did not test with NVDA, JAWS, VoiceOver or TalkBack. Also not tested: text spacing (WCAG 1.4.12), the iOS and Android app, Live with the room, presenting on a TV or projector, trade show mode, spaces, the speaker window, the phone as a remote and what Presentor exports (PDF, video, PowerPoint and GIF).

04What is already there

Only what we checked:

• Keyboard: you control a shared presentation with the arrow keys, space, Home and End. O opens the slide overview, ? the keyboard shortcuts and U the captions. The overview and the shortcuts keep the focus inside the window and close with Escape. In the editor, Tab reaches the top bar, the slides, the canvas and the panel, and a tour keeps the focus to itself.
• Visible focus: buttons, links and fields show a focus ring, in light and dark. A text field on the editor canvas gets an outline with ink on both sides, so it also shows on a white slide.
• Skip to content: on the site and in the app the first Tab is a link that jumps to the content.
• Screen readers: buttons and fields have a name, and every page has its own title and a main area. When a viewer goes to another slide, the slide number and title are announced. The maker can set the language of the slides: it becomes a language attribute on the slide, so a screen reader picks the right pronunciation.
• Images: an image without alt text gets an empty alt, so a screen reader skips it. In the editor you enter alt text with the image, and with Pro AI can suggest a description, which the maker checks.
• Captions: the maker can share the speaker notes as captions. Viewers turn them on with the captions button or the U key.
• Reduce motion: when that is on in your operating system, repeating animations stand still on the site, in the app and in a shared presentation. The dot next to Live on the home page pulses three times and then stands still. The recordings on the home page and under Features then do not start by themselves. Even without Reduce motion they have a pause button and no sound. Per presentation the maker can turn on Calm: the build-up then shows in its end state straight away and every transition is a short cross-fade, for all viewers.
• Phone: pages reflow down to 320 pixels wide, pinch zoom works, and a shared presentation on an upright phone shows the slide with its text below it at a readable size.
• Buttons and links are large enough to tap or have enough space around them (WCAG 2.5.8, measured with axe).
• You can log in without a password or puzzle: with a passkey or with a link or code by email.

05Known problems

This is what we found and have not yet fixed:

• Shared presentation, slide overview (O key): the name of a tile is "Slide 3: title", while the tile also shows the text of the slide as a thumbnail. The automatic check reports that as a difference between what you see and what voice control knows (WCAG 2.5.3). We see the thumbnail as a picture, but we did not test it with voice control.
• Moving backgrounds: a presentation with a moving gradient or glow behind the text keeps moving as long as you watch. Reduce motion in your operating system and Calm from the maker stop it; there is no button on the viewing page itself yet (WCAG 2.2.2).
• Recordings on the home page and under Features: they have no sound and no full text version. There is a short description for screen readers, a pause button and a list of steps below them (WCAG 1.2.1).
• Editor: in a table every cell is its own tab stop. With a large table it takes many Tab presses to reach the panel using only the keyboard. It can be done, but it is awkward.

If you report a problem that is not listed here, we will add it. We update this statement when something changes.

06What the maker of a presentation does

Presentor makes it possible to present accessibly, but the content comes from the maker. Please take care of this yourself:

• Enter alt text for every image that tells something, and leave the alt text empty for an image that only decorates.
• Choose colours with enough contrast in your own house style: at least 4.5 to 1 for normal text and 3 to 1 for large text. Check in the editor points out too little contrast, too much text, empty boxes and blurry images.
• Write speaker notes and share them as captions, so that people who cannot hear can read along.
• Turn on Calm if your audience is bothered by motion, and leave out a moving background when the slide stays up for a long time.
• Set the language of the slides if the presentation is not in the language of the viewer. Then a screen reader picks the right pronunciation.
• Give every slide a clear title and do not use colour alone to show something.

07Contact and response

Does something not work with your assistive technology, or can you not do something? Email hallo@presentor.io with the page, what you use (browser and assistive technology) and what went wrong. We reply within five working days and tell you what we will do about it.

How we handle your data is described in the privacy statement.