Page check reviews your page for spelling, link, World Wide Web Consortium (W3C) validation and accessibility errors. Page check reviews the preview of your page, that is, how the page looks inside Omni CMS without include files. Page check reviews reusable content on the page and performs the same checks as final check.
- Navigate to Content > Pages, click the More Actions menu , click Review > Page Check.
- When viewing a checked-out page, click the More Actions menu in the page actions toolbar.
- From the "Page Check" box select the following:
- File Type: Select an item from the dropdown.
- Some pages create more than one item when published, for example, both a web page (HTML) and a PDF file.
- Run All: Click to run all available checks (Spelling, Links, W3C Valid, and Accessibility).
- Spell Check Language: Select a language for the spell check.
- Spelling: Click to check the spelling of the page.
- Links: Click to check for broken links on the page.
- Levels 9 and 10 users can Make Exception to allow pages in the account to publish without fixing the link.
- W3C Valid: Click to check for valid HTML and XHTML code on the page.
- Accessibility: Click to check that the page conforms to accessibility standards.
- File Type: Select an item from the dropdown.
- When the check is complete, click "Show Results" to see a detailed breakdown of the problems.
- Click Done.
Administrators can configure page check options (including accessibility guidelines) in account settings. They can also set page check at the site and user level.
SpellingLink to this section
The "Spell Check Results" box lists misspelled words on the page and how many times they occur. Right-click on the word, click "+Add to Dictionary," and spell check no longer counts it as misspelled. Depending on restrictions set by your Administrator, you may not have the ability to add words to the dictionary.
Spell check scans words in the editable page content, the source code, and image descriptions. Words may display correctly but be marked as misspelled due to tags in the code. For example, writing
folde<span>r</span> will appear as "folder" in the page text, but spell check will register "folde" as a misspelled word.
LinksLink to this section
The "Link Check Results" box shows every link on the page, whether it works or not. It lists the URL, the status of the link on both the staging and production servers, and a status code (if applicable). Levels 9 and 10 users can Make Exception to allow pages in the account to publish without fixing the link.
|Staging, Production||The link is valid. (Link is Valid (202), all other 200 statuses)|
|Staging||The link is broken on the page in staging.|
|Production||The link is broken and points to a file that has been moved or some other miscellaneous issue. (Moved Permanently (301), Found (302), all other 300 statuses)|
|Production||The link is broken and points to a nonexistent destination. (Not found (404), all other 400 or 500 statuses)|
|Production||Link check is unable to verify if it's a valid link or not; often occurs with mailto links. (Cannot check link, all 100 statuses)|
W3C ValidLink to this section
Most web pages are written using markup languages such as HTML and XHTML. The W3C develops standards for the use of these languages. The W3C check in Omni CMS makes sure that your page obeys these standards.
As you edit content, the What You See Is What You Get (WYSIWYG) editor translates your changes into valid code. However, it may miss some items. A W3C error doesn't always prevent a page from displaying on your website, but can cause inconsistencies in how the page looks in different web browsers.
The "W3C Validation Results" box shows errors and warnings along with a location in the source code and a description of the cause.
AccessibilityLink to this section
Accessibility check looks for issues in the page as defined by accessibility standards such as Section 508 and Web Content Accessibility Guidelines (WCAG). It identifies three types of problems (known, likely, and potential):
- Known problems have been verified as broken or creating an error.
- Likely problems need to be reviewed by a user to determine if it's actually a problem or not.
- Potential problems are either code that may cause errors or possible errors that cannot be automatically checked and require human review.
In the accessibility check results, each problem is listed with the location of the error in the source code, the name of the issue, an excerpt of the offending code, and a suggested repair.
Level 10 administrators can add exceptions to the accessibility check by clicking the "Make Exception" button next to an identified problem. Exceptions are still noted by the system but don't prevent page publish, if the page needs to pass page check to be published. When adding an exception from page check results, that exception is made for every page in the site.
Accessibility check settings and exceptions can be managed from the account settings.