Features Q&A: Canvas Deploy Notes (2025-06-18)

[InstContentTeam]

Looking to discuss these features from the 2025-06-18 Deploy Notes? Post a reply and start a conversation!

Updated Features

• Assignments: Improved Error Flow for Google File Integration [Added 2025-06-17]
• Discussions: Discussion Checkpoints Support Group Discussions
• New Quizzes: RIch Content Editor Media and Document Tools Disabled by Quiz Setting
• New Quizzes: Support of MathML equations in the Rich Content Editor

Other Updates

• Accessibility Updates: Enhanced Structural Clarity
• Accessibility Updates: Improved Error Feedback
• Accessibility Updates: Improved Visual Clarity and Semantic Structure
• Accessibility Updates: Streamlined Navigation and Keyboard Accessibility

ADD FEEDBACK FOR THESE FEATURES IN Q&A TOPIC

• This topic is for feature discussion only—Please share use cases, best practices, questions, clarifications, etc. regarding this feature.
• Please thread replies as possible to keep posts organized. This will help everyone to track discussions and to participate.

ADDITIONAL FEEDBACK—WHERE TO POST IDEA SUGGESTIONS AND SUBMIT BUG REPORTS

• Idea requests for the Product Team to consider should be submitted in ideas.canvaslms.com . This is the best way to ask for additional or alternative functionality than what is included in the release. Linking to the related idea here so others can find it is encouraged!
• Bug reports should be submitted to Canvas Support. This way, cases can be connected and uniform updates can be provided to those involved. Bugs will not be triaged in this thread

[theJBRU]

The blog post about accessibility updates is a step in the right direction. There is more information there than has been previously available about the updates being made. The information is still broad and vague, however, and appears to be inconsistent in some places. For example, it states that "Interactive elements performing page actions will be marked up with <button> tags." What exactly constitutes "page actions" is not defined. It also states that "Navigational elements will be correctly labeled using <a> tags." but later indicates that "All interactive elements—like “Next” and “Previous” buttons—will be fully operable using only a keyboard."

So are Next and Previous navigational items which will use <a> tags, or is navigating to the next or previous part of a module considered a "page action" and so these will be <button> elements?

Please expand on the work you started with the blog post and provide additional detail about specific parts of the user interface that are changing.

[TrinaAltman]

It's interesting to see that Discussion Checkpoints will be be available again for schools to enable without going through their CSM (From the Discussion Checkpoints Support Group Discussions item: "Additionally, admins can manage the Discussion Checkpoints feature option directly in their account settings. Previously, it was managed by the Customer Success Manager.").

I’m surprised that after all of the hullabaloo around Discussion Checkpoints when it was rolled out earlier this year, then the Feature Option was removed due to issues, that Discussion Checkpoints is being released overall back to schools in this way – as add-on verbiage within a different change (checkpoints being available in group discussions now). That said, my understanding is that even though the Feature Option will be unlocked, that will only apply to subaccount configuration. Instructors will not be able to enable/disable it in individual courses. Since it will be disabled by default, instructors won’t be able to use it until schools enable it at the account level (if they didn't already have it enabled). Again, that is just my understanding (and not something I can check on beta since we had it enabled there long ago).