Content Checks

Overview

You can check new and revised assets for spelling errors, invalid internal or external links, and accessibility issues with Cascade CMS's built-in content checks.

To run these checks, ensure they're enabled for your site and select Check Content & Submit when creating or submitting an asset for changes.

Tip - You can enforce content checks for users by disabling the Bypass Accessibility, Link, and Spell Checks when submitting content changes ability in their Site Role.

Spell Check

The Spell Check checks and reports all words (in asset content and metadata) that are not found in the system dictionary.

Depending on your role abilities, you have the following options for handling each misspelled word:

  • Add - Add the word to the system dictionary.
  • Ignore - Disregard the word.
  • Fix - Enter your own correction or choose from a list of suggested replacements.
Note - Only users with the Modify Dictionary ability enabled in their System Role can add words to the system dictionary.

Link Check

The Link Check ensures that all links between assets in the system and links to external resources are valid. The Broken Link column lists the URL of the broken link, and the Link Text column lists the text wrapped for hyperlinks or the tag name for other types of links. You can click the question mark icon (  ) to the left of each link for more information on why the link is considered invalid.

You have two options for handling each broken link:

  • Ignore - Disregard the link.
  • Fix - Enter a corrected URL in a text box (for external links) or choose an asset within Cascade CMS via an asset chooser (for internal links).

Scheme-relative Link Checking

External links that do not include a protocol, such as "//google.com" rather than "http://google.com" or "https://google.com" are called scheme-relative links. On the live site, they will navigate the website visitor to the same protocol as the page they are on. Cascade CMS follows a slightly different checking routine for such links as it cannot predict which protocol the visitor is going to view the page on. It verifies the link works with any of the two protocols and reports the link as broken only if the connection fails for both of these protocols.

Accessibility Check

The Accessibility content check ensures WYSIWYG content complies with the following accessibility guidelines:

  • Image (img) tags must have alternate text describing the graphic. (Section 508 / WCAG 2.0)
  • Table captions should not be empty. (HTML5 recommendation.)

For each issue found, you have the following options:

  • View Non-Compliant Content - View the specific HTML markup flagged during the check.
  • Ignore - Disregard the issue.
  • Fix - Enter a value for the missing or flagged content. For example: alternate text for an image or caption for a table.

WCAG 2.0 Content Check  

Cascade Cloud users have the option to enable additional checks for WCAG 2.0 violations. When this check is enabled, these issues will be listed under Advanced WCAG Issues.

Advanced WCAG issues can't be corrected during the content check itself; so to correct these issues, click the save icon (  ) to return to your draft and edit the content directly. Click Inspect (  ) to view more information about the issue:

  • Recommendation - Advice for how to correct the issue.
  • Content in Violation - The specific HTML markup flagged during the check.
  • Description of Issue - A detailed summary of the issue.
  • Standards Violated - The specific accessibility standards and guidelines associated with the issue.

Enabling Content Checks

At the System Level

  1. Click the system menu button (  ) > Administration > Preferences > Content.
  2. Under General > Content Checks select one or more options.
  3. Click Submit.

At the Site Level

  1. Navigate to Manage Site > Site Settings.
  2. In the Properties tab, select one or more options under Content Checks.
  3. Alternatively, select Inherit from system preferences to enable the content checks selected in your system preferences.
  4. Click Submit.
Note - (For Cascade Cloud Only) - In order to include WCAG 2.0 issues in the Accessibility content check, you must enable accessibility checking under Administration > Accessibility Checking. See Enabling the WCAG 2.0 Accessibility Check for more details.