Illustrated cover reading "How to Make a Responsive eLearning Course That Works on Phones" on a lilac and peach background with a topo pattern

How to Make a Responsive eLearning Course That Works on Phones

Table of Contents

Share:
Easily share intel
Summarise this page with your favorite AI assistant

A responsive eLearning course reflows its text, images and controls to fit the screen. You build it once, and it works on a phone, a tablet and a laptop. The skill is in setting clear rules for small screens and then testing on real phones before you publish.

Most phone problems go beyond layout. Buttons are too small, drag-and-drop does nothing, a video will not start, or the LMS mobile app never records completion. This guide covers each problem and its fix.

It is for trainers, subject-matter experts and small L&D teams who build in an authoring tool without writing code. It includes a table that matches each screen element to a phone fix, and a checklist to run before launch. Facts are current as of November 2026.

Key takeaways

  • Design the narrowest screen first. WCAG 2.2 asks that content work at 320 CSS pixels wide without sideways scrolling.
  • Treat touch as the default. Hover effects and drag-and-drop need a tap-friendly alternative.
  • A course that looks fine on a phone can still fail inside an LMS mobile app, so test the exported package there.
  • Test on real phones, not just a resized browser window.

What is responsive eLearning, and how is it different from a separate mobile version?

Responsive eLearning is one course that rearranges itself to fit the screen. A separate mobile version is a second build made for phones. Adaptive design sits between the two and swaps certain elements by device. In our judgment, responsive design is cheaper to maintain because you update only one course.

Authoring tools use these words differently. Gomo’s documentation says adaptive design changes interactive elements by device type, such as turning a side-by-side filmstrip into a swipeable vertical one on mobile. dominKnow’s page describes both a fixed-layout mode and a responsive mode. Check which your tool exports.

Approach How it works Best fit Main drawback
Responsive One course; layout reflows by screen width Mixed devices; text-led content with light interaction Complex layouts need more design thought
Adaptive One course; some elements swap by device Interactions that cannot simply reflow More settings to test on each device
Fixed layout, scaled Slides shrink to fit the screen A quick fix for an old slide-based course Text often becomes too small to read
Separate mobile version A second build for phones Phone-only learners doing a different task Two courses to review and update

The last two rows are our judgment, not a vendor claim.

How do you set up a responsive eLearning layout for phones?

Start with the narrowest screen. Use one column, put content in reading order and let blocks stack. WCAG 2.2 asks that content work at a width of 320 CSS pixels without two-dimensional scrolling, so make 320 your smallest test width. Add wider layouts after the phone version works.

The W3C Reflow criterion excepts parts that need a two-dimensional layout, such as data tables, maps and diagrams. Headings and buttons around a table must still reflow.

A breakpoint is a screen width where the layout changes. One FAQ, published in 2016 and updated in 2021, lists 320, 480, 768, 1024 and 1280 pixels, which follow old devices. Our judgment is to set breakpoints where your own content starts to look wrong. Most courses need only two or three.

Two more settings matter. WCAG 1.3.4 says content should not lock itself to one orientation unless that orientation is essential. If you edit page code, MDN’s viewport guidance recommends width=device-width. It warns that blocking zoom with user-scalable=no stops people with low vision from reading the page.

Pro tip: Draft the Phone Screen First. In your storyboard, sketch the 320-pixel screen before the desktop one. If a screen needs two ideas, a table wider than three columns, or a hover to make sense, split it or redesign it now. Our eLearning storyboard template guide shows a screen-level format you can adapt.

How big should text and buttons be in a responsive eLearning course?

Use body text of at least 16 pixels and make every control easy to hit with a thumb. WCAG 2.2 Level AA sets a minimum target size of 24 by 24 CSS pixels, with exceptions. The stricter AAA level asks for 44 by 44. On a phone, aim for the larger size.

The Target Size (Minimum) criterion lets a small target pass if a 24-pixel circle centered on it does not touch another target. So space between buttons counts as much as button size.

The 16-pixel figure comes from iSpring’s mobile course guide, which also advises against inline text links because swipes cause accidental taps. Use buttons instead. Text must also grow: WCAG 1.4.4 requires resizing to 200 percent without losing content. If your player blocks pinch zoom, treat that as a defect. Our WCAG 2.2 AA guide for eLearning covers the wider rules.

How should tables, images and video work on a small screen?

Keep tables small, make images fit the screen width, and start video only when the learner taps play. Wide tables break a single-column layout. Large images push text out of view. Browsers often block autoplay, so a video that relies on it may sit still.

For tables, limit each to three columns or turn every row into a stacked card. If a wide table must stay, let it scroll sideways inside its own box, which the reflow exception allows. Never put text inside an image, because it cannot reflow.

For video, MDN’s autoplay guide says browsers allow autoplay when the video is muted or the learner has already interacted with the page. It also says Safari needs the playsinline attribute. If playback is blocked, show a manual play button. Add captions so the video still works with the sound off.

What should you change for each screen element in a responsive eLearning course?

Check every screen element against a phone. If it needs a mouse, a wide screen or a fixed size, change it. The table lists common elements, what goes wrong and the fix. Rows tied to a standard name it; the other fixes are our judgment.

Screen element What goes wrong on a phone Fix
Wide data table Columns get cut off or squeezed Three columns or fewer, or stacked cards; scroll only inside the table
Small icon buttons Thumbs miss or hit the neighbor At least 24 by 24 CSS pixels (WCAG AA); aim for 44 by 44 with space around
Hover tooltips and reveals Touch screens have no hover Tap to open; content must be dismissible and stay visible (WCAG 1.4.13)
Drag-and-drop matching The page scrolls instead; drops miss Offer tap-to-select, tap-to-place (WCAG 2.5.7 asks for a single-pointer option)
Image hotspots Hotspots are too small to tap Enlarge them, or swap for a numbered list or accordion
Infographic with text inside Text is tiny and cannot reflow Rebuild as live text plus a simple image; offer tap to enlarge
Autoplay video Blocked, or unsupported full screen Show a play button; add captions; keep clips short
Pop-up links to other sites May not open in an LMS app player Put the reference inside the course, or use a plain link and test it
Locked screen orientation Learners must turn the phone to read Support both orientations unless one is essential (WCAG 1.3.4)
Fixed-size simulation Shrinks until it cannot be used Replace with a short video and a quiz, or label it clearly as larger-screen only
Free-text answer box The keyboard covers half the screen One short field per screen; prefer choices where the goal allows

If you build many courses, make these fixes once inside reusable blocks. Our guide to interactive eLearning template blocks explains how to set that up.

Why does a phone-ready course still fail in an LMS mobile app?

A responsive course can still fail because the LMS app sets its own limits. SCORM does not control how a course looks, and it needs a connection to report progress. Some apps also block features such as pop-ups. Always test the exported package in the app your learners use.

iSpring’s guide, last updated September 2026, says SCORM runs on phones if the browser can run JavaScript. Poor display, it says, usually comes from the authoring tool or LMS. It also says that opening a zipped package directly in a browser records nothing in the LMS. SCORM.com adds that reporting normally needs a constant internet connection.

Offline use is the next trap. iSpring says SCORM stats are not recorded offline, and that offline tracking needs an LMS app built for it. Docebo’s mobile app help article (undated, as of November 2026) says SCORM should be responsive HTML5 and that multi-SCO packages do not work offline. It also says pop-up links to outside sites and fullscreen autoplay video are not supported inside SCORM.

An older Moodle developer specification for its mobile SCORM player covered SCORM 1.2 zip packages only. Treat that as a reason to ask your LMS vendor, not as today’s rule. For crews with patchy signal, see our guide to mobile learning for aviation crew.

Pro tip: Test the Exit Path, Not Just the Content. Docebo says learners should leave through the app’s own X button, and the package must send the SCORM FINISH command before it closes. A course that plays perfectly but ends without that command can show as incomplete. Close it that way in every test.

How do you test a responsive eLearning course on real phones?

Publish the package, load it in your LMS, and open it on real phones. A resized browser window is a start. Chrome’s documentation calls device mode a first-order approximation and advises running the page on an actual device when in doubt. Our SCORM package QA checklist covers the LMS side.

Before you publish, work through this phone test checklist on at least one iPhone and one Android phone:

  • Open the exported package in the LMS, and in its mobile app if learners use one.
  • Rotate the phone and zoom text to 200 percent; nothing may be lost or cut off.
  • Tap every button with a thumb at 320 pixels wide; watch for sideways scrolling and mis-taps.
  • Play each video from a tap, with captions, on mobile data.
  • Complete every drag or hover activity by touch alone.
  • Finish the course and confirm the completion status and score in the LMS report.
  • Close the course halfway, reopen it, and check that it resumes where you stopped.
  • If you promise offline use, switch to airplane mode and confirm what the app records.

What should you do next?

Pick one live course and run the checklist on two phones. Match each failure to a row in the screen-element table and fix the three that hurt learners most. Then retest in your LMS app.

If you are choosing a tool, ask for a SCORM export you can test yourself. SimpliAuthor is made by SimpliTrain, the same company that publishes this site, so weigh this mention accordingly. Based on the vendor’s published pages as of November 2026, it mentions a single responsive canvas for editing and exports SCORM 1.2 and SCORM 2004 packages. We have not tested its output on phones. You can start free with SimpliAuthor and run the checklist on a package of your own.

Frequently asked questions

What is the difference between responsive and mobile eLearning?

Responsive eLearning is a design method: one course adapts to any screen. Mobile learning describes where and when people learn, such as in short moments away from a desk. A mobile learner can use a responsive course, but a course built only for desktop will fail them.

What screen sizes should I test a responsive course on?

Start at 320 CSS pixels wide, the width WCAG 2.2 uses for reflow. Then test one larger phone and one tablet. Real devices beat emulators, because Chrome describes its device mode as only a rough approximation. Use the phones your learners carry.

Does SCORM work on mobile phones?

Yes, with limits. iSpring’s guide says SCORM runs on phones if the browser can run JavaScript, and that it does not control how content looks. Tracking needs a stable connection, and Flash courses do not run at all. App players can add rules of their own, so test in the app.

Can learners finish a SCORM course offline on a phone?

Only if the LMS app supports it. iSpring says SCORM stats are not recorded offline in a normal browser. Docebo’s help article says multi-SCO packages do not work offline in its app. Ask your LMS vendor what its app supports, then test one package before you promise offline use.

Should I turn off pinch zoom in my course?

No. MDN warns that disabling zoom with user-scalable=no prevents people with low vision from reading the page, and WCAG requires text to resize to 200 percent. Browsers may ignore the setting anyway. If your authoring tool blocks zoom, ask the vendor for a fix or choose another output option.

Want to learn more?

Reach out to us to learn more.

One Platform for
All Your Training Needs

Get a personalized demo.