Accessibility statement

LectaMe is used in education and training. There you find students, course participants and teachers with diverse needs — some work with a screen reader, others only with the keyboard or with a magnified display. We believe they should all be able to take part.

Accessibility is an ongoing process. This statement is honest: we describe what already works, what does not yet work and what we are going to improve.

This statement applies to:

• The public website of LectaMe (https://lectame.com).
• The logged-in user environment (dashboard, settings).
• The participant experience during live sessions.
• The presentation editor — with the known limitations mentioned below.

We apply WCAG 2.2 level AA as a development goal. Concretely this means: we evaluate new features against WCAG 2.2 AA and resolve identified issues step by step. LectaMe has not yet been formally tested for full WCAG conformance.

We pay extra attention to the WCAG 2.2 additions that are relevant in a presentation environment:

• Focus Not Obscured — the focus must never be hidden behind sticky banners or modals.
• Dragging Movements — where possible we offer an alternative to dragging.
• Target Size — interactive elements get a sufficient click area.
• Consistent Help — help is always in predictable places.
• Redundant Entry — previously entered data is not requested again unnecessarily.
• Accessible Authentication — logging in must not depend solely on cognitive tests.

• The public part of the website uses semantic HTML with a clear heading structure, landmarks and language setting (Dutch).
• Our cookie banner is fully keyboard-operable, closes with Escape and uses role="dialog" with focus trapping. The "Accept all" and "Only necessary" buttons are visually equivalent.
• Modals and dialog windows return focus to the original opening element after closing.
• Forms in registration and login have linked labels and show error messages that are read aloud by screen readers.
• The visible focus outline is enabled on interactive elements.
• Color contrast in the default "lectame" palettes is tuned to AA targets for text and interactive elements.

The following points are not yet at WCAG 2.2 AA level. We are working on them, but want to mention them honestly here:

When using AI to generate presentations, the teacher remains ultimately responsible for accessibility. We recommend checking the following for each generated slide:

• Does every meaningful image have alt text?
• Is decorative imagery marked as decorative?
• Is the contrast between text and background sufficient?
• Is the reading order logical and not purely visual?
• Does the amount of text per slide suit the target group and language level?
• Are interactive elements (quiz, poll, open question) clear and do they support keyboard operation?

• Numeric input for the position and size of canvas elements, so dragging is not the only option.
• List view of elements on a slide with keyboard operation for ordering and properties.
• Full prefers-reduced-motion support in animations.
• A standard skip link to the main content on all public pages.
• An accessibility checklist that teachers can call up for a slide or presentation.
• An external accessibility audit by an independent party.

Run into an accessibility problem? Let us know. We greatly appreciate reports and use them to improve LectaMe.

Email: toegankelijkheid@lectame.com

Preferably mention: which device and browser you use, on which page you got stuck, and what you were trying to do. We aim to respond substantively within five working days.

Made a report and find our response insufficient? You can always follow up via info@lectame.com. If you believe there is structural exclusion, you can also report this to the Netherlands Institute for Human Rights.

This statement is reviewed at least once a year, or sooner in the event of major product changes. The date and version are shown at the bottom of this page. For general questions you can visit the privacy and terms pages.