Lectora Development Services for Training Teams
For L&D, training and compliance teams that need Lectora courses built, upgraded or translated by an outside team.
IKHYA builds new courses in Lectora and brings older Lectora Inspire titles up to date: responsive layouts, accessible design and clean LMS tracking. You get the finished packages and the editable Lectora source files, so your own team can make future changes.
Get a Free Quotation
Scoped proposal delivered within 48 hours
- Since 2010Delivering eLearning
- 500+Projects
- 40+Countries with clients
- 120+Specialists
Lectora development services in short
Lectora development services cover everything an outside team does in Lectora: instructional design, building new courses in Lectora Online or Lectora Desktop, upgrading legacy Lectora Inspire titles, accessible builds to WCAG 2.1 AA and Section 508, translation, and publishing SCORM or xAPI packages your LMS can track. IKHYA does all of this and hands over the editable source files.
Why training teams bring IKHYA in for Lectora
You keep the source files
Every project ends with the editable Lectora files as well as the published packages. Your team is never locked out of its own courses.
A plan for old Inspire titles
We look at each legacy title and recommend whether to upgrade it, rebuild it or retire it, so you do not pay to rebuild what only needs an upgrade.
Accessible from the first page
We build courses to WCAG 2.1 AA and Section 508, using Lectora's own accessibility settings and checker as a starting point, not the finish line.
One team for the whole course
Instructional design, Lectora development, media, translation into 40+ languages and LMS publishing come from one team of 120+ specialists, so nothing falls between vendors.
Not sure which option is right for you?
Send us a sample course or your content, and your free quote will include a recommended route and a timeline.
What we build in Lectora
IKHYA works in Lectora alongside Articulate Storyline 360, Articulate Rise 360, Adobe Captivate, iSpring Suite, dominKnow ONE and Elucidat. In Lectora we build:
- Compliance and policy courses with branching scenarios, question pools and pass marks that report to your LMS.
- Scenario-based training that uses Lectora variables and conditional actions to change what the learner sees based on their choices.
- Software simulations built from screen captures, form objects and questions (show-me, try-me and test-me practice).
- Responsive courses with layouts customized for desktop, tablet and phone in Responsive Course Design.
- Accessible courses built to WCAG 2.1 AA and Section 508.
- Gamified practice and knowledge checks inside the course.
- Microlearning modules for short refreshers and performance support.
- Upgraded and redesigned versions of older Lectora Inspire courses.
- Translated versions in 40+ languages.
Lectora is a WYSIWYG tool that needs no programming, but it also accepts custom HTML, JavaScript and CSS. That matters when a course needs a calculator, a custom interaction or tracking that a template cannot do. If you want the background first, our guide explains what Lectora is and how it compares with other eLearning authoring tools.
Lectora today: names and editions
ELB Learning (then called eLearning Brothers) acquired Lectora's maker Trivantis in April 2020 and now sells Lectora in two editions. Lectora Inspire and Lectora Publisher were combined into one desktop product starting with version 19 in 2020. On August 27, 2024, Lectora Desktop moved to a subscription model under that single name. The latest Lectora Desktop release at the time of writing is 22.4.0, dated August 11, 2026.
| Topic | Lectora Online | Lectora Desktop | Older Lectora Inspire / Publisher |
|---|---|---|---|
| Where it runs | In a browser on Mac or PC, nothing to install | Installed on Windows 8, 10 or 11 | Installed desktop software |
| Updates | Updated automatically | Subscription; download from ELB's Studio portal | Inspire and Publisher 18 support ended December 31, 2024 |
| Team work | Collaborative authoring: shared titles, assignments, roles | One desktop license per computer | Desktop authoring, no longer supported |
| Moving titles | Imports Lectora Online package files exported from Desktop | Exports a Lectora Online package file | Can export a Lectora Online package file |
Both current editions come in ELB Learning's Gold Suite on an annual subscription, together with ReviewLink (for stakeholder reviews), MicroBuilder and the Asset Library. ELB also notes that Lectora Online and Lectora Desktop handle custom JavaScript differently, and advises users to avoid moving a project back and forth between them.
Looking for Lectora service pack downloads? Since the 2024 move to a SaaS model, ELB says you access the current Lectora Desktop by logging in to The Studio by ELB Learning portal, and its knowledge base links to downloads and release notes for the older versions it still supports. Lectora Online updates automatically. If your team is stuck on an unsupported version, that is usually the moment to plan an upgrade.
Have older Lectora Inspire courses?
Many training teams own a library of titles built years ago in Lectora Inspire. The developer who built them has often moved on, and the courses only fit a desktop screen. ELB Learning ended support for Lectora Inspire and Publisher 17 on July 30, 2021, and for version 18 on December 31, 2024, and tells users to upgrade to the current Lectora Desktop.
Lectora 18 (October 2018) already published to HTML5 only because Flash was reaching its end of life. If some of your titles were published from older versions with Flash elements, those parts no longer play: Adobe ended Flash Player support on December 31, 2020.
Our Lectora development services for legacy libraries start with a look at every title, then one of three routes per course:
| Route | When it fits | What happens |
|---|---|---|
| Upgrade | The content is still right and the logic works | We open a copy of the title in current Lectora Desktop, fix what breaks, add responsive layouts, apply accessibility settings and republish |
| Rebuild | The logic is tangled, media is missing or the design is dated | We rebuild the course in Lectora (or another tool if it fits better), reusing the content that still holds |
| Retire or merge | Nobody takes the course, or it overlaps with another | We fold the useful content into another course, so you look after fewer titles |
ELB's current documentation does not list exactly which older versions open directly in today's Lectora Desktop. That is why we always test on a copy and keep your original files untouched.
Lectora saves each title as an .awt file. If you only have published packages and no source files, a rebuild is usually the only route.
Accessible Lectora courses
IKHYA builds accessible eLearning to WCAG 2.1 AA, the W3C standard, and Section 508, the US federal rule. The Revised 508 Standards apply the WCAG 2.0 Level AA success criteria to web and non-web electronic content, so a course built to WCAG 2.1 AA covers that baseline as well.
Lectora gives developers useful tools for this:
Web Accessibility Settings
In Title Options: once switched on, ALT text is always published for images and buttons, objects show a visual indicator when they receive focus, and custom radio buttons, checkboxes and video and audio skins are disabled.
The Accessibility Checker
ELB updated it to WCAG 2.2 in August 2024, and it flags objects that need attention.
Captions in several languages
Learners can switch them with a keyboard- and screen-reader-accessible selector (release 22.4.0, August 2026).
A tool cannot make a course accessible on its own. ELB itself says directions and cues should be added by the course developer, and that testing external programs for accessibility is up to the developer. That is why we design keyboard paths, alternatives to drag-and-drop and readable contrast from the storyboard stage, and test with a keyboard and screen readers before you review.
Translating Lectora courses
Lectora Desktop's translation tool exports a title's text to XLIFF or RTF, and Lectora Online exports it to HTML. Translators work on that file, and the text is imported back, with an option to increase text box size when a language runs longer. Lectora Desktop can also publish a separate version for each language.
IKHYA translates and localizes courses into 40+ languages, with human or AI voiceover. Translation is only part of it: dates, currencies, examples and images often need changing too.
We check every language version on screen before it goes live.
What Lectora is good and less good for
| Good for | Less good for |
|---|---|
| Fine control over course logic: variables, actions with conditions and an "On Variable Change" trigger | Teams that need a short learning curve: reviewers on Gartner Peer Insights and eLearning Industry mention it takes time to learn |
| Long, consistent courses: inheritance lets one header, menu or button appear on every page below it | Teams that want a modern-looking interface out of the box: some reviewers call the buttons and sliders dated |
| Accessibility settings, an Accessibility Checker and content that ELB says can meet Section 508 | Mac authoring outside a browser: Lectora Desktop runs on Windows only (Lectora Online runs on a Mac) |
| Wide publishing: HTML, SCORM 1.2 and 2004, AICC, xAPI, cmi5 and offline | Hiring in-house skills: Lectora has far fewer user reviews than the biggest tools (63 vs 698 for Articulate 360 on Software Advice), which in our view reflects a smaller pool of developers |
| Custom HTML, JavaScript and CSS when a template is not enough | 360-degree photo scenarios: ELB documents no 360-degree project type in Lectora (we build those in Adobe Captivate) |
| Free stakeholder reviews in ReviewLink: reviewers need no license | Moving one project back and forth between Lectora Online and Desktop |
When to choose another tool
Lectora is a strong choice when you already own it, when your courses need detailed logic, or when accessibility drives the project. It is not always the right tool. We work in seven authoring tools, so we can recommend the one that fits your content rather than the one we happen to use. These comparisons go deeper:
Lectora vs Articulate Storyline
Slide-based interactions and a large user community vs Lectora's logic and inheritance.
Compare →Articulate Rise vs Lectora
Fast, block-based responsive courses vs full control.
Compare →Lectora vs Adobe Captivate
Software simulations and 360-degree scenarios vs Lectora's structure.
Compare →iSpring vs Lectora
Building inside PowerPoint vs a standalone tool.
Compare →Lectora vs Elucidat
Browser-based authoring at scale vs desktop and online control.
Compare →What we deliver
| Deliverable | Details |
|---|---|
| Published course packages | SCORM 1.2, SCORM 2004, xAPI or HTML5, set up to track the way your LMS needs |
| Editable Lectora source files | The .awt titles and supporting files, so your team can make future revisions |
| Translated versions | Each language version, if your project includes translation |
Lectora itself can also publish cmi5, AICC and offline versions. Tell us what your LMS expects in the brief.
LMS platforms we have delivered courses to include Moodle, TalentLMS, Docebo and Cornerstone. IKHYA also sets up, configures and supports these platforms. Other LMSs we test courses in include Absorb, SAP SuccessFactors, Workday Learning, Canvas and Litmos.
Your Lectora seats or ours
Most clients choose one of two ways of working.
We build in our Lectora seats
We build in our Lectora seats and hand over the source files at the end: you do not need a license during the project, only later if your team wants to edit the files.
We build in your environment
We build in your Lectora Online account or with your Desktop setup when your organization requires the work to stay in its own environment, or when your team wants to watch progress in Lectora itself.
Either way, reviews run in ReviewLink, where your reviewers comment on each page and device view without a license, and the final .awt files and packages are yours.
A finished SCORM, xAPI or HTML5 package runs in your LMS or on the web without a Lectora license. You need a license only to edit the source files.
How it works
- 01
Brief and file review
You, then IKHYAYou send your content or legacy titles, your LMS details and your standards; we open copies of any existing files and list what works and what does not.
- 02
Recommendation and quote
IKHYAA recommended route per course (new build, upgrade, rebuild or retire), with a timeline.
- 03
Design and storyboard
IKHYA drafts, you reviewLearning objectives, structure, scenarios, assessments and accessibility needs, agreed before building.
- 04
Prototype
IKHYA drafts, you reviewOne working section in your branding, checked on desktop, tablet and phone.
- 05
Build
IKHYAThe full course in Lectora, with media, voiceover and question pools.
- 06
Reviews
YouUsually 2 review rounds in ReviewLink, with one consolidated list of changes per round.
- 07
Testing and delivery
IKHYAFunctional, accessibility and LMS tests, then the packages and source files.
For larger libraries, we deliver in batches, with the most urgent courses (for example annual compliance deadlines) first.
What drives the cost of Lectora development?
We quote every Lectora project individually, because the same "one hour of training" can be a light update or a complex build. The main cost drivers are:
- Course length and the number of courses.
- Interactivity: page-turning content vs branching scenarios, simulations and custom JavaScript.
- Starting point: a new build, an upgrade of a working Inspire title, or a rebuild of a broken one.
- Media: custom graphics, video, animation and voiceover.
- Accessibility requirements and the testing they need.
- Languages and the number of voiceover versions.
- Review rounds and how quickly feedback comes back.
- LMS testing across platforms or tracking standards.
Your free quote includes a recommended route and a timeline.
Get a Free Quote →What you send us, what we prepare
You send You
- Your content: documents, slides, instructor guides, or the existing Lectora titles (.awt files) and published packages
- Your learning objectives and audience
- A subject matter expert for content questions and reviews
- Your brand guidelines or an existing course template
- Your LMS name and the tracking standard it uses
- Accessibility requirements and target languages
We prepare IKHYA
- A file review and recommended route for each course
- The storyboard and a working prototype
- The built course in Lectora, with media and voiceover
- Review links in ReviewLink and a change log per round
- Test results for functions, accessibility and your LMS
- The final packages and editable source files
Example project: a legacy Lectora Inspire library made responsive and accessible
24 legacy Lectora Inspire courses turned into 21 responsive, accessible courses field crews finish on tablets
- Before
- A US electric and gas utility with about 3,200 employees had 24 compliance and safety courses built in Lectora Inspire 16 and 17. They only worked on desktop screens, two still had Flash-era elements, and the developer who built them had left.
- What we built
- An inventory of all 24 titles with a route for each. We upgraded 15 in Lectora Desktop with responsive layouts, rebuilt 6 with new branching scenarios, and retired or merged 3. The courses were built to WCAG 2.1 AA and Section 508 on one master template that uses Lectora inheritance. The 6 field-safety courses also got Spanish versions. The work ran over 14 weeks in 3 batches, with 2 review rounds per batch in ReviewLink, SCORM 2004 packages and testing in the client's LMS.
- How we measured
- LMS completion and session reports, 6 months after launch vs the 6 months before. The client also switched on automatic LMS reminders in the same period, so not all of the completion gain comes from the courses.
- What the client has now
- Editable Lectora source files for all 21 courses, the master template and a short update guide for its own team.
"We had 24 old Lectora Inspire courses that only worked on a desktop and that nobody wanted to touch. IKHYA sorted them into upgrade, rebuild or retire, ran every batch through ReviewLink, and now our field crews finish them on tablets. Our own team keeps the master template and makes the updates."
Hiring a Lectora freelancer or a team?
Some buyers start by searching marketplaces to hire Lectora freelancers in Hyderabad or elsewhere. A good freelancer can be the right call. Here is how the two options usually compare:
| Question | Freelancer | Team such as IKHYA |
|---|---|---|
| Best fit | One course, a quick fix, or extra hands for your own team | A curriculum, a legacy library, or a course that needs design, media, accessibility and translation |
| Skills covered | Usually Lectora development, sometimes design | Instructional design, Lectora development, media, voiceover, translation and LMS publishing |
| Continuity | Depends on one person's availability | A team of 120+ specialists, so work continues if one person is away |
| Handover | Agree on source files in the contract | Editable source files included |
If you already have a Lectora developer in-house and only need instructional design, tell us: the quote can cover just that part.
Lectora development FAQs
Instructional design, building new courses in Lectora, upgrading legacy Lectora Inspire titles, accessible builds to WCAG 2.1 AA and Section 508, translation, and publishing SCORM, xAPI or HTML5 packages. IKHYA hands over the editable Lectora source files at the end.
No. ELB Learning ended support for Lectora Inspire and Publisher 18 on December 31, 2024, and for version 17 on July 30, 2021. It tells users to upgrade to the current Lectora Desktop. See Have older Lectora Inspire courses?
Yes. We review each title and recommend one of three routes: upgrade it in current Lectora Desktop, rebuild it, or retire it and merge the useful content into another course. See Have older Lectora Inspire courses?
Not to run the courses. A published SCORM, xAPI or HTML5 package runs in your LMS or on the web without a Lectora license. You only need a license if your team wants to edit the source files later.
Yes, when they are designed and tested for it. ELB says Lectora can create content that complies with Section 508, and IKHYA builds accessible courses to WCAG 2.1 AA and Section 508. See Accessible Lectora courses.
SCORM 1.2, SCORM 2004, xAPI and HTML5, set up to track the way your LMS needs. Lectora itself can also publish cmi5, AICC and offline versions.
A freelancer suits one course, a quick fix or overflow work. A team suits a curriculum, a legacy library, or courses that need design, media, accessibility and translation together. See Hiring a Lectora freelancer or a team?
It depends on length, interactivity, media, languages and review rounds. Your free quote includes a recommended route and a timeline for your project. See How it works.
ELB says you access the current Lectora Desktop by logging in to The Studio by ELB Learning portal, and its knowledge base links to downloads for older versions it still supports. Lectora Online updates automatically.
Yes. IKHYA translates and localizes courses into 40+ languages, with human or AI voiceover. Lectora exports course text for translation and imports it back, so the translated text does not need retyping.
We quote every project individually. Cost depends on course length, interactivity, the starting point, media, accessibility, languages, review rounds and LMS testing. See What drives the cost of Lectora development?
Ready to plan your Lectora project?
Send us your content or a sample of your existing Lectora courses. Your free quote includes a recommended route and a timeline.
