Publish Screen Requirements | CMS Knowledge Base

The Publish screen ensures pages meet spelling, link, and accessibility standards before going live. Review all required checks carefully to ensure compliance and prevent publishing errors.

Spelling

The Spell Check Results box lists misspelled words on the page and how many times they occur. If you need to add a word to the dictionary, please email webcommunications@nsuok.edu to request a word to add into 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. If you suspect this as an issue and are not comfortable checking the code, please do not hesitate to contact webcommunications@nsuok.edu.

Links

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).

Link check will automatically ignore links beginning with "tel:" or "mailto:".

Icon	Column	Meaning
	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)

Accessibility

Accessibility check looks for issues in the page as defined by accessibility standards such as Section 508 and Web Content Accessibility Guidelines (WCAG). It can identify up to four types of issues:

• Critical issues block content for people with disabilities and will definitely prevent them from accessing fundamental features or content.
• Serious issues will partially prevent people with disabilities from accessing fundamental features or content.
• Moderate issues for people with disabilities will not prevent them from accessing fundamental features or content.
• Minor issues are considered to be an annoyance for people with disabilities.

The Accessibility Check Results shows the cause of the issue, location of the issue in the source code, suggested repair(s), and a description of the repair needed.

This automated accessibility check scans page content that is visible to the website visitor once it's published. Content that is hidden from a visitor or assistive technology will not be automatically analyzed for accessibility rule violations.

So any view that is offscreen—such as dialogs, modals, pop-ups, accordions, or tab regions—cannot be automated for accessibility. Please check these elements manually for accessibility conformance.

You must:

• Repair all known problems
• Resolve as many potential problems as possible
• Reach out for assistance if needed

Our goal is to exceed accessibility expectations. Please utilize our Digital Accessibilities Resources to help obtain compliance.

Schedule

Pages may be scheduled to publish at a specific date and time. This feature should be used carefully, as it controls when content becomes publicly available.

Scheduling is taught in Intermediate Training. Do not schedule pages unless you have completed Intermediate Training or received guidance from the Web Communications team.

Include Unpublished Dependencies

If you uploaded a new image, document, or file while editing your page, that file must also be published.

When publishing a page, you may see an option to Include Unpublished Dependencies. This ensures that any new images or documents linked to the page are published along with it.

If dependencies are not published:

• Images may not appear
• Documents may not open
• Links may appear broken

Always review the dependency list before publishing and confirm that newly uploaded files are included.

Version Description

Every time you publish a page, OmniCMS saves a version of that page.

This allows you to:

• See what changes were made
• Compare previous versions
• Restore an earlier version if needed

Versions act as a safety net in case content needs to be corrected or rolled back.

When publishing, you must enter a clear Version Description.

A good version description:

• Explains what was changed
• Includes the term or semester when applicable
• Makes it easy to locate previous updates

Examples:

• Fall 2026 Commencement Update
• Spring 2027 Tuition and Fees Revision
• Updated Staff Directory

Clear version descriptions make it easier to find last year’s content, restore older versions, and track the page history.