We've got a few new updates that are rolling out today that we wanted to call to your attention. Most of these updates are non-critical and do not require any immediate action on your part. Any actions required on your end will be noted in bold inline with the change information.

• Issue: the top and footer navigation tags sharing same ARIA role value ("navigation").
  Fix: we've added in aria-label attributes to distinguish the two from each other.  
  
  To obtain this fix: re-publish your navigation components (your main navigation and any subsite navigation) and your footer components.  This will publish out the minor changes in both the navigation and footer templates. 
  
  
• Issue:  Personnel lists were cutting off some of the entries when printing out the personnel list.
  Fix: We've added in some print CSS conditions to the personnel list LESS file to address this.
  
  To obtain this fix: republish your core.css files (and any subsite CSS page assemblies).
  
  
• Issue: When browsing a tabbed content page on PC computers using Chrome, occasionally the first tab listed on your page would have its name injected in the last breadcrumb navigation item.
  Fix: We've corrected the Javascript handling breadcrumb navigation generation to clear out re-used variables.
  
  To obtain this fix: republish your core.js file. 
  
  
• Issue: Page load and performance times.
  Fix: We're continually looking for ways to improve the page load and performance. We've made a few adjustments to different Javascript files — the core.js file (and all of its contents) are set to async, and the rest of the Javascript files have been set to defer.  The difference between async and defer is that async will execute as soon as its downloaded, and defer will execute in the order that it was downloaded. These changes resulted in an approximate 17% improvement to page downloads.  We will continue to make updates to consolidate Javascript files that relate and move more files to async instead of defer, since that will slightly decrease the loading time.
  
  To obtain this fix:  republish your core.js file and your footer file(s) — you are already doing this for changes noted above.

If you have questions about these or any changes that have been made, drop us a line or submit a help desk ticket.