What features could Articulate add to Storyline 360 to improve accessibility for learners with disabilities?

Introduction

To improve accessibility for learners with disabilities in Articulate's Storyline 360, we need to identify and implement features that enhance the learning experience for users with various disabilities. I'll approach this by understanding the current product context, analyzing user segments, identifying pain points, generating solutions, and proposing a roadmap for implementation.

Step 1

Clarifying Questions

• Looking at the e-learning authoring tool market, I'm thinking Storyline 360 might be facing increased competition from more accessible alternatives. Could you share insights on our current market position and how accessibility features might impact our competitive edge?

Why it matters: Determines the urgency and scope of accessibility improvements Expected answer: We're market leaders but losing some ground to more accessible competitors Impact on approach: Would prioritize quick wins and differentiating accessibility features

• Considering the diverse nature of disabilities, I'm wondering about our current user base. Can you provide information on the types of disabilities our users most commonly report struggling with when using Storyline 360?

Why it matters: Helps focus our efforts on the most impactful accessibility improvements Expected answer: Visual and motor impairments are the most reported issues Impact on approach: Would prioritize features addressing these specific disability types

• Given the complexity of e-learning content, I'm curious about our current accessibility standards. What level of WCAG compliance does Storyline 360 currently meet, and what are our goals in this area?

Why it matters: Sets a baseline for improvements and aligns with industry standards Expected answer: Currently at WCAG 2.0 Level A, aiming for Level AA Impact on approach: Would focus on bridging the gap between current state and Level AA requirements

• Considering the technical aspects of Storyline 360, I'm interested in understanding our current architecture. How flexible is our system for implementing new accessibility features, particularly those that might require deep integration?

Why it matters: Influences the feasibility and timeline of proposed solutions Expected answer: Modular architecture with some legacy components Impact on approach: Would balance quick wins with longer-term architectural improvements