Body

Resources for Digital Accessibility

Curated Learning Paths

Use these LinkedIn Learning learning paths to learn more about digital accessibility and creating inclusive digital materials.

Dare to be an a11y: Digital Accessibility Basics
A special THANK YOU to WCU for sharing their learning path with us! We have duplicated it in our own LinkedIn Learning portal.
This learning path details what digital accessibility is and how to use accessibility features in common applications.
Dare to be an a11y: Digital Accessibility Toolkit
This learning path dives deeper into how to make your materials accessible in common applications.
Dare to be an a11y: Inclusive Learning Design
This learning path is geared toward faculty and also includes info from the Toolkit path above.

Strategies for Remediation

Remediate for the Timeline

Digital content needs to be compliant with WCAG 2.1 Level AA by April 24, 2026. You can work on Spring materials students will need on April 24 and beyond(Summer, then Fall), and then return to the previous content to remediate it.

Use the 4 R's: Review, Retire, Replace, or Remediate

You can prioritize preparing your existing materials using this strategy.

Step 1: Review

Review all your digital content to determine if it is in use, relevant, or necessary. For courses, a good time to do this is after copying your course from a previous semester. Determine whether the files, links, and other materials still meet your course objectives and whether you are using them. For websites, a good rule of thumb is to review heavily trafficked pages and content first. Do your pages, forms, or other digital content still provide meaningful, relevant information to its audience?

Step 2: Retire

If your content isn't relevant, or if you aren't using it, retire it. Remove it from the course or from your website.

For courses, if you have resources hidden in Brightspace Content that you are not using, remove them. Hidden items in Content don't need remediation if they stay hidden, but it is best practice to remove items you aren't using. Hidden items still generate Accessibility scores in YuJa Panorama and will affect the course score overall.

If you are no longer using links or materials, remove them. Remember they are still in your old course if you do need or decide to use them.

Step 3: Replace

For content that is staying, assess it for accessibility. If the content isn't accessible, determine if it can be replaced by an accessible version.

Can PDFs be replaced with links to digital versions of the same resource? Check our library resources or with your publisher to see if your material is available in a digital, accessible format that can be shared as a link rather than a document.
Can PDFs be converted to OCR or Word? An OCR format will allow the text in a scanned PDF to be readable by screen reader, and Word documents are readable by them as well.
Can you replace inaccessible materials with new accessible content, learning activities, or teaching strategies that meet the same learning objectives? Some activities may need to be changed to be accessible. For example, if students are brainstorming during class and handwriting mind maps, have them also generate alt text that can be added to the digital document with their handwritten notes.

Step 4: Remediate

For content that is staying but needs to stay in its current format, remediate for accessibility.

Use this Resource Guide to remediate content with our accessibility checklists and tips below.
Use YuJa Panorama in Brightspace Content or via its DocHub feature.
- Once a material is scanned, work through the Accessibility Report to apply the Fix Issue button on as many issues as you can. If you do need to take the source document out to an application to continue, then you will have done most of the work in Panorama which might save you time and effort.
- Use Panorama's OCR generation feature to replace scanned PDFs with OCR versions.
- Use Panorama's OCR generation feature to fix untagged PDFs.
Use Accessibility Check in native applications to work through accessibility issues in the source documents.