Turkish captions not displaying properly.
Hi, team. I'm currently converting some English modules into Turkish, and most of the captions are not displaying correctly: The correct characters are there in the source file (first screenshot), but when published onto the LMS, some characters are omitted (second screenshot). Is there a way to fix this?Jaws Multiple choice question not pausing for periods when sentences are ending with a number.
Jaws Multiple choice question not reading/pausing for periods when sentences are ending with a number. If my first sentence end with "1." Next sentence, Jaws will not pause for the period. If my first sentence end with "1a." (or any letter), Next sentence, Jaws will pause for the period and read the next sentence. Temporary solution: Added a space before the period to fix this.Dark mode for Storyline 360
Hi there Just wondering if there is a way now (or will be...) in SL360 settings to have the build tool adjustable to a dark grey background and tool bars like in the MS Office suite and Adobe CC programs. I jump from those with a nice dark grey to Storyline 360 and it's bright white window is a bit of a jolt on the eyes... Cheers SimonAI Audio + Pronunciation + Correct Closed Captions
I'm having an issue with the new AI Audio feature in Storyline, as it relates to pronunciation and generating CCs. In the past, using Text-to-Speech, I often needed the voice to pronounce something differently than how the word appeared. I'd generate and insert the voiceover with "Generate Closed Captions" checked: "Welcome to Brivo." Then I'd go back into that voiceover, change the words to phonetic spelling according to how I needed them pronounced, uncheck "Generate Closed Captions," and insert: "Welcome to Breevo." This would result in correct CCs and correct pronunciation. The audio would state "Welcome to Breevo" while the CCs would read "Welcome to Brivo." I'm unable to duplicate this workflow using AI Audio. When I uncheck "generate CCs," it simply does not insert any CCs at all. I'm left having to waste so much time generating and re-generating audio in hopes that it randomly pronounces all my words correctly. Has anyone figured out a workaround for this issue? Am I just not using the tool correctly?New Storyline Accessibility bug
Hello There seems to be a brand new bug since the October 22 update. When a button that was previously disabled is changed to normal, the screen reader and keyboard still pick it up as disabled - it reads as 'button unavailable' and is ignored by the tab and cannot be selected by the keyboard. However, the state shows as normal with the hover state working properly and it can be clicked with a mouse. This seems to happen in specific circumstances - The trigger to change the button from disabled to normal is "When the timeline starts on this slide" and the button has an entrance animation. Normally I would just ditch the entrance animations but it worked fine before the October 22 update when we accessibility tested it, the course including animations has been signed off by our client and entrance animations are blinging anyway. Here is an example module. The current version was published using todays November update and the slightly older version was published using the October 8 update to Storyline. I would also rather not roll back Storyline to republish as there are a whole bunch of recent bug fixes that I need. https://360.articulate.com/review/content/c5e0d117-32d3-4a2b-b91b-f5e4504765a3/reviewDialogue accessibility
Hi! Just wondering if this is expected behaviour. When a dialogue is displayed and then closed again, the screen reader: Reads the label of the dialog after the dialog is closed (or it says 'dialogue' if there is no label) Once it gets to the end of the focus order, reads the most recently visited dialogue label (or 'dialogue' if no label) again. It seems to focus on the whole slide when it does this. It happens before it gets to the player controls. Bonus weird thing/bug: If you activate NVDA then click with your mouse on elements (including ones that are hidden from accessibility), when you go back to keyboard control, the elements you clicked on also get added to the end of the focus order before the player controls. https://360.articulate.com/review/content/985a380f-0762-4823-b2f1-62f0f3ba2bac/reviewHow to play audio files by hovering over text
Hi all, For all you Javascript gurus out there... I am trying to create a storyline file that caters for accessibility and in this case plays a unique audio file every time you either hover over or click a piece of text on the screen and then stops when you hover or click on another line of text. For example, if you had 2 headings on the screen saying "Section One" and "Section Two", the respective audio will play for these. Now, I went on Microsoft co-pilot and asked it the following:- "Write a javacript function in Articulate Storyline where if you click on a some text, it plays an audio file, let's say that this is called sound1.mp3 but if you click on another piece of text, sound2.mp3 plays and sound1.mp3 stops." It actually wrote some javascript and gave me instructions how to implement it within Storyline. So... I went ahead and done this, tested it and found out that for some reason it is not working! I have looked at the javascript and for the life of me, I cannot see why this cannot work! I have attached the source file if anyone would like to take a quick look! Thanks in advance
