Rise upload video file accessibility ideas?
We hit a showstopper accessibility snag with Rise's upload multimedia block. We are required to use WAVE as our checker and it throws a missing video alt tag error for videos we upload. We've looked at these possible solutions but they raise other issues or they're unknown territory. Wondering if anyone has found a solution?? Solutions we've discussed so far... Continue to use file upload and use the video caption field and text before the video block to describe the content (likely no: organization needs a clean WAVE test) Self host videos on our server (no, not optimized for streaming, captioning) Embed the video and host it on YouTube: (can of worms when it comes to privacy, Google terms of use, video participant consent). We are looking at other video hosting platforms with more nuanced sharing and embedding controls... Provide an accessible PDF of the whole module: (told no, don't want multiple versions of modules) Maybe put the video in a Storyline block? We'll test this but I'm not very familiar with Storyline and accessibility and am wondering if anyone has any experience using it for this situation? Other ideas???? Thank you!Before-After: Accessibility Makeovers in E-Learning #466
E-Learning Accessibility Makeovers #466: Challenge | Recap Pop quiz: What do you think is the most asked question by course designers in our weekly trainings? Okay, other than "Is this session being recorded?" If you guessed anything about accessibility, you're correct. Anytime we show a feature, demo, or example, one of the first questions is usually about how it meets accessibility guidelines. Ideally, accessibility should be considered right from the start of the course design process. However, many courses, examples, and demos were initially built with more focus on design and interaction than accessibility. That's okay because you can always return and ensure those older projects meet accessibility guidelines. And that's what this week's challenge is all about. 🏆 Challenge of the Week This week, your challenge is to share a before-after example that reworks a short project to make it more accessible. If you’re just getting started with accessibility, start with something simple like making text accessible with alt text or ensuring a color contrast ratio of 4.5:1. You can work on a single slide or multiple slides. If you don't have your own projects, you can use slides from the Content Library or our downloads hub. The goal is to practice making courses more accessible. Inspiration Check out last year's accessibility makeover challenge for examples: Accessibility Makeovers #417: Challenge | Recap 🧰 Resources Accessible Elearning in Articulate 360 Looking for more information on designing accessible e-learning? The following resources are chock full of practical tips for getting started with the accessible features in Storyline 360 and Rise 360. Webinars What is Accessible E-Learning? 5 Things You Need to Know About Accessibility How to Create Accessible Courses with Articulate 360 Articles For even more on accessibility in e-learning, you can find all our best content in this series: All About Accessibility User Guides Articulate 360 FAQs: Accessibility How to Test Storyline 360 Content with a Screenreader Storyline 360: How to Design an Accessible Course 🙌 Last Week’s Challenge: Before you get started on your accessibility makeovers, check out the creative ways your fellow course designers reworked classroom activities for e-learning: Converting Classroom Activities to E-Learning #465: Challenge | Recap 👋 New to the E-Learning Challenges? The weekly e-learning challenges are ongoing opportunities to learn, share, and build your e-learning portfolios. You can jump into any or all of the previous challenges anytime you want. I’ll update the recap posts to include your demos. Learn more about the challenges in this Q&A post and why and how to participate in this helpful article.Seeking Right-to-Left (RTL) Support in Rise 360 for Arabic Training Courses
Hello Articulate Community, I hope you're all doing well! I am relatively new to Rise 360 and truly impressed with its intuitive design and functionality. It has great potential to support our organization’s training needs. However, I’ve encountered a challenge that I hope the community can assist me with. We develop training programs predominantly in Arabic, which is a right-to-left (RTL) language. Unfortunately, I’ve learned that Rise 360 does not currently support RTL formatting out of the box. While the platform works wonderfully for left-to-right (LTR) languages, the lack of RTL support presents a significant limitation for designing Arabic courses that align with our organizational requirements. I’ve heard there are workarounds involving modifications to the CSS and index.html files in the published output, but I’m unsure where to begin. Specifically, I’d like to know: Has anyone successfully implemented RTL formatting in Rise 360 courses? What are the key steps or best practices for modifying CSS and index.html files to achieve a seamless RTL experience? Are there any potential challenges to watch out for when implementing this workaround? Our training programs are intended for large-scale educational organizations, so ensuring that the content is fully aligned to Arabic (RTL) standards is essential. If anyone has managed to create a polished RTL course using Rise 360, I’d greatly appreciate it if you could share your experience, tips, or even examples! Thank you so much for taking the time to help. I look forward to learning from the community’s insights and expertise.Screen reader main landmark inconsistent reading
I have a project that has an image as the first item in the focus order of almost every slide in the course. This is important because we need the alt text to be the first thing the screen reader announces on slide. When testing the scorm in different environments including scorm cloud, and using NVDA screen reader. The slide sometimes will announce "blank" "main landmark" or both before the alt text of the image. The issue is that this is not consistent, while reviewing the file some slides will say it, some will not. The same slide will provide different reads during different reviews or slide revisits. Sometimes it will read the alt text immediately, sometimes it will say "Blank main landmark", sometimes it will just say "main landmark". Is there a reason as to way the screen reader is announcing this, and if this is intended why is it not consistent?Accessibility: Font size in Storyline 360
Hi, I wonder if anyone in community or Articulate staff know why does Articulate guideline for accessibility state a 12 points minimum font size, when clearly the font size in Storyline is not true to size in comparison to web design, or designs in any Adobe tools. Here's the link to Articulate guidelines:https://access.articulate.com/support/article/Storyline-360-How-to-Design-an-Accessible-Course Screenshot of the content: I find that this is misleading. A 12 point font size on a 960x540 slide dimension in Storyline, looks way out of proportion. Especially also when W3C doesn't really specify a minimum font size in their official guidelines. Unless maybe there's something I don't know, or an unknown trick to make the font size is true to size in Storyline, please enlighten me! Thank you!New Matching lay-out
Last week we received the updated lay-out of the matching knowledge check. The moment I discovered it was a bit unlucky (during a presentation, got me a bit confused) but today I had some time to look into it. The changelog as following on the articulate website: Enhanced: Matching knowledge check blocks have been upgraded with intuitive navigation, full keyboard support, and comprehensive screen reader integration. Now, I think it's great that Articulate is improving it's software's accessibility, however, I don't see anything intuitive about the new design. A lot of new things have been added which for me only make the assignment more confusing. On the left side the hamburger icon and number suggest some sort of clickability, which is not there. The drop downs on the right give the assignment a new layer of intractability which only wouldn't want for the student. Overall the lay-out is a lot less clean and drains focus away from the content towards the design. Maybe a simple solution would be to add a slider which let's us choose between this lay-out and the previous one (or this one without the rings and bells). That's just my opinion, I was wondering what other think of the new lay-out!Storyline Player - accessibility and learner experience
Hey All! I'm putting out a query whether anyone has stayed away from using the Storyline player because it's "a lot" for the learner who uses assistive technologies to interact with the options on the player and then the content within the slide. Would it be a more accessible experience to have everything that requires the learner to interact with, within the slide (i.e., without the player)? Thoughts? I understand that the player has been updated for a more logical order of tabbing through the options. Yet what have people experienced ... good or bad? Much appreciated!
