DubBot Web Governance Reports

Web Governance Reports help identify content that may require additional review based on organizational standards, policies and content best practices.

Unlike Accessibility Reports and Broken Links Reports, Web Governance Reports are not primarily focused on technical errors. Instead, they help website managers monitor content quality, review potentially problematic content and identify patterns that may not align with established standards.

DubBot includes both built-in governance checks and the ability to create custom policies that can identify specific content across an entire website.

Understanding Web Governance Reports

Web Governance Reports are organized into two primary categories:

Flagged Words

Flagged Words identify words or phrases that DubBot recommends reviewing.

Being flagged does not necessarily mean content is incorrect or must be changed. Instead, flagged words serve as a reminder to review the content and determine whether it is appropriate in context.

For example, a flagged word might appear perfectly acceptable in one situation and require revision in another.

Policies

Policies allow DubBot to search for specific patterns, phrases or content standards.

Some policies are provided by DubBot, while others can be customized to support organization-specific needs.

Policies can be useful for:

  • Finding outdated terminology
  • Monitoring content standards
  • Identifying accessibility-related content patterns
  • Locating specific words or phrases across an entire website
  • Supporting branding and governance efforts

Custom Policies

One of the most powerful features of Web Governance Reports is the ability to create custom policies.

During Tulane's DubBot implementation, custom policies were used to identify specific content patterns across Tulane websites.

If you have a recurring content issue that you'd like to monitor across your website, contact the UCM Web Team. We can help determine whether a custom policy may be appropriate for your needs.

Common Examples

Examples of issues commonly identified in Web Governance Reports include:

  • Flagged words requiring editorial review
  • Generic link text such as "Learn More" or "Read More"
  • Content patterns identified through custom policies
  • Institution-specific terminology and standards

DubBot provides detailed explanations for each issue and highlights the relevant content directly within the page report.

DubBot Documentation

Video Tutorial

Review the DubBot Web Governance Reports video tutorial.

This transcript has been lightly edited for readability and accuracy. It contains the spoken content from the Web Governance Reports video and is provided as an alternative format for users who prefer reading the material instead of watching the recording.

DubBot Web Governance Reports Video Transcript

Welcome back to the DubBot Training Series. In this video, we'll explore Web Governance Reports.

Unlike Accessibility or Broken Links Reports, Web Governance Reports help identify content quality, brand consistency and policy-related issues. They can help you find items that may not be strict accessibility errors but are still important to review.

Web Governance Reports include Flagged Words.

DubBot maintains a library of words and phrases that may warrant review. Being flagged does not necessarily mean the content is wrong. It simply means DubBot would like you to take a closer look.

In this example, the word "dummy" is highlighted.

In this context, the term is being used to describe a dummy social media profile. Whether this requires action depends on the context, but the report helps ensure potentially questionable items receive additional review.

Just like other DubBot Reports, Element Location and Element Source help identify exactly where the flagged content appears.

The second major category within Web Governance is Policies.

Policies allow DubBot to look for specific patterns, words, phrases or content standards.

Some policies are provided by DubBot, and others can be customized to meet organizational needs.

During our original DubBot rollout, we created policies to identify specific content patterns across Tulane websites.

If you have something you would like to monitor across your site, contact the UCM Web Team. We can work with you to determine whether a custom policy would be helpful.

This example checks for links that use "Learn More" as the link text.

Link text should describe where the link takes a user. Using generic text like "Learn More" or "Read More" may not provide enough context, particularly for screen reader users.

Here, DubBot highlights the Learn More button and explains why it was flagged. It also provides guidance about the issue and displays the underlying source code associated with the link.

If you decide the content should be updated, you can use View in Drupal to open the page and make corrections.

After making changes, Refresh Content retrieves a new copy of the page from the live website.

Analyze reruns tests against the content already stored in DubBot.

For policy-related changes, Analyze is often the tool you will use most frequently.

That concludes our overview of Web Governance Reports in DubBot.

Remember the key takeaways from this session. Review flagged words in context. Use policies to identify content standards. Use Element Location and Element Source to understand issues. And remember that custom policies can help find specific content across your website.

Thanks for watching, and I'll see you in the next video where we'll explore Best Practices Reports.