Legal
Accessibility
What Lectern does for people with disabilities, both those who make videos with it and those who watch them, where it falls short, and how to tell us.
Effective October 23, 2026
We want everyone to be able to make videos with Lectern, and everyone to be able to watch them. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We haven't had the apps audited against it yet, so we don't claim they conform. This page says what's done, what isn't, and how to tell us about a problem.
For the people who watch
- Captions. The desktop and phone apps make captions from your recording on your device, in your own words when you read from a script. You can correct them word by word, and they go out with the video: built into the file, as a separate caption file, or with a share link.
- Transcripts. A shared video's page shows its captions on the video and as a transcript beneath it.
- A check before you publish. The app warns when a project has sound but no captions, step by step, and shows you where.
For the people who make videos
- Keyboard. The app can be used with a keyboard: menus, dialogs and settings, the prompter, and the cut tools (X to cut, the arrow keys, Home and End). Things you drag with a mouse, such as a picture's place on the screen, also have keys or number fields. A project's steps lay themselves out, so nothing needs dragging into place: they're one stop for Tab, the arrow keys go from step to step, and a list shows them in the order they play, with buttons to move each one earlier or later.
- Screen readers. Buttons, fields and dialogs have names that screen readers read out, and messages that appear (an error, a recording starting) are announced. Each of a project's steps says where it goes and what comes before it.
- Seeing it. Text and controls are held to WCAG AA contrast in both the light and the dark theme. The prompter's text size and speed are yours to set, and its reading strip moves without sliding when your system asks for reduced motion.
- Tested on every change. Automated accessibility checks (axe, against WCAG 2.2 A and AA) run over the app's main screens and dialogs, in both themes, as part of its tests.
Where it falls short
- Automated checks find only some problems. We haven't yet tested the whole app by hand with screen readers (VoiceOver, NVDA, JAWS) or with people who use them every day.
- Editing on the timeline is easiest with a mouse or touch. The keyboard ways to do the same are there, but slower. Joining one step to a step other than the next is done in the step's settings (Goes next), not on the diagram itself.
- Captions come from speech recognition and can have mistakes, especially in names and technical words. Read them over before you publish.
- The version in the browser makes captions and transcripts on a computer, not in a phone's browser, and keeps captions beside a video rather than in the file.
- Audio description (narration of what's on screen, for viewers who can't see it) isn't built yet. It's planned.
- This website is built to the same target, but isn't covered by the automated checks yet.
Tell us about a problem
If something in Lectern or on this website is hard or impossible to use with your disability or your assistive technology, write to hello@lecternvideo.com. Say what you were trying to do, where, and what you use (a screen reader, say, and its version, and which app or browser). A person reads every message, and we treat accessibility problems as bugs to fix, not requests.
For schools and procurement
An Accessibility Conformance Report (ACR), on the VPAT 2.5 template, is being written. Ask us for its status. The IT page covers the rest of what an institution's review asks: the network, data and permissions.
Lectern is made by Lectern Video LLC, PO Box 4001, Bartonville, IL 61607. Questions about this page: hello@lecternvideo.com.