Found this content helpful? Log in or sign up to leave a like!

Accessibility in Classic Quizzes vs New Quizzes

Jump to solution
sidedeirene
Community Member

Hello Instructure Community, 

My team came across this comparison chart for features in Classic Quizzes vs New Quizzes https://docs.google.com/document/d/11nSS2EP0UpSM6dcuEFnoF-hC6lyqWbE9JSHELNmfG2A/preview?tab=t.0#head...

Unfortunately, accessibility or accessibility features are not included in the document. 

Is there an updated version of this document that includes that, or could more details on the differences be provided to raise awareness? 

Best, 

Irene

Labels (1)
Canvas | Quizzes Feature Comparison Make informed decisions about your institution's quizzing solution with this feature comparison of Classic Quizzes and New Quizzes. For confirmed, or in-discovery items, development timelines are included, but are subject to change. Last Updated: March 2...
1 Solution
mtuten
Community Contributor

Good morning,

I do not have such a document nor do I think it would be easy to have such a document as a lot of work is still going into New Quizzes.

I have done a lot of testing of New Quizzes with a screen reader and have been reporting the problems I see to Instructure for further/future improvement.

I can say that New Quizzes has come a long way, accessibility wise. The only question type in New Quizzes that is completely inaccessible to screen reader and keyboard only users is the hotspot question type and Canvas does include a warning message in the editor when faculty attempt to use that question type.

Beyond this roadblock, there are still several speed bumps in the design of New Quizzes, but I'm hopeful that they will be straightened out over time.

Currently, these are my recommendations for building a most accessible New Quiz (aside from the design tips that apply to all RCE)
I don't think that many at my institution follow the part about informing the student on the number of answer options they have available and such but that is not an accessibility requirement either--it's a practice that at least one screen reader user has told me they find useful.

View solution in original post