Closed Captioning
Hi I am adding closed captions to an e-learning for the first time... great function - very easy to use! However the text has a black outline which depending on the background and text colour makes reading the text really difficult (see example below) how do I get rid of the black outline??Articulate 360 - Troubles to import translated Xliff 2.0 with Matecat
Hello Everyone, I hope you're doing well ! I've been using Matecat for the translations of my courses and it was okay with the xliff 1.2, but the 2.0 seems to not work when I try to import it again in Articulate. There is an error message that indicates: "Completed with exceptions the attribute 'xmlns:matecat' is not supported on the Xliff Document element." Any ideas how to fix that ? Or should I redo the full translation with an xliff 1.2 ? Thanks in advance !Content on previous/next slides not displaying after interacting with layers
Description: I'm experiencing an issue in Articulate Storyline where slide content disappears after navigating using the Previous/Next buttons. On one of my slides, I use multiple layers that can be triggered either by hotspots on the Base Layer or through a custom timeline slider. When a user activates a layer (via hotspot or slider), and then uses the built-in Previous or Next buttons to move to a different slide, the content on those other slides doesn't display as expected. It appears blank or incomplete. This issue seems to occur after a layer has been shown, and it affects the rendering of other slides—even though no changes were made to them. Steps to reproduce: Navigate to the slide with multiple layers. Activate a layer using a hotspot or the timeline slider. Use the built-in "Next" or "Previous" button to navigate to another slide. Observe that the new slide doesn't show its content properly. What I’ve tried: Ensured that slide properties are set to "Reset to initial state" Verified that other slides do not use layers or custom states that could conflict Tried publishing and previewing—same result in both Any help resolving this would be appreciated. Thank you!Articulate Storyline - Can you swap images on base layer?
I have created multiple storyline simulations for our software product and invested a lot of time getting everything to work as intended (triggers, transitions, etc.). Like most software, it has recently undergone a User Interface update. So now the content needs to be updated to reflect the new UI. What I am trying to do is swap out the base layer for each slide in my project. The software UI looks different via colors and fonts, but functionality has remained the same (meaning hotspots won't move, callouts remain the same, etc.). is there a way to swap out only the "image" on a base layer so i don't have to recreate each project? If not, what is the best way to accomplish this. In my mind, in a project with 20 slides, it's 20 replacement images - avoiding the need to re-record and edit every single item on each slide. Thank you to anyone who can help. New user here and trying to find the most efficient way to do this.Labeled Graphic - Problem with Markers
Hello everyone, When I create a course with Rise 360, I like to use a labeled graphic. But when I look in the preview or later in my LMS, the markers become quite vivid. They start flickering randomly, see video. Does anyone know how to fix this problem? I am using a Macbook. Could it be that there is a problem with macOS? Many thanks in advance MarcReview 360: Invite Stakeholders to Review Content
After publishing or uploading an item to Review 360, you can use either a share link or review request to invite stakeholders to review the item and post their feedback. Learn about each process below. Use a Share Link Create a Review Request Use a Share Link To share your content and collect feedback, send stakeholders a direct link to your Review 360 item. From your dashboard, hover over an item, and click the More (...) icon that appears. Then, choose Share settings. Or select the checkbox in the upper-left corner of the card, and choose the chain link icon from the action toolbar on top. You can also open a Review 360 item from the dashboard and click Share in the upper right corner of the screen. Next, choose who can view your item using the Item Access dropdown. You can select Anyone with the link or Only invited users. The dialog box shows different options depending on your choice: Anyone with the link Only invited users Anyone with the link Select Anyone with the link from the dropdown to share your content more broadly. Then decide if you need these optional settings: If your reviewers don’t have Articulate accounts, select Allow users without Articulate IDs to comment. Stakeholders must enter their email addresses so you can identify their comments, and they can receive discussion notifications. We recommend encouraging stakeholders to sign in with an Articulate ID for the best experience. For example, reviewers who sign in can see badges for unread comments and change their email notification settings. Ask them to create a free account here. To password-protect your content for additional security, select the Set a password checkbox and enter a password in the field that appears. Turn off the password at any time simply by unchecking it. (Only the content owner and team folder editors can add and remove passwords.) Notes: Although share links are public, we prevent search engines from indexing our site so they won’t be searchable. However, if you post these links on a public web page, they may be indexed by a search engine. To protect confidential information, set a password or limit access to specific users. When you share Storyline project files with collaborators, they can access any integrated comments linked to the slides unless you password-protect the Review 360 item. Only invited users Choose Only invited users from the dropdown if you want more control over who can view the link. Invited users must have an Articulate ID to access the item you’re sharing. (If the stakeholder you want to invite doesn’t have an Articulate ID, ask them to create a free account here.) Then follow these steps to manage access: To add users, type in the person's email address in the People with Access field, then press Enter or select it from the drop-down list. Or copy a list of email addresses (use any form of separator—commas, semi-colons, spaces, cells in spreadsheets) and paste it to the People with Access field to add them automatically. You can add anyone from your team or outside the organization, as long as they have an Articulate ID. Remove users by clicking the X icon beside their name. Click Save to confirm any changes. Tips when making your item private: If your item is in a team folder, you'll see folder editors listed under "People with Access" with a folder icon beside their names. You can remove them via the folder share settings. Although you can add reviewers without Articulate IDs via request review, only those with accounts are included automatically. You'll see them under "People with Access" with a clipboard icon beside their names. Those without Articulate IDs must create a free account using the same reviewer email address to gain Viewer access. If you want collaborators to see integrated comments linked to slides in your Storyline project files, you must grant them access to the Review 360 item you want to share. Check out this FAQ for more information. Copy the shareable link from the dialog box and send it to your reviewers. Be sure to give them the password if you added one. And if your reviewers have never used Review 360 before, feel free to share this user guide or this downloadable PDF on reviewing content in Review 360. Create a Review Request To set a due date and keep track of your stakeholders' progress, create a review request by following the steps below. Launch the Review 360 item and click the Request Review button on the top right. Add reviewers by clicking the Assigned Reviewers fields and choosing any of the following methods: Select them from the drop-down list that appears by clicking the checkbox beside their names. The initial list shows the last five reviewers added, followed by the names or email addresses of recent reviewers you added and the members of your subscription. Type in the reviewer's email address and select it from the drop-down list. Copy a list of reviewer email addresses formatted with any kind of separator—commas, semi-colons, spaces, or cells in spreadsheets—and paste it into the Assigned Reviewers field to add them automatically. Enter a custom message for your reviewers if you like. For example, if your content is password-protected, include the password in your message. Make messages easier to read using the formatting options on the toolbar on top. Or, use the keyboard shortcuts below. Icon Function Key(s) Window / macOS Bold Ctrl+B / Cmd+B Italic Ctrl+I / Cmd+I Strikethrough Ctrl+Shift+X / Cmd+Shift+X Hyperlink Ctrl+C / Cmd+C to copy the URL Ctrl+V / Cmd+V to hyperlink the selected text Ordered list Ctrl+Shift+8 / Cmd+Shift+8 Bullet list Ctrl+Shift+7 / Cmd+Shift+7 Clear formatting N/A Add a line break Shift+Enter or Control+Enter / Cmd+Enter Set a due date for sending email reminders to reviewers if they haven't completed their review. Reminders are sent the day before, on the due date, and the day after. Confirm all the details are correct, then click Send Request. The text on the request review button reflects the status of the request, which could be either of the following: Button Text Description Request Review You haven’t assigned any reviewers. In Review You have assigned reviewers who haven’t completed the review. Review Assigned to You Assigned reviewers see this text when they use their personalized URL or are signed in with their Articulate ID. More details in below. Review Complete All assigned reviewers have completed their review. All reviewers will receive an email notification with a personalized URL to launch the Review 360 item. Using this URL, they'll see a Review Assigned to You button on the top right. When they click the button, they’ll see details of the request, including the due date, a list of reviewers, and a Finish Review button to set their status to Review Complete. A Re-Open Review link appears at the bottom right once they’ve completed their review. If they need to reset their status, they can click the link and choose Re-Open when prompted. Note: If your Review 360 item share link is private, reviewers must have an Articulate ID to view it. Ask them to create a free account here if they don't have one. Update Your Request Modify your request after sending it. Change the Due Date Click the In Review button, select a new date from the due-date dropdown, and click Save. All reviewers will receive email notifications of the new due date. Their status doesn't change. Add Reviewers Invite more reviewers to look through your content. Click the In Review button and then the More (...) icon beside the Request Review header. Select Add Reviewers. Type in their email address and select it from the drop-down list. Click Update Reviewers when you're done. Note: To remove a reviewer, click the X beside their name and select Remove. Delete Delete the current round of review requests to start a new one. Click the In Review button and then the More (...) icon beside the Request Review header. Select Delete Request, and click Yes to confirm. Note that you can't undo this action. Monitor Status Track your stakeholders' progress. Refer to the table below for more details on each status: Status Description E-mailed The reviewer hasn't viewed the Review 360 item. Item Viewed The reviewer launched the Review 360 item or reopened their review. In Progress The reviewer posted their first comment. Completed The reviewer marked the review request as complete. Tips: If your reviewers are new to Review 360, point them to this user guide for stakeholders or share this quick-start guide document (PDF) in your custom message. All seatholders can create or edit a request for any Review 360 item within the subscription. Only the request owner will be notified when reviewers set their status to complete. If a reviewer has an Articulate ID account linked to their email address, they must sign in with their password before posting a comment. Anyone viewing the Review 360 item using the public link can see the Request Review details. Assigned reviewers with Articulate IDs will see the Your Review section using this link when signed in. Select Allow users without Articulate IDs to comment if you want assigned reviewers without Articulate IDs to post comments.Issue with Bold Italic Font not retaining on export in Storyline
Dear all ! I hope you're well. I'm currently working on a project in Articulate Storyline, and I've noticed that the bold italic formatting of my font does not remain after exporting the course (HTML5/SCORM). The text appears correctly inside the authoring tool, but once exported, the formatting seems to be lost. Inside the authoring tool : After the export : Could you please let me know why this is happening and if there's a way to ensure the bold italic style is preserved in the exported version? Thank you in advance for your help! Best regards,Gsap Mouse Down animation
Hello everyone, I am currently working on a little game where the character used must walk, so I've been trying to use GSAP to make it work, the interaction is simple: While the button is pressed, the character moves to the left, it already worked when is a simple click on the button, it moved a certain distance in a certain amount of time, now I want it to move while the button is pressed. Here is the code... let object1 = document.querySelector("[data-model-id='6ZrZMfnavnW']"); let button = document.querySelector("[data-model-id='6fhUtThupA']"); button.addEventListener("mousedown", ()=>{ gsap.to(object1, { x: "20", ease: power1.inOut }); }); If anyone could help, I would be very grateful, and it could be useful for somebody else another time.Aria-hidden
Since the last update a new warning shows in the console. Blocked aria-hidden on an element because its descendant retained focus. The focus must not be hidden from assistive technology users. Avoid using aria-hidden on a focused element or its ancestor. Consider using the inert attribute instead, which will also prevent focus. For more details, see the aria-hidden section of the WAI-ARIA specification at https://w3c.github.io/aria/#aria-hidden. Allthough it doesnot prevent anything from working i always get wary from these kind of messages as they often a warning for something changing in the near future. So please Articulate devs... do check if and where aria-hidden is used and if that might give issues in the near future.
