Search Close Search
Search Close Search
Page Menu

Siteimprove: Reviewing and Resolving Accessibility Issues

Wednesday, February 12, 2025
|

In this post, we will provide guidance on where to start reviewing accessibility issues, how to use SiteImprove to prioritize remediation, how to resolve any accessibility issues flagged by SiteImprove, and where the content editor is responsible for resolving certain types of issues.

  • Title II of the Americans with Disabilities Act requires state and local governments to make sure that their services, programs and activities are accessible to people with disabilities.
    • State and local governments must make sure that their web content meets WCAG 2.1, Level AA,
  • CMS website owners are responsible for the content on their websites meeting the WCAG 2.1, Level AA guidelines.
  • Anything not fully accessible should be made as accessible as possible, and time, cost, or knowledge constraints are not legitimate reasons to not do so.

Where to start: review accessibility issues

UMass Chan uses Siteimprove to track analytics for quality assurance, SEO and Accessiblity.

Please review the following links if you are unfamliiar with Siteimprove analytics or ADA and WCAG compliance:

Prioritizing: Siteimprove's accessibility report

Within Siteimprove's report, you will see column headings for Conformance, Difficulty, Responsibility, etc. We will review and explain these items below. Sorting on the table headings will help prioritize issues

Conformance

Our webpages need to be complaint for "A" and "AA". You can filter out "S" (best practices) and "Aria" for now. While "S" and "Aria" should be resolved, they do not need to be resolved for the April 24, 2026 deadline.

list of issues noted in Siteimprove

Difficulty

You can use this "Difficulty" column to prioritize the pages you need to resolve. For example, click the "difficulty" heading to change the sort order showing all "Beginner" items first.
Siteimprove issues list highlighting the Difficulty column

Responsibility

Siteimprove has tagged issues as "visual design," "content writing," "ux design," or "development." While reviewing issues on your pages, most tagged as "development" you can ignore; however there are a few that the content editor must resolve. In the Resolving issues section below, we identify the responsibility for each issue.

Siteimprove issues list highlighting the Responsibility column

As new issues appear or if there is confusion on how to resolve an issue, we will use the CMS Yammer channel to post solutions as well as update this blog post.

  • Visual design - Mixed
    content editor or developer (UMass Chan IT)
  • Content writing - Mixed
    mostly content editor, but in a few cases, this will be the developer
  • UX designs - Mixed
    mostly developer, but in a few cases, this will be content editors
  • Development - Mixed
    mostly developer, but in a few cases, this will be content editors

In the next section, we review each issue in detail, who is responsible and how to resolve each issue.

Request a review

If you are unsure if the issue listed is your responsibility, submit a ticket to IT and we can review how best to resolve.


Occurences and Pages columns

Alerts you to how many times this issue is noted within your site and how many pages need resolution. You may want to prioritize the pages that receive the most traffic.


Resolving issues

Conformance rating AA

Difficulty  Beginner 

Description

Headings should clearly describe the content they introduce. Siteimprove uses AI to review whether headings are descriptive. You can edit the review at any time if needed.

Responsibility

Content editor

Steps to resolve

This can be a tough one to resolve. The best way to think about a descriptive header, if this heading was taken out of context, what would it mean to the viewer? Or being blind and only hearing the header, is it informative enough to know what content will follow? As an added benefit, the more descriptive headers also help with SEO rankings and better search results within our own site searches.

Some examples of how to make a header more descrtive:

"Our Services"
Sighted viewers can easily identify what site they are on or quickly gather contextual clues around the page that "Our" may be referring to. Someone blind, or visually impaired may not see/hear those other clues, so out of context, what does "Our" refer to?

Instead of "Our Services," a suggestion might be "Services for Sibling Support" or "Service provided by the CANs program."

"FAQs"
A more descriptive header might be "Course help: Frequently asked questions" or "FAQs regarding the MST program." 

If you have updated a headline to what you believe to be truly as descriptive as it can be, you can mark this issue by marking the issue as reviewed.

  • In Siteimprove, when reviewing your page, along the left you will see "Note that this occurrence is based on a guided review."
    Note that this occurrence is based on a guided review with a pencil icon.

  • Click on the pencil icon and the area changes to display the question "Does this heading clearly describe the content it introduces?"
    • click the yes button if you truly believe this is the most descritive this heading will be
      Does this heading clearly describe the content it introduces?



Related links and resources