localization
3 TopicsScreen reader reads translated content in original language
Hello! One of my Articulate Storyline courses was originally written in German, and I have duplicated and imported the XLIFF file to create an English version of the course. I just tested it with JAWS and the screen reader doesn't recognise it's in English! It reads it out like a German person who has never learnt English in their life. While hilarious, this is not the outcome I'm looking for! My whole system is in English by default, including JAWS. Therefore I assume that the duplicated German course still tells the screen reader the content is supposedly in German. Where do I change this setting in my project, please? ThanksSolved115Views0likes6CommentsFocus is moving away from the dialog box in language selection page
The focus should stay in the first dialogue box but instead the screen reader is reading the content in the background. This is an accessibility issue. After Localization and publishing the course, when we come to the language selection page, the screen reader is reading the content of the main page (Heading of the course and topics of the course) instead of the language selection box. I tested the issue again with Jaws on Edge browser. The issue is there with Jaws.51Views0likes4CommentsIs Localization Part of Accessibility? Let’s Talk
In my opinion, localization is accessibility. We create barriers when content isn't available in our learners' languages. It's that simple. Localization helps remove those barriers so more people can fully engage, learn, and succeed. Microsoft's story, Microsoft Powers World-Class Customer Support With Localization, is an excellent example of how localizing training can unlock access for thousands of learners worldwide while saving time and effort. I'd love to hear your thoughts. Do you think localization is part of accessibility? What takeaways do you have from Microsoft's approach? Share your reflections in the comments!38Views3likes0Comments