Useful Tools and Resources
Hi everyone, I'd like to share some accessibility (a11y) resources. I hope these will be helpful in making your content more inclusive and accessible to everyone. Whether you're new to accessibility or looking to deepen your understanding, these resources provide valuable insights, and best practices to ensure your work is accessible to all users, regardless of their abilities. Thanks. Understood: Understood is the leading nonprofit empowering the 70 million people with learning and thinking differences in the United States. https://www.understood.org/ Funkify: A disability simulator that helps you experience the web and interfaces through the eyes of extreme users. https://www.funkify.org/ Accessible Numbers: Presenting numbers and data clearly. https://accessiblenumbers.com/ Neurodiversity Design System: A set of standards and principles that combine neurodiversity and UX design for Learning Management Systems. https://neurodiversity.design/ WhoCanUse: A tool that brings attention and understanding to how colour contrast can affect people with different visual impairments. https://www.whocanuse.com/ Viz Palette: Colors in action. https://projects.susielu.com/viz-paletteCreating alt text for complex images easier
Hey folks, I'm really glad to see this new accessibility Group on E-Learning heroes. Right now in my own line of work, I'm pushing for really accessible courses and it's quite crazy how trainers are missing fundamental things such as alternative text on images. Which I would end up having to do to ensure a project gets done in time. Anyway, I made a video tutorial very recently on how you can speed up creating alternative text for graphics using Microsoft Copilot. It can also be done with other tools such as ChatGPT. I hope it helps and more importantly, gets more people to make sure that all their graphics have alternative descriptions. Enhancing Accessibility in Instructional Design with Microsoft CopilotIntroduction
Welcome to our Accessibility Group! We're excited to have you join this collaborative space, where you can find inspiration and connect with like-minded individuals. We're all human and learning on this accessibility journey. Use this group to ask questions, share ideas, support each other, and learn about the latest guidelines and laws. Together, we'll grow in accessibility maturity and create a supportive community through this safe and inclusive space.Accessibility: Frameworks, Prioritization, and Maturity
How Articulate uses a prioritization framework to drive accessibility maturity Thanks to everyone who joined us for this webinar with Deque. We had a great time, a great turnout, and some great questions. I wanted to share some resources with you: Webinar recording: How Articulate uses a prioritization framework to drive accessibility maturity Presentation slides Webinar takeaway - Accessibility Maturity: A Guide to Getting Started with Your Organizational Model In addition, I'm evaluating all the questions that came in, and I'll select the ones related to this topic that we did not discuss during the live Q&A. Let's continue the conversation right here in the comments! Original Post: Join Articulate for this free webinar with Deque on September 26, 2024. How Articulate Uses a Prioritization Framework to Drive Accessibility Maturity I'd love to hear about the processes your organization is using for accessibility maturity.Storyline custom focus control
There have many been times, when using Storyline to develop content, it has not been possible to get the kind of screen reader focus control that I have needed. Using layers for this can only get you so far. I developed a JavaScript function that allows you to send the screen reader focus to the text field that you want, via any trigger. Adding the following JavaScript to your projects Slide Master will make it available throughout your module: // Check if function has been defined already if (typeof window.setFocus === "undefined") { // Get reference to the Storyline Player var $player = GetPlayer(); // Set the amount of time to delay before attempting to send focus to the target element (milliseconds) 1000 = 1 second. var $interval = 100; // window.setFocus = function ($target) { // Get the target element, based on the passed argument var $target = document.querySelector('[data-acc-text^="' + $target + '"]'); var $id = "acc-" + $target.dataset.modelId $target = document.getElementById($id); // Send focus to target, after defined $interval setTimeout(function () { $target.focus(); }, $interval); } } Once the function is defined in your Slide Master, you can then call the function on the page using a JavaScript function, which can be triggered by any Storyline trigger such as timeline start, timeline end, button click etc. window.setFocus("Customer in the queue"); The argument, which is passed in the "" quotes, is the text contents of the text field you are targeting. You do not have to include all the text, just enough to ensure it is unique. For example, if you have two text fields: "Customer in the queue talking on their phone." "Customer in the shop staring into space." Passing the words "Customer in the" would not be specific enough, as there would be two text fields found. However, passing "Customer in the queue" would send the focus to the text field that contains the text "Customer in the queue talking on their phone."Accessibility Best Practices in eLearning
There are many ways that you can create an accessible eLearning course. Feel free to share any resources or knowledge that you have! I'll go first: Here are some resources from that describe what you can do to make sure that your content is accessible by people from all walks of life: All About Accessibility | Articulate - Community A Quick Reference Guide On eLearning Accessibility Standards (elearningindustry.com) eLearning Accessibility: Best Practices, Tips, And Tricks - eLearning IndustryGroup Guidelines
Please take a moment to familiarize yourself with our community guidelines. These guidelines ensure that we maintain a friendly and welcoming space, which allows a positive experience for everyone. Key points include: Be Respectful: Treat all members with kindness and respect. Stay On Topic: Keep discussions relevant to accessibility. Be Helpful: When providing feedback, be constructive and helpful. No Spam: Avoid posting spam or self-promotion. If you encounter any technical issues, please post them in theDiscuss Forum. Thank you for being a part of our community. Let’s work together to create a supportive and engaging environment for all.Tab Order and Text Boxes
Hello everyone, I am working on a project for a client who wants to ensure our module is screen reader compliant. A large concern for them is questions where the screen reader states the question, then the learner can tab to the options. Having audio autoplay the question was our original solutionbut it was not acceptable because of the conflicting audio with the screen reader. Because it is text, the screen reader will not read the question first when tabbing through. The user has to use up and down arrows, which makes it confusing when the screen reader jumps to the options first. When I make the question stem interactive, it adds a "button" to the end of the screen reader. Is there a way to make a text box tab-able directly without also having a "button" tagged on automatically?Accessibility and states
Hello! hoping someone can help or point me in the right direction. I have a colleague that has created text that changes depending on the state. How can the text box appear again in the focus order? For example: 'Button one' changes 'text box' state to 'hello'; 'button two' changes 'text box' state to 'goodbye'. I want the focus order to be Button one, text box, button two, text box. Is this possible for screen readers to hear both states?
