May 2022

May 2022

Audio/Video – Manual transcoding option to optimize video files

Depending on the file format of audio and video files, they might not play in a web browser by default. Previously, all uploaded audio and video files were transcoded; now, transcoding only occurs when necessary, All MP3 and MP4 video files are saved in their original form because they can play in a browser without transcoding. Other files, such as WMV and AVI, which would not play by default, continue to be automatically transcoded.

With this update, the new Optimize for Streaming option in the editing tool enables users who want to manually transcode original versions of the files, for example, to reduce the file size or enable multi-bitrate streaming.

Note: This feature applies to uploading audio and video files in Content, Lessons, and Video Note upload. Original versions of videos are used for editing and playback. This feature does not apply to Video Note web cam recordings, which continue to be transcoded automatically.

This change also moves the Language selector to the Table of Contents and Closed Captions area.

In your Video Topic properties, access the Edit > Advanced Editing option.
Figure: In your Video Topic properties, access the Edit > Advanced Editing option.

The Video Editing tool showing the new Optimize for Streaming button, and the Language selector in the Table of Contents and Closed Captioning area.
Figure: The Video Editing tool showing the new Optimize for Streaming button, and the Language selector in the Table of Contents and Closed Captioning area.

This feature has accessibility impacts, including:

  • WCAG 2.1 Success Criteria 1.2.1 Audio-only or Video-only (Prerecorded)
  • WCAG 2.1 Success Criteria 1.2.5 Audio Description (Prerecorded)

Brightspace Learning Environment – Updated default font and color stylings for improved accessibility

This feature introduces a color change to fonts and icons in Brightspace Learning Environment to meet WCAG guidelines.

Previously the dark grey font #494c4e did not meet the 3:1 contrast ratio with the color of our links. The new font #202122 (still grey!) is darker and meets the WCAG link contrast criteria for accessibility. This change is visible in most locations in Brightspace Learning Environment.

  Before and after showing the updated font color visible in the My Courses widget
Figure: Before and after showing the updated font color visible in the My Courses widget. 

  Before and after showing the updated font color visible in text and inline links.
Figure: Before and after showing the updated font color visible in text and inline links. 

This feature has accessibility impacts, including:  

  • WCAG 2.1 Success Criterion 1.4.1 Use of Color
  • WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum)

This feature implements a new and improved context link menu in Brightspace Editor. The new menu has the same functionality as before – enabling users to highlight text and create a link, edit the link, remove the link, and preview the link – but now also enables support for the previewing of quicklinks that contain replace strings while editing their HTML. The new formatting context menu continues to allow users to highlight text within the editor and apply formatting or create links.

Previously, when a user created a new quicklink within the editor that contains a replace string, this proved not replaceable by the context menu. Clicking to preview the link resulted in a 404 Error.

The layout of the new Content link menu.
Figure: The layout of the new Content link menu.

The layout of the previous Content link menu.
Figure: The layout of the old Content link menu.

The layout of the new formatting context menu.
Figure: The layout of the new formatting context menu.

The layout of the old formatting context menu.
Figure: The layout of the old formatting context menu.

Manage Files – Improved error message when invalid files are uploaded

Building on the features added in November, this feature adds an improved error message to the File Upload dialogue. When a user attempts to upload a file containing one or more illegal characters in the file name, this message explains to the user the reason why the upload failed.

Previously, users received a generic “Oops! Your file could not be uploaded” message, which did not explain the reason the file upload failed.

The File Upload dialogue with the new error message displayed.
Figure: The File Upload dialogue with the new error message displayed.

Manage Files – Shared Files renamed to Public Files

To better secure files by making users aware of the availability of files in the Shared Files area, this feature renames Shared Files to Public Files. In addition, when files are uploaded to the Public Files area, a warning message is displayed indicating that the files are publicly available.

To avoid breaking any links referencing already-existing files with this change, the file path within Shared Files has not been renamed with this feature update. Permission language terms are updated but the internal permission name is not. The effect of this will be that Roles and Permissions exports will remain functional if they were exported prior to the name change.

The renamed Public Files area with the warning message indicating the public status of uploaded files displayed.
Figure: The renamed Public Files area with the warning message indicating the public status of uploaded files displayed.

SCORM – Improved completion messaging to avoid confusion in SCORM embedded experience

Upon completion of SCORM content a “This activity is complete” message displays. This change has been implemented to avoid confusion in the SCORM embedded experience as the old message was only relevant to content rendered in a pop-up window and did not account for other SCORM experiences.

Previously, the SCORM player would display the message: “The content has exited successfully, you may now close this window”.

This feature has accessibility impacts, including:

  • WCAG 2.1 Success Criterion 3.2.4 Consistent Identification

SCORM – Legacy SCORM Player no longer renders advanced HTML elements within the SCORM player sidebar

In the Legacy SCORM Player sidebar, advanced HTML elements including iFrames, Images, CSS, and actions such as mouseovers now render as plain text.

Previously, when using Legacy SCORM (Manage Files Based SCORM) some advanced HTML content was not properly rendered. The values could include any type of text or HTML which could result in broken image icons or unexpected behavior. Elements such as plain text and enumeration continue to function as expected.

This change affects the sidebar titles displayed within a sequenced SCORM package.


 Sidebar visible in sequenced SCORM packages.
Figure: Sidebar visible in sequenced SCORM packages.

Examples of functional vs non-functional sidebar information include the following: 
Functional Examples: 

  • Bold text: <strong>Table of Contents<strong/>
  • Font style and size: <p><font face=”Arial Black” size=”6″>TEST 101&nbsp; Table of Contents</font></p>
  • Enumeration Titles:
    • SidebarModuleFormatString  {Enumeration}{URLStart}{ModuleShortTitle}{URLEnd}
    • SidebarTopicFormatString {Enumeration}{URLStart}{TopicShortTitle}{URLEnd}

Example of enumeration titles is a SCORM sidebar.
Figure: Example of enumeration titles is a SCORM sidebar.

Non-functional Examples: 

  • <IMG src=\content\Strategic_Thinking\images\puzzle_title.gif>

Previously, a broken image link would display. Now the topic name displays as the plain text link.

  • <b style=”text-decoration: none;” onMouseOut=”style.backgroundColor=”#fff”;” style.textDecoration=”none”;” onMouseOver=”style.backgroundColor=”#ff0”;”>{URLStart}{TopicShortTitle}{URLEnd}</b>

Previously, the mouseover would display some features. Now, the topic name displays as the plain text title.

  • <style type=”text/css”>@import url(“/content/enforced/1111-Sandbox/css/table_of_contents.css”);</style>{ModuleLongTitle}

The name displays as the plain text <style type=”text/css”>@import url(“/content/enforced/6933-Sandbox_ Username/css/table_of_contents.css”);</style>{ModuleLongTitle}.

This update only impacts SCORM packages uploaded to the legacy SCORM player.

Related Articles