What's New

Buzz Release Notes (2020-08-27; v3.0.189) - Accessibility updates

Ryan Richins
  • Agilix team member

A round-up of all improvements and changes to the Buzz platform in versions v3.0.189 available on August 27, 2020.

Accessibility updates

In this release, we made various accessibility updates, including:

  • Improved keyboard tabbing in the main toolbar, Course home, and Activity player screens.
  • Updated accessibility labels in the rich text editor and assessments.


  • Fixed an issue where the spacebar would not toggle a custom, boolean metadata field in the admin app.
  • Fixed an issue where pressing the TAB key while taking an assessment could sometimes navigate you to the Jump To toolbar.
  • Fixed some accessibility labels in the rich text editor and assessment player.
  • Resolved an issue where users would see a blank activity screen after editing User notes, trying to navigate away without saving, and choosing to stay on the screen.
  • Resolved an issue with clearing course agendas when switching from a course with an agenda to one without.
  • Resolved an error when viewing the Gradebook for a course with an empty grading table.
  • Resolved an issue with activity instructions not displaying when the activity had no content.
  • Fixed an issue with attempting to drop images onto the Create Task and Edit Journal Post screens in the student app.


Updates in version 2020.08.26.4851.

  • General system improvements.
  • Command Usage: Updated the concept document to clarify response codes and appropriate usage of the API. Note that “batch” requests are no longer recommended and will be limited in the future.
  • API Time Limiting: A new concept document for upcoming limiting to API requests. API Time Limiting is not currently enforced but will be in the future. This mechanism’s algorithm is similar to, but not quite the same as, the well-known leaky bucket algorithm. All developers using the Buzz API should prepare for the enforcement by updating their tools to review the HTTP response header to know how much more API can be consumed. A formal announcement will be made in the future as to when this will be enforced.

Have a question or feedback? Let us know over in Discussions!