For Lectora by ELB Learning

Lectora AI translation and localization tool.

New language. Same working course. Translate Lectora Desktop and Online exports with AI and 100% schema preservation. Bring your XLIFF, RTF, or HTML file. Get natural, context-aware language back without sacrificing course variables or WCAG accessibility markup.

Translate a course free See tag protection
  • Desktop + Online
  • Protected variables
  • Same-format return
Desktop .xlf and Online .html files are translated together, then returned to their original environments for successful import. Desktop .rtf is supported too.
100%

Schema preservationValid, supported exports. See scope.

3 formats

XLIFF, RTF + HTMLOne workflow for both Lectora environments.

100+

Target languagesContext-aware translation, course-wide.

The cost of a broken export

One missing tag.
Days of avoidable repair.

Lectora is an enterprise standard for highly accessible learning, giving developers precise control over interactions and WCAG-focused content. External translation is the awkward part. Desktop hands off XLIFF or RTF; Online uses HTML. A general-purpose AI tool sees a wall of text where Lectora expects a working document.

Strip an aria-label, rename a custom variable, or lose an inline code pair and the damage goes beyond a typo. Imports fail. Quiz logic breaks. A course that passed accessibility review lands back in remediation, and your instructional designers spend days fixing markup instead of reviewing the learning.

The language needs a rewrite. Your course structure does not.

Your course's structural layer PROTECTED

  • Import mappings

    XLIFF unit IDs, namespaces, inline codes, and RTF controls keep translated text connected to the right course objects.

  • Course logic

    Custom variable names and placeholders stay unchanged. A learner's language changes, not the conditions behind a button or quiz.

  • Accessibility relationships

    HTML tags, roles, IDs, and ARIA references remain connected instead of being treated as editable prose.

Text is translated. Protected code stays outside the AI rewrite path.
From export to reimport

How Lectora course
translation works.

Keep your authoring environment. Keep your file format. Replace the fragile translation handoff.

  1. Export from your Lectora project

    Use the translation export available in your version: XLIFF or RTF for Desktop, HTML for Online. Keep the original export and work from a copy of the source title.

  2. Translate the language, not the logic

    Select your target language. The AI reads neighboring segments for context, maintains corporate terminology, and translates learner-facing text while protected structural elements stay locked.

  3. Reimport. Then test.

    Download the translated file in its original format and return it to the matching title. Schema-preserved output removes translation-caused structural errors from the import. Preview the localized lesson before publishing.

Choose your authoring environment

Desktop: XLIFF or RTF

Your Lectora XLIFF translator and RTF translation workflow, without converting the export to plain text first.

.xlf.xliff.rtf
XLIFF
Unit IDs, namespaces, placeholders, and paired inline codes are preserved.
RTF
Formatting controls and structural mappings remain unchanged.
Return to
The translation import workflow for the original Desktop title.
Keep the export specification. No format conversion is required.

Online: protected HTML

Translate the HTML from your Lectora Online translation workflow, not a copy of visible text pasted out of the browser.

.html
HTML
Document structure, element IDs, tags, and protected attributes stay intact.
Accessibility
Roles and ARIA relationships are protected from structural changes.
Return to
The source Online project's supported translation import workflow.
Review learner-facing accessible names in the target language before release.
Start with a translation export, not a published SCORM ZIP. Export options vary by Lectora release.
.xlf → .xlf .rtf → .rtf .html → .html
Accessibility-aware file protection

Translate the words.
Leave the protected tags alone.

Your WCAG work lives in the details. A correct sentence is not enough if the button loses its accessible name.

Tag protection · EN → ES
Source snippet 
<source>Click <button aria-label="Submit Quiz">Here</button></source>
"Click" becomes "Haz clic"; "Here" becomes "aquí". The scanner skips the protected button tag and its ARIA attribute. This illustration keeps the accessible-name value unchanged to show the lock.

Structural parsing separates learner-facing text from protected code. The AI translates the language; it does not regenerate your HTML or invent replacement attributes. That distinction protects both the import and the accessibility structure your team already built.

  • Variables stay executable

    Custom variables and placeholders keep their names and bindings. Translation does not turn a course token into ordinary prose.

  • Inline codes keep their partners

    Lectora XLIFF translation preserves tag pairings, unit IDs, and namespaces so target segments still map back to their source objects.

  • Accessibility relationships stay connected

    Protect HTML roles, element IDs, and references such as aria-labelledby. Keep the metadata that assistive technology depends on.

Beyond a valid file

Human-level language.
Across the whole course.

A perfect import is only half the job.

A compliance course cannot sound like a collection of disconnected sentences. Qopywriter.ai reads across segments, connecting instructions, scenarios, and assessment feedback instead of translating each string in isolation. "Report" means something different in a reporting policy than it does in a sales dashboard. Context settles it.

Get human-level linguistic accuracy that rivals a professional translation agency: natural phrasing, consistent corporate terminology, and a regulatory tone that does not turn "must" into "might." The result reads like training written for the audience, not a literal copy with different words.

Keep subject-matter sign-off for regulated content. Spend that review on meaning and policy, not broken syntax.

Cross-segment context in practice EN → ES
01 / COMPLIANCE POLICY

You must report suspected bribery through the reporting channel.

Debe comunicar cualquier sospecha de soborno a través del canal de denuncias.

02 / FOLLOW-UP INSTRUCTION

Open the reporting channel to submit a report.

Abra el canal de denuncias para presentar una denuncia.

One term across segments Mandatory tone retained Illustrative compliance-training translation.

Corporate terminology

Keep recurring product names, policy terms, and internal language consistent from the opening screen to the final assessment.

Compliance register

Preserve distinctions between requirements, recommendations, and permissions. A mandatory action stays mandatory.

Instructional intent

Translate the task the learner needs to perform, not just the words in the text box. Instructions and feedback keep their purpose.

For developers, IDs + accessibility reviewers

Keep the release checklist.
Lose the tag repair.

Schema validity protects the file. Final QA protects the learner. Give both a place in your release process.

  1. Import into a project copy

    Use the matching source title. Check text-object mappings, custom variables, branching, quiz feedback, and scoring after import.

  2. Review the learner view

    Check text expansion, right-to-left layout, and line breaks. Images, audio, video, and captions need their own localization review.

  3. Test access, not just tags

    Confirm target-language accessible names and page language. Test keyboard controls, focus order, and screen-reader announcements.

  4. Publish and verify in the LMS

    Publish a fresh package from Lectora. Test completion, scores, and resume behavior in your actual LMS before releasing the course.

Straightforward translation pricing

Start with a lesson.
Plan for the course library.

Test your Lectora export before committing. Paid plans include context-aware AI, structural protection, and access to 100+ languages.

For lighter translation workloads

Lite

$9/ month

400.000 charactersper month

  • Context-aware AI translation
  • Structure and formatting protection
  • 100+ target languages
Start free trial
For regular course updates

Starter

$19/ month

1.000.000 charactersper month

  • Context-aware AI translation
  • Structure and formatting protection
  • 100+ target languages
Start free trial
For learning teams

Business

$49/ month

3.000.000 charactersper month

  • Unlimited team members
  • Structure and formatting protection
  • Priority support
Start free trial
Annual billing

Yearly

$169/ year

12.000.000 charactersper year

  • Unlimited team collaboration
  • Structure and formatting protection
  • Priority support
Start free trial
Technical questions, clear answers

Lectora translation,
without the guesswork.

File formats, accessibility scope, and what to check before a course goes back into production.

Working with an unusual export?
Send your Lectora version and file format to support@qopywriter.ai.
Can I translate Lectora XLIFF, RTF and HTML exports?

Yes. Use .xlf or .xliff for Lectora XLIFF translation, .rtf for a Desktop RTF workflow, or .html for Lectora Online. XLIFF 1.2 and 2.0 are supported. Choose the export offered by your Lectora version and return the translation to the same source title.

What does the 100% schema preservation guarantee cover?

The guarantee covers 100% preservation of the schema and protected structure in valid, supported exports. Translation-unit IDs, namespaces, paired inline codes, HTML attributes, RTF control syntax, and course variables stay intact. It does not repair an invalid source file, cover unrelated project changes, or certify the final course's accessibility.

Does tag protection make a translated course WCAG compliant?

No. Preserving accessibility markup protects the work already in your course; it does not certify the published experience. Review accessible names, page language, keyboard access, focus order, captions, and screen-reader output in every target-language version.

What happens to aria-label text during translation?

The demo deliberately locks aria-label="Submit Quiz" to show that protected metadata is not rewritten by the AI. Learner-facing accessible names still need approved target-language wording. Localize those values through your project's accessibility workflow and check the final published course with a screen reader.

How does the AI keep compliance terminology consistent?

The model reads across segments, using surrounding instructions, scenarios, and assessment feedback to resolve meaning. It keeps corporate terminology and the level of obligation consistent, so a mandatory instruction stays mandatory. Retain subject-matter and regulatory sign-off for regulated training.

Can I upload a published SCORM ZIP?

No, this workflow starts with a Lectora translation export, not a published SCORM ZIP. Import the translated XLIFF, RTF, or HTML file into its source project, complete localization QA, then publish a fresh LMS package. Test completion and scoring in your LMS.

What should I check if a file will not import?

Check that the file belongs to the same source title, matches its export format, and has not been resaved by an editor that changes encoding or markup. Compare it with the original export. Send support your Lectora version, file type, and the exact import error; use a redacted sample for confidential content.

Can I test Lectora translation before choosing a plan?

Yes. Start a free trial with a representative course export. Include a variable, quiz feedback, and an accessible control, then check the translated file in Lectora before choosing a paid plan. Trial character limits apply.

Put the round trip to the test

Start with one Lectora lesson.

Choose a lesson with a quiz, a variable, and an accessible control. Translate the export, reimport it, and test the learner experience. Keep the original file beside you.

Translate a Lectora export

New to Qopywriter.ai? Start a free trial.