Articulate spent 2026 shipping AI about as fast as it could write release notes. The Q1 update put AI-generated images straight into course drafts and let you set how long a generated course should run. In July, Rise 360 added an AI Tutor in public beta — a course-aware chatbot that answers a learner’s questions inside the course — alongside skip-ahead quizzes that let people pre-test out of content they already know. Storyline 360 picked up AI that syncs animation timing to narration, and both tools gained real localization and accessibility work. It is a strong run of releases.
Every one of those features is worth having. None of them is a good reason to choose, or to switch, your authoring tool. The question a learning team should be asking is not which vendor shipped the best AI this quarter. It is which tool fits the content you actually make and the team that has to author it. The feature list is the most visible part of that decision and close to the least important.
What actually shipped in 2026
The direction across the releases is consistent. AI is moving from a drafting aid to something that sits inside the finished course: the AI Tutor answers a question at the moment a learner is stuck, instead of sending them back to a search bar. Skip-ahead quizzes are an adaptivity feature — the course adjusts to what someone already knows rather than marching everyone through the same slides. The localization work covers custom block translation, timelines that re-time per language, and layout that resizes to fit translated text, which matters to any team shipping one course in eight languages. And the accessibility investment — a WCAG checker, keyboard and screen-reader support for more question types — is the least flashy and probably the most consequential, because it is the part most likely to be a legal requirement rather than a preference.
Two things are worth noticing about that list. The features are strong, and they are not unique. AI course generation, an in-course chatbot, adaptive pre-tests, a WCAG checker, localization at scale — these are the same bets every serious authoring vendor is making right now. A year from now the feature comparison will be close to a tie, and the thing that was actually different about each tool will be the thing that was always different: what it is built to make.
Features are a poor axis for the decision
Authoring tools converge on features and diverge on shape. Rise 360 is built to let a subject-matter expert assemble a clean, responsive course in a browser without ever opening a timeline. Storyline 360 is built for control: software simulations and branching scenarios, the work that needs a real developer and a real timeline. Those two are not competing on their changelog. They are answers to different questions, and Articulate sells both precisely because most organizations need one far more than the other and often cannot tell which.
Widen the field and the same holds. Adobe Captivate leans into responsive and software-simulation work. iSpring keeps authoring inside PowerPoint for teams that will never adopt a standalone tool. Lectora has long been the pick where accessibility and compliance are the hard requirement. Elucidat and dominKnow are built for many authors working on a shared library at enterprise scale. None of these is the best tool. Each is the best tool for a particular kind of team making a particular kind of content.
What should actually decide it
The real decision runs on four questions, none of which appears in a feature announcement. What kind of content do you make most of the time — linear knowledge, practiced skill, software steps, or reference people dip into? Who has to author it, and what will they realistically learn to use? How does it have to be delivered and tracked — which LMS, SCORM 1.2 or xAPI, and which accessibility standard you are legally on the hook for? And what does switching actually cost, once you count re-authoring the existing library and the months of slower output while the team climbs the curve?
The most expensive line in any tool switch is rarely the license. It is the existing library. A few hundred courses built in one tool do not move to another by export — they get rebuilt, one at a time, by the same team that still has to keep the current catalog running. That single cost is what makes “the tool with the better AI” a weak reason to move, and “the tool our content and people actually fit” the only one worth the disruption.
Choosing a supplier is the same question
The supplier decision — build in-house, or bring in a partner — has the same shape, and the new AI features sharpen it. When a first draft is nearly free to generate, the value a good development partner adds stops being production and becomes judgment: deciding what actually needs to exist, and building the parts a generator still cannot — the interaction that changes behavior, and the tracking and accessibility that hold up in an audit. That is a longer argument, made here. A supplier chosen for how fast they can produce courses is now competing with a chatbot. One chosen for how well they diagnose the problem is not.
The best authoring tool is not the one with the newest features. It is the one your content and your authors already point to.
The tool is downstream of the work
The tools will keep leapfrogging each other, quarter after quarter, and the AI features especially will keep getting better in ways that are easy to demo and hard to resist. The teams that choose well read the release notes as news rather than instruction. They start from the content they make and the constraints they carry, and let the tool fall out of that. Articulate’s new features are good. They are still the last thing you should decide on.