udoit threw over 1600 errors on my course. need a quick way to fix this

[SeanKim]

I checked my course with the udoit accessibility checker, and it threw well over 1600 errors, many of them dealing with extremely trivial things like using "colors for emphasis" and recommended fix being bolding or italicizing the words. 

I can't be the only one dealing with this. Is there a patch, or some kind of batch fix for this? Or is there a setting I can use to change or ignore all errors of this type, or change the app to ignore it automatically? Or perhaps set it to make the changes automatically? (bold it, italicize it etc)

[chriscas]

Hi @SeanKim,

We have a UDOIT (which is an open-source, 3rd party tool) installation in our Canvas too, but unfortunately I'm probably not an expert in it.  With that being said, I don't know of an "auto-fix" option, but when you first launch a new course scan, you could uncheck the "suggestions" option un the "Scan for" section, which hopefully will reduce the amount of issues.

You could also uncheck individual error types to hide them from the total:

With that being said, if accessibility is an area of focus at your school/institution, you may be expected to actually fix all of the issues.  While auto-fix definitely sounds like a great idea, on the tech side it could really get to be a nightmare to account for all of the different possibilities and fixes for those possibilities.  Also, if something went awry with an auto-fix and content got completely erased or changed in an unacceptable way, there would really be no recovery.

-Chris

[SeanKim]

Ok, I don't see that option dialogue box. It just has scan now and full rescan 

[chriscas]

Hi @SeanKim,

I can see you're using the CidiLabs version of UDOIT, which has some modifications to the original source and may also be newer than what we have.  I'd recommend asking your local Canvas team (usually in the eLearning / IT / Digital Education areas) if they have any advice for you on this similar to what I shared for the open-source UDOIT we run.

-Chris

[SeanKim]

I decided to edit the entire course for the html tags specifying the styles and colors using notepad++ and find in files functionality in it. It basically removes all instances of the html tag in all of the files as long as you include the entire tags

[Chris_Hofer]

@SeanKim ...

Are you possibly using a newer version of UDOIT?  I know that schools can get UDOIT through Cidi Labs (which is what your screenshot shows), so I wonder if your school went that direction?  I'm not sure what @chriscas has for his UDOIT version, but it looks similar to what I used to use as a former Canvas admin in higher education.  Screenshots on Cidi Labs' website look similar to what you've posted in your reply:

UDOIT Cloud Accessibility Tool | Cidi Labs

[SeanKim]

Yes we're using the cidilab version and the admin at the school probably decided not to include the options for the users to prevent confusion or problems down the road. 

I edited the entire course files for the html style and color tags and removed them entirely and that seems to have fixed the errors for now. But now I have only black texts on all my pages.