Update: Articulate 360 will discontinue support for Internet Explorer 11

Starting in January 2022, we will remove support for the Internet Explorer 11 browser (IE11) from all Articulate 360 web apps, Articulate.com, and E-Learning Heroes.

Why we’re making this change

Microsoft stopped supporting IE11 in its Microsoft 365 apps as of August 17, 2021, and will also stop supporting IE11 on Windows 10 on June 15, 2022.

Who this impacts

This change impacts folks using IE11 with Articulate 360 or Storyline 3 or visiting Articulate.com and the E-Learning Heroes community. Here’s what you need to know:

Beginning January 1, 2022, you won’t be able to:

  • View Articulate.com or the E-Learning Heroes community using IE11
  • Use Articulate 360 Training or Review 360 or view 360.articulate.com using IE11

Beginning July 1, 2022, you won’t be able to: 

  • View courses published from Storyline 360, Studio 360, or Rise 360 in IE11
  • Publish to CD from Storyline 360 or Studio 360 (this feature uses IE11 to publish content) 

Beginning October 1, 2022, you won’t be able to: 

  • View courses published from Storyline 3 in IE11
  • Publish to CD from Storyline 3 (this feature uses IE11 to publish content) 

What to do if you use Internet Explorer 11

Depending on your operating system, we recommend downloading the latest version of a browser like Microsoft Edge, Google Chrome, or Mozilla Firefox.

Learn more at our support knowledge base.

Edited to add: We'd like to address a common question! Courses published prior to July 1, 2022 will continue to work in IE11. These changes will only apply to courses published after July 1, 2022.

We're sorry our language was unclear!

30 Replies
Joe Tansengco

Hi Barry,

This thread is regarding the announcement that we're discontinuing support for Internet Explorer 11, but if you need assistance in hosting content in SharePoint, you can check out this article: 

Viewing Articulate 360 Content in SharePoint Online

Note that we do not provide support for hosting content in SharePoint, since this is an environment that does not support HTML, but we hope the article points you in the right direction. 

Barry Greene

My original communication was concerning not only the discontinuing of support for internet explorer 11 but also the loss of "Publish to CD" option which we rely on heavily when we have issues connecting to our LMS.

Articulate plans to discontinue that option but without offering any real solutions.

In the past we "published to CD" on our Share-point and people have recommended "publish to the Web" then converting the files to .aspx but evidently that no longer works either.

I really wish Articulate would give us another option that would work for the modern Share-point.

Thanks,

 

Jennifer Brown

Hey, all who might be following this:

We LMS Admins and Learning Orgs must account for changes in browser related technology. 

My organization (mainly me and my application support team that maintains our LMS) had a bear of a time getting our content working on Edge. Shoutout to Taylor and others on the Articulate Support team. (Thank you, Taylor for the above and beyond!)

Ultimately, we spent too much time dealing with one of those very tiny issues that causes problems (secure vs unsecure HTTP links).

A bigger issue was an opportunity to make our LMS validation procedures more robust. Because not all our developers were updating their Storyline when updates occured, and while those WBTs worked on IE11, they did not work on Edge. (Storyline 360 isn't an option for us). 

As an LMS Admin (and Storyline developer), the headaches became an opportunity to update our validation and review procedures to:

1) Ensure any content being added or revised be built in current Storyline 3 version, and

2) Establish a firm republish/retire/revise protocol.

It has to be updated periodically to avoid the stress of things like Flash End of Life, and IE11 retirement, and other browser technology changes. So my validation procedures not include checking the Storyline build version before I start testing. And the content development procedures are being updated to include a minimum two year review cycle that will include republishing even if nothing is changing. We happen to have some content that has been around in one version or another for over 10 years. It's evolved, but still valid. And it must be able to function in the current Storyline build.

In my experience, the interruptive technology changes are more likely after two years.  Some are bigger than others, but if content gets republished in a current build at least every two years, there's less likely of the scrambles like Flash end of Life, or as we discovered, synchronous xhr.

Updating 150+ WBTs at a time isn't ideal. So read those release notes and keep content in current builds. :D