0
Followers
1
Following
8
Spaces
Profile menu
Profile picture of Christopher Philips
·
Visible also to unregistered users
## Canvas and Alt Text There are currently some significant challenges with Ally when adding alt text to images. This [Guide to Adding Alternative Descriptions for Canvas](https://usergroup.ally.ac/s/resources/?contentId=39538) goes over 5 different ways that alt text can be added to images and then 2 different ways that content can be copied forward. Depending on which method is used to add the alt text to Canvas combined with which method the content is copied/migrated determines whether the alt text carries forward. The Ally recommendation is to “Copy this Course” instead of using the “Import/Export” functionality, however - due to how our courses are setup, that isn’t an option for us and so each semester, all of our alt that that was added through the Canvas Files Tool or through the Ally Course Accessibility Report is gone - and the instructor would have to start again the next semester from scratch. My understanding is that this is because of a limitation from Canvas that does not allow alt text added by Ally to be stored by Canvas unless it is added directly through the rich text editor. I have not seen a similar guide for other LMS’s so I am assuming this is specific to Canvas - if so I would love to put pressure on Canvas to enable this to be able to work and would be grateful for some feedback from Ally on what would be needed to make that happen. I don’t have exact numbers, but before we knew about this limitation we have added alt text to thousands of images through Ally that ended up going to waste and not persisting forward with the course content was imported to the next semester. Ideally this could be fixed so that all of that work could be stored in Canvas, but if not - would it be possible to have a feature flag to turn off the ability for alt text to be added through the files tool or Ally Course Accessibility Report? Or at least a warning that the data entered will not be stored in Canvas - the way the tool is currently built does not give any warning that the work they are doing will not be stored, which I think is generally a safe assumption.