Forum Discussion
Dark Mode
For accessibility, could we get an option for the user to choose Dark Mode?
19 Replies
And for the editor too. Eeesh. It's sooo bright....
I welcome the Darkside. I hope they will implement it soon.
Hello CarrieAnders421,
Thanks for sharing your voice with us! While this isn't currently available, I've shared your insight with our product team. We'll be sure to share any future updates in this thread so all are in the loop.
Have a great start to your week!
https://community.articulate.com/discussions/discuss/dark-mode-for-storyline-360/917863
This has been a problem for more than seven years. When is this cut-and-paste answer going to change? It is an accessibility + usability issue that every other company has figured out.
I also hope dark mode will be available soon for developers because like Loupetron said, It's bright. Hurt my eyes when I work on my projects for long hours.
Developers have been asking for dark mode for years, we need an update before we go blind!
There is another request for dark mode here:
https://community.articulate.com/discussions/discuss/dark-mode-for-storyline-360/917863This! So much this! All my other apps are set to dark mode. Opening Storyline is like turning on a flashlight in a dark room at midnight.
This isn't just a minor preference or a "nice-to-have" feature—a native Dark Mode for Storyline 360 is a fundamental accessibility and usability requirement for professional e-learning developers.
1. Reduce Eye Strain & Prevent Cognitive Fatigue
The vast majority of developers using Storyline are working in front of screens for 10 to 12 hours a day. Staring at a high-contrast, bright white canvas framed by an equally bright white, unyielding UI for hours on end causes severe eye fatigue, chronic headaches, and physical strain.
When every other core tool in a modern developer's tech stack—from the Adobe Creative Cloud suite to Microsoft 365, browser dev tools, and audio/video editing software—supports system-level dark themes, switching into Storyline’s glaring white interface is like stepping into a room with harsh fluorescent lights on full blast. It isn't just "jarring"; it is physically uncomfortable and directly impacts how long we can sustain focus without suffering digital eye strain.
2. Biggest Workflow Impact: Contrast Distortion & Color Accuracy
The current bright UI has a massive negative impact when designing custom UI components, high-contrast layouts, or darker, immersive slide themes:
- Perceptual Color Distortion: Designing dark-themed slides, custom video interfaces, or low-light scenarios inside a blinding white authoring tool distorts visual perception. White surroundings trick the eye, making slide colors, contrast ratios, and subtle gradients appear drastically different than they actually are.
- Seamless Context Switching: Many of us work across dual or triple monitor setups, constantly moving assets between Photoshop/Illustrator (in dark mode) and Storyline. Flash-banging our eyes every time we drag an asset into Storyline causes constant visual readjustment, disrupting focus and breaking flow state.
3. What Difference Would Dark Mode Make?
For individual developers and enterprise teams alike, a dark mode interface translates to:
- Sustained Productivity & Health: Decreased physical fatigue means longer periods of deep focus and better well-being during intense project crunch times.
- Modern Industry Standard: Storyline is the flagship tool in the instructional design industry. The lack of a dark UI makes the software feel visually dated compared to every other major professional design tool on the market today.
- Accessibility Compliance for Authors: Accessibility isn't just for end-users viewing published courses; it applies to the content creators building them. Light sensitivity, photophobia, and migraines are real conditions, and an all-white UI actively creates a barrier for developers with visual sensitivity.
The community feedback across this forum is overwhelming and consistent: we need a Dark Mode theme option for the Storyline authoring interface.
We love the power of Storyline, but we desperately need an interface that prioritizes the health, comfort, and daily working reality of the professionals who rely on it for hours every single day. We strongly urge the product team to move this from a discussion topic into active development.
Well said. I think the key point is that Dark Mode is no longer viewed as a cosmetic feature in professional software.
Most creative and development tools now offer theme options because they recognize that people spend entire workdays inside these applications. For devs that utilizes Storyline who regularly work 8-12 hours creating courses, a Dark Mode option would improve comfort, reduce visual fatigue, and bring Storyline in line with modern industry standards.
What is particularly surprising is that this isn't a new request. Community members have been asking for Dark Mode for more than six years, and the feedback has remained remarkably consistent throughout that time. Given the clear demand and the fact that Dark Mode has become a standard feature across most professional authoring, design, and development tools, it's difficult to understand why Storyline still lacks this option.
I understand that every product team has competing priorities, but after so many years of user requests, it would be helpful to hear more transparency about whether Dark Mode is on the roadmap or what challenges have prevented its implementation.
The request isn't about replacing the current interface. It's about giving users a choice that better supports productivity, accessibility, and long-term comfort while using Storyline every day.
Dark mode is no longer a niche feature. It has become a standard expectation across modern software platforms because it supports accessibility, learner comfort, and user choice. For eLearning specifically, dark mode can reduce eye fatigue during lengthy training sessions, improve usability in low-light environments, and better accommodate individuals with light sensitivity or migraine-related triggers.
From a user experience perspective, providing both light and dark viewing options recognizes that learners have different needs and preferences. Many employees already use dark mode in their daily tools and applications, making a consistent experience across platforms increasingly important.
What makes the lack of dark mode particularly frustrating is that it has been a highly requested feature for many years. Despite repeated customer feedback and the widespread adoption of dark mode throughout the software industry, Articulate has yet to provide a comprehensive solution that allows course creators to easily offer this option to learners.
For a company whose products are centered on learning accessibility and learner engagement, dark mode should not be viewed as a cosmetic enhancement. It is a meaningful usability feature that supports inclusivity, aligns with modern software standards, and improves the overall learner experience. As organizations continue to prioritize accessibility and user-centered design, the ability to create courses that support dark mode becomes increasingly important rather than simply a "nice-to-have" feature.
Hello AliciaHiltner,
I appreciate you bringing the learner’s experience into this discussion. You’ve highlighted the value of giving learners more choice in how they experience course content, and I’d love to better understand what that flexibility would ideally look like for you.
- Would learners choose their preferred mode, or would authors control it?
- In what types of courses or learning situations would dark mode make the biggest difference?
- Which course elements would you want Storyline to automatically adjust so your design works well in both light and dark modes?
Thanks for highlighting the connection between accessibility, learner choice, and course design. That adds a valuable perspective to the conversation around dark mode.
To be candid, I'm surprised these questions still need to be asked. Articulate's business is creating tools for learning professionals, and dark mode has been a widely adopted accessibility and usability feature across digital products for years. Understanding when learners benefit from dark mode, why they request it, and what interface elements would need to adapt seems like foundational user experience research for a platform of this maturity. The discussion shouldn't be about discovering the need anymore; it should be about how and when the feature will be implemented.
The biggest benefit of dark mode is author and learner comfort over extended periods of screen time. When learners are comfortable, they are less likely to experience visual fatigue (which you will find in other's responses as well). The core purpose of dark mode is improving the overall user experience.As learning professionals, we're constantly encouraged to remove barriers that don't contribute to the learning objective. If a learner spends part of their mental energy dealing with screen discomfort, glare, or visual fatigue, that's energy that isn't being spent on learning. Dark mode is a simple way to reduce that friction and create a more comfortable experience for a significant portion of the audience.
That's ultimately why this request has persisted for so long. It's not a cosmetic feature. It's a user experience feature that helps learners focus on the content rather than the interface.
