Questions answered by this guide
- What should I check before publishing a translated course?
- Which localization checks are automated and which are manual?
- What is the most common thing missed when localizing an eLearning course?
- Do I need to re-check accessibility after translating a course?
What you'll learn
- Run this once per language version, comparing that version to the source
- A11yCheck automates 10 mechanical source-vs-target checks; the rest of this list is manual
- The single highest-yield manual check is previewing every screen at 100 percent for clipped or overlapping translated text
- Player and navigation labels are translated in their own separate place and are the most commonly missed item
What's inside
Reviewers signing off a localized Storyline or Rise course before release
- 01How to use this
- 02Best practices
- 03Common mistakes
- 04Automated checks (A11yCheck Localization review)
- 05Manual checks
- 06Accessibility after localization
Why it matters
A localized course is a new deliverable. It can be missing slides, clip translated text, keep the source language in its navigation, lose a font, or fall out of sync with its voice-over, none of which show up in a translation review or in the source-language sign-off. Running a short, consistent pass per language catches these before a learner does.
Best practices
- Run this pass once per language version, comparing that version against the same source, and keep a separate record of what each language turned up.
- Let A11yCheck's Localization review do the 10 mechanical source-vs-target comparisons first, then spend your time on the manual checks it cannot make.
- Preview every screen at 100 percent size in the target language before anything else, clipped and overlapping translated text is the highest-yield thing you will catch by eye.
- Translate the player and navigation labels in their own location (Storyline: Settings, then Labels; Rise: the course Labels), separately from the translated slide content.
- Run a full A11yCheck Accessibility review on each language version's URL. The source-language accessibility sign-off does not carry over to a translation.
- Keep a short per-language glossary so you can check terminology consistency by hand, no automated check verifies it.
Common mistakes
- Signing off a translated course on the strength of a good translation review alone, missing slides, clipped text, and lost fonts do not show up there.
- Checking only the target course and never comparing it to the source, so dropped slides and missing media go unnoticed.
- Leaving the player and navigation labels in the source language because they are not part of the translated content export.
- Treating every difference between source and target as a defect, a localized course is meant to differ; the review looks for differences with a real consequence.
- Assuming the Localization comparison also re-checks accessibility. It does not; that is a separate review, run per language version.
Practical checklist
- AUTOMATED (A11yCheck Localization review compares source vs target): No target text is clipped where the source was not.
- AUTOMATED: Every source slide has a matching target slide, and vice versa, or the difference is explained.
- AUTOMATED: No target slide is left byte-identical to the source on real content (untranslated exact-match text).
- AUTOMATED: Where the source shows a date, number, or currency, the target slide has a comparable pattern.
- AUTOMATED: Text direction is consistent; a right-to-left target is treated as expected, not flagged.
- AUTOMATED: The target slide's fonts overlap with the source's (no silent whole-slide font substitution).
- AUTOMATED: A single source video or audio element matches its target counterpart in length within tolerance.
- AUTOMATED: The set of link destinations is compared between source and target.
- AUTOMATED: A single caption track matches between source and target on cue count and total span.
- AUTOMATED: Each slide has the same number of media elements in source and target.
- MANUAL: Preview every screen at 100 percent size and look for clipped, wrapped, or overlapping translated text.
- MANUAL: Player and navigation labels (Next, Previous, Submit, menu, quiz feedback) are in the target language. In Storyline this is Settings, then Labels; in Rise it is the course Labels.
- MANUAL: Non-Latin scripts (Cyrillic, CJK, Arabic, Thai, and similar) render in an embedded font that matches the design, not a system fallback.
- MANUAL: Dates, numbers, currency, and units are in a form appropriate to the locale, not just present.
- MANUAL: For right-to-left languages, the layout mirrors correctly and Tab order follows the visual reading order.
- MANUAL: Links open locale-appropriate destinations where a localized target exists.
- MANUAL: Captions and transcripts exist in the target language and read correctly, not just present as a track.
- MANUAL: Voice-over is in the target language, and timeline-synced animations or captions still line up with it.
- MANUAL: Every quiz question and answer option is present and translated; feedback layers are translated.
- MANUAL: Variables and dynamic text resolve, with no %placeholder% or untranslated variable text visible to a learner.
- MANUAL: Terminology is consistent with the glossary for this language.
- MANUAL: Text baked into images or screenshots has been localized or has a localized text alternative.
- MANUAL: Branching paths and interactions reach the same content they do in the source.
- MANUAL: Nothing in the localized content is culturally inappropriate for the target audience, and the learning intent is unchanged.
- ACCESSIBILITY (separate review, run per language): A full A11yCheck Accessibility review has been run on this language version's URL.
- ACCESSIBILITY: The course language is set for this version (screen readers use it to pick pronunciation rules).
- ACCESSIBILITY: Accessible names, alt text, and instructional text are in the target language, not left in the source.
- ACCESSIBILITY: Reading and focus order still make sense after any layout changes from text expansion or mirroring.
How A11yCheck reviews this
The items marked AUTOMATED are what A11yCheck's Localization review compares between the source and target rendered courses. It reports a difference only when it has a real consequence, not on every difference. The items marked MANUAL are not automated by any A11yCheck review. The items marked ACCESSIBILITY are covered by A11yCheck's separate Accessibility review, which you run on each language version's URL, they are not part of the Localization comparison.
Frequently asked questions
Do I run this once, or once per language?
Once per language version. Each version is compared against the same source, and each gets its own record of what was found.
Which of these does A11yCheck actually do for me?
The 10 items marked AUTOMATED. Everything marked MANUAL is a human check. The items marked ACCESSIBILITY are done by A11yCheck's separate Accessibility review, not the Localization comparison.
What is missed most often?
Player and navigation labels. They stay in the source language unless translated in their own separate location (Storyline's Labels tab, or Rise's course Labels), which is not part of the translated content export.
Is checking accessibility again really necessary after translation?
Yes. Translation can leave accessible names in the source language, drop or change the course language setting, and shift reading order when expanded text reflows a layout. The source-language accessibility sign-off does not carry over.
Related Guides
Localization QA for eLearning: What to Check in a Translated Course→
Localization QA is checking that the translated version of a course still works the way the source does, structurally, visually, and for assistive technology, not judging whether the wording is good. Here is what to review source-vs-target, and which of those checks A11yCheck runs automatically.
Text Clipped Guide: Why Text Gets Cut Off and How to Fix It→
Text gets clipped when a fixed-size text box doesn't grow to match zoomed-in text, so words are cut off at the box's edge. Here's how to fix it in Storyline and Rise.
Accessibility After Localization: What Translation Can Break→
A course that passed an accessibility review in its source language can fail in a translated version. This covers the regressions translation introduces, missing language metadata, untranslated accessible names, right-to-left reading order, font fallback, and reflow from expanded text, and what A11yCheck can and cannot see.
Localizing in Storyline vs Rise: What to Review in Each→
Storyline and Rise take different approaches to localization, and that changes what you review in each. This covers the concrete differences: Storyline's Localization menu, Layout Issue Finder, and Labels tab, and Rise's lack of an equivalent finder plus its shared-image behavior.
Before You Publish Checklist→
A short checklist to run through before you publish any Storyline or Rise course. It covers accessibility, course quality, and course engagement in one pass.
Course Review Checklist: A Role-Based Process for Reviewing eLearning→
Before You Publish Checklist is one person's fast pass right before hitting publish. This is the process a course goes through to get there: who reviews what, in what order, before anyone signs off. Use this when more than one person touches a course before it launches.
Summary
A per-language pre-publish pass for a translated course, split into the 10 mechanical checks A11yCheck compares between source and target automatically, and the manual checks (text fit, player labels, fonts, locale formats, RTL, links, media and caption language, quiz parity, variables, terminology, cultural fit) that still need a human. Accessibility is a separate review, run it on each language version.
Review your course before you publish it.
A11yCheck reviews Storyline and Rise courses for:
- Accessibility
- Course Quality
- Course Engagement
www.a11ycheck-dev.com