Accessibility issues/flags, quarto html and reveal.js files

[jfieberg]

Description

I teach with the Canvas LMS. A lot of the content (slides, homework solutions, textbook) I share for my courses is created using quarto. I've started to check these files for accessibility issues using UDOIT for Canvas, and have found that documents created in this way result in an overwhelming number of flags. Two of the most prominent issues appear to be related to:

a) empty "a" tags associated with code chunks
b) pre elements associated with source code and R output

I'm curious if anyone knows of ways to create content to avoid these issues? I've done a lot of searching and found some useful sites with clues, e.g., this github issue tracks the empty "a" tag issue and this site tracks accessibility issues more generally. I have come to understand that pandoc includes an aria-hidden = "true" attribute so that screen readers can skip the empty "a" tags, but these will still be flagged when content is screened for accessibility (and therefore have to be dealt with within Canvas to pass required checks). I have not been able to find any discussion related to the latter issue.

Thanks for any help/pointers!

[cnoecker]

I currently have this same problem and would be eager to know if anyone has found a workaround. Thank you!