508 remediation of Storyline course

Hello ContractsManage​ . I tried, but it seems that it is not possible to resize an object to a fixed size (e.g., 24x24) so easily. You have to use the “scale” function, taking into account the original dimensions of the element to achieve a fixed result (24x24). For example, if one icon is 50x50 and another (almost identical) is 52x52. But there is an additional problem that I have not been able to overcome: resizing causes a shift that must be configured in order to reposition the icon in the right place (for example, at the top right). This becomes very complicated (for me), and I therefore think that my solution is not simple at all, and therefore unusable in your case. 

For 508 remediation in Storyline, the challenges you’re facing are common, especially with large courses. Here’s the best approach to streamline your work:

1. Use Slide Masters and Layouts:
   • Instead of editing each slide individually, apply changes to the Slide Master or custom slide layouts.
   • For example, if your “X” close icons appear on a consistent layer or in the same position across slides, you can place a master icon on the Slide Master, assign it the correct alt text, and set the size to 24x24. This way, every slide using that layout inherits the change.
2. Rename Slide Titles at the Layout Level:
   • Slide titles are important for accessibility. Use the layout names and adjust the title text boxes in the master to apply consistent, descriptive titles across multiple slides.
3. Global Styles for Fonts & Colors:
   • Storyline doesn’t automatically update all fonts across every slide unless you’re using Themes. Check your Theme Fonts and Theme Colors to ensure accessible fonts and color contrast are applied universally.
   • Once a theme is updated, new slides will automatically follow these styles. Existing slides may need minor adjustments.
4. Consistency Across Layers:
   • For objects that appear in multiple layers (like pop-ups), create reusable objects by copying them from a master slide or using templates. Assign alt text and formatting once, then reuse rather than recreating each time.
5. Accessibility Checker:
   • Run it frequently as you fix issues. Focus on high-impact errors first (slide titles, alt text, font size, contrast).
6. Consider Breaking Up Large Projects:
   • Splitting 652 slides into scenes, as you’ve done, is smart. It makes the project easier to manage and prevents Storyline from slowing down.

💡 Pro tip: If a certain icon or button appears on every slide, using the Slide Master or layout-level object is the most efficient method. Individual slides should only be edited if they have unique content or variations.

This method will save you hours of repetitive work and keep your 508 remediation consistent across the course.

Hello ContractsManage​ . Your post deserves to stay at the top of the list for as long as possible to get answers and gather useful tips.
We all struggle with these kinds of problems.
I don't have a magic formula. 
Regarding your X icon that needs to be enlarged: if it needed to be shrunk, there would be a trick. But I don't know of a way to change the size of 508 elements on 508 different slides, even if they are all identical and only appear once in the Media Library. I don't think it's possible... (see below).

However, using the Media Library, you can find your X icon element in the list, write alternative text, AND CLICK on “Apply to All” (apply the text to all occurrences of this media). This way, with a single click, all your X icons will share the same alt text. BUT not all icons will become accessible if they are not already. You have to do it slide by slide...

Now, for resizing, I thought that an alternative solution might work with JScode. I'll look into it. Since all X icons (now) share the same alt text, they can all be targeted by code that would resize them (height and width) and reposition them on the slide (roughly at the top right, adjustable in the code) at the beginning of the slide. These are simple things that code can easily do, in theory. I'll get back to you when (if) I get a result.

This morning, ChatGPT failed miserably at writing this simple code. If anyone feels up to the task, please give it a try. For my part, I'm going to find a small piece of code that does the job (moving an element, for example) and continue discussing it with ChatGPT.