The Learning Designers Incorporated

Once every couple of weeks, I explain to localization project managers that: ▪ a publication (SCORM or WEB, it doesn't matter) is not the source file of a course, ▪ PDFs from the course are not inside the .story file, ▪ and a one-minute video weighing 1 gigabyte is just a bit too much for any course. Hello class, let's talk about localization today. I’m sure this topic will be surprising for many of you, since I usually write about animation or interactivity in e-learning. But here we are! I have worked in localization for almost 20 years. And for half of this time, I have been regularly working on course localization. I want to say that preparing content for translation from any course is one of the simplest and most meditative tasks in the world of e-learning creation. It's easy, and it's beautiful, especially if you love a systematic approach and following instructions. Preparing content for translation is exactly a system and a set of steps where you can completely switch off your mind. For anyone interested, I've shown it in an infographic. Let me briefly explain how this process works. A .story file is a box containing text (on slides, in notes, alternative text, subtitles), images, audio, and video. Outside this box, there can be additional materials, and when converting this box into a SCORM or WEB package, the storyline through the links loads all additional materials into the package (in SCORM or WEB, but not in the .story). Your task is to extract all the text from the box and external files: ▪ some of the text can be extracted by Storyline itself, ▪ some can be extracted using external text recognition services (from graphics or audio), ▪ and some can only be provided by the client. That's it. The end. The main task here is not to miss anything and extract every letter, down to the last comma. Do you know the project manager's worst nightmare in localization? Finding out the day before the project is due that something didn't make it into the translation. The PDF with the guide is available for download in the store (it’s free). https://lnkd.in/dCgF-brh #localization #elearning

W3C WAI encourages you to review the updated Draft W3C Group Note:     Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)     https://lnkd.in/g6J875A4 We expect this document will impact future ICT standards worldwide. This is the planned last draft before we publish it as a W3C Group Note. Overview: WCAG2ICT provides guidance on applying WCAG 2 to non-web documents and software. This draft includes guidance for WCAG 2.0, 2.1, and 2.2 success criteria and glossary terms. For an introduction to WCAG2ICT, see:    WCAG2ICT Overview    https://lnkd.in/gA_mfbTY For review: We would particularly like your comments on: * Guidance for new and changed WCAG 2.2 success criteria and glossary definitions listed in the Comparison with the 2013 WCAG2ICT Note section * Updates to the Comments on Closed Functionality and Appendix A: Success Criteria Problematic for Closed Functionality sections * Sections with Editor’s notes that pose specific questions or request specific input Comments: To comment, please open a new issue in the WCAG2ICT GitHub repository:       https://lnkd.in/gj6unYMh Create separate GitHub issues for each topic, rather than commenting on multiple topics in a single issue. If it's not feasible for you to use GitHub, send comments in e-mail to: public-wcag2ict-comments@w3.org Please put your comments in the body of the message, not as an attachment. Start your e-mail subject line with: [Public Comment] Please send comments by 6 August 2024. If you need more time, please request an extension by sending an e-mail to public-wcag2ict-comments@w3.org Thank you in advance for your review.