The Accessibility Checker ensures the pages compliance with the Web Accessibility Initiative (WAI) Guidelines.
- Is content created with Cascade Server accessible?
Content created via Cascade Server is automatically checked for 508 compliance (for persons with disabilities), and relevant W3C standards are adhered to.
The WCMS enforces the objective items for levels 1 and 2 compliance. This includes ALT attributes for images and summary attributes for tables. Certain initiatives are subjective, and human intervention is required.
Introduction to Accessibility Checker
The Accessibility Checker is typically turned on or off, system-wide, by an administrator. Depending on a user's permissions, the checker may be turned on or off at the page level as well.
When turned on, the Accessibility Checker, much like the spell checker and the link checker, is invoked after a page edit is committed by clicking the Submit button. If there are any elements that the CMS deems suspect, the user is forwarded to an Accessibility Checker page listing the errors sorted by the field on the page in which they occur.
The Checker will report on common errors such as <table> elements without summary attributes as well as <img> tags without alt attributes.
- Does Cascade Server validate content?
Published content is validated to ensure it is in compliance with XHTML XML, and CSS specifications set by the organization. This ensures cross-browser support for published content.
Notification is given any time invalid code (XML, XSL, HTML, etc.) is submitted. The user is required to correct the error before saving changes to an asset.
Turning the Accessibility Checker On & Off Globally
Accessibility checking can be turned on and off globally (system-wide) by an admin user. This can be done by going to System Menu > Preferences > Content.
Under the section "Default Data Checks," check the "Content Accessibility" checkbox to enable or uncheck to disable. Then press "Submit" at the bottom of the page to save the changes.