Known Accessibility and Other Issues Found in Dubbot

Overview

This page lists known issues we have discovered while setting up the initial scanning of WSU sites in Dubbot. Rules can be set up in Dubbot to safely ignore them. If you have questions, please reach out to us.

NOTE: These issues are specific to the Dubbot scanning tool and do not apply to all sites unless specified.

False Broken Links – 403s

You get a 403 when loading a site that you do not have access to view. Some sites reply to scanning tools like Dubbot and Google with a 403 because the sites want to protect their content from getting scraped. e.g. X\Twitter, Facebook, Congress.gov, and others you may find all reply with a 403.

The 403 response shows up as a broken link to Dubbot because it cannot load the site. You can add rules in the Dubbot Tool to ignore 403s from these sites.

IMPORTANT:

• Do not tell Dubbot to ignore these errors until you verify the page do indeed load correctly when you view them. It is possible someone is linking to a private site.
• Related, never ignore all 403s as some could be valid errors. e.g. Your site accidentally links to a protected and\or internal site.

Example:

• RegEx example to hide 403 errors from TikTok:
• Go to the Manage Link Checks for your Site\Account.
• Add “https?:\/\/(www\.)?tiktok\.com\/(.*)” do not include the quotes.
• Check after the next scan that these error disappear.

NOTE:

If these happen on a few sites, you can add them yourself. If you see the errors across all or nearly all of your Accounts\Sites in your Agency, reach out to Dubbot to have them copy them to all of your Sites. That way you do not have to manually add them.

False Red Outlined Text Error

There are at least three pages that use CSS to create text with a WSU Red outline as pictured below:

This text gets flagged by Dubbot as a color contrast error when it is actually not an error. If you see this text flagged by Dubbot AND it shows something like the following, you can safely Ignore this error only on the page that it happens. NOTE: Again, you do not want to Ignore this error on all pages.