Alt text and Pick-One interaction
Hello It seems that when you use images as options in the Pick One interaction in Storyline, the interaction automatically tags the images as radio buttons (good so far) but the alt text is read as if it is a separate object to the image/radio button when you use the arrow keys to move between them (not so good). Is there a way to attach alt text to the radio button? It seems to work properly if you use shapes rather than images but that isn't really an option for me. https://360.articulate.com/review/content/10a3ab95-5df6-440e-9931-0e7de955a38d/review This is using NVDA screen reader. Thanks!eLearning Alt Text Help
Hi! Can you help me with something? I've sent a similar message to a few of my instructional designer friends, but thought I'd post it here as well. I have a question regarding adding alt text to images in eLearnings and other mediums. I cannot seem to find a consistent answer. So, I’m hoping you can help me. I typically use Articulate Rise for our eLearnings and sometimes Articulate Storyline. I have added alt text to all of our eLearnings/trainings. But I have found a few resources that say how I've have my alt text is incorrect. I cannot seem to find a consistent answer and would prefer not to go back through all of our eLearn ings and update them to find out later the alt text is still incorrect. Here's what I've found: - Alt text for logos should read: alt="_____ Logo" where others say to just have it read: "_____ Logo", and others say it should read: _____ Logo without quotations. If the logo is added for decorative purposes only then you should leave the alt text blank. I've watched the alt text webinar available on E-Learning Heroes and it say: - For decorative images, alt text should be nulled out (e.g., alt="" or ""). The alt text should not be left blank. Which is the correct way to post alt text for logos? Also, should alt text read: alt="_______" or just "________" (with the description of the image in between the quotes)? This shouldn't be this confusing, but I cannot find a consistent rule about this. Thanks for your help! AnneWhat Are the Best Practices for Designing Accessible E-Learning Courses in Articulate 360?
I’m working on creating e-learning courses in Articulate 360 and want to make sure they are fully accessible to all learners. I’m curious about: What strategies or techniques do you use to make courses accessible? Are there specific tools, templates, or workflows in Articulate 360 that make accessibility easier? How do you balance accessibility requirements with interactivity and design quality? I’d love to hear about real-world examples or lessons learned from your own projects. Thanks in advance!Content access management for groups
Hello, i am just getting myself acqainted with this tool and had a few question which I hope you can clear. Assigning content to groups is fine, but is there a 'general content' section that I can create which, by default, can be accessed by all groups? Or am i supposed to create content and manually give access to all of my groups? Can we have certain compulsory and elective courses within groups, and also in the 'general content' section as previously mentioned? I understand that we can create rules in Storyline 360 by about users having to complete a set of compulsry scenes before accessing further scenes or content like quizzes etc. but I am seeking better clarity in this matter. What are all the ways available on this tool regarding reminders? I would like to explore all possibilities - whether it is about annual reminders, reminders to complete a course, due date reminders, reminders for compulsory courses but not the elective ones etc. It would be nice to have answer to this question asked by a member: Reach360 - Course Specific Learner Notification | Articulate - CommunityZoom image icon incorrect alt text
Hello All, We have an image with zoom enabled. While testing this with a screen reader, we observed that an incorrect label is used for the Zoom button. The screen reader reads it as “Zoom image” plus the image alt text. It should read only “Zoom image.” Regards, ShraddhaSCORM Resizing Issue on Android WebView
Hi All, I’m facing an issue with SCORM player sizing in the Totara Mobile App. I’ve attached two screenshots of the same SCORM video — one from an iOS device and one from an Android device. Both devices have nearly identical screen sizes. Issue: On iOS, the SCORM preview/player appears correctly sized and fully visible. On Android, the SCORM player appears very small, even though the device display size is the same. When I open the same SCORM package directly in Chrome on Android, the player appears correctly (same as iOS). → This suggests the issue may be related to how the Totara Android app’s WebView loads or scales the content. What I need help with: Is there any specific setting in Articulate Storyline that affects mobile SCORM scaling for Android vs iOS? Are there any Totara configuration settings that control SCORM iframe / WebView scaling in the mobile app? Or is this something that needs to be adjusted by the mobile app developers (e.g., CSS, viewport, WebView settings)? Any guidance on settings or fixes would be really appreciated. Thank you!PROCESS block is NOT Accessible
Hello all, We are developing Rise accessible courses. While using the PROCESS block, we found that it is not accessible, even though Articulate Rise states that it is accessible. The issues we are currently facing are: When using keyboard navigation (Tab/Shift+Tab), the focus skips the interactive navigation buttons below (1, 2, 3, etc.) and jumps directly to the next content. The reading order is incorrect. When the user presses the down arrow key, the focus moves to the bottom of the page, but the screen reader does not move focus to the start button or the slider content. Regards, ShraddhaSearch feature only highlights results which is not accessbile for all users
People who cannot see or distinguish certain colors, or who use devices that change colors on their display, may be unable to understand content's meaning. Our in-house accessibility team brought this issue to my attention. Is there a way to make the search results more accessible? Thank you! Gretchen Handy
