The accessibility scan checks the published content of every page on your website showing you all accessibility issues so you can address them quickly.
The accessibility checker checks accessibility compliance to WCAG 2.0 level A, AA, and AAA, and gives you source snippets of where problems occur. Obviously the automated checker cannot check some issues which require human investigation, but it can suggest areas that may need checking. Contensis will provide you with a platform to ensure that inaccessible content from a technical level will simply not be allowed to be published, if you so desire.
It is also worth ensuring that areas that cannot be checked with an automated checker are reviewed regularly.
Maintaining an accessible website really requires that accessibility be understood internally, and you must ensure content and design processes take accessibility into consideration. If you are not familiar with web accessibility the WAI (Web Accessibility Initiative) website is a good starting point.
Individual editors can check the spelling in their pages, but what if they forget? What if that last minute news article goes out unchecked?
When the QA module checks the site, it scans all the textual data for spelling, and keeps a record of all misspelt words.
If a word doesn't exist in the dictionary, you can add it to the global dictionary with a single click. Often product names and industry specific terms need to be added. Once a library of these is built up, the spell checking becomes a very effective part of the QA, as it will constantly scan for misspelt words, even on non-CMS content such as content that has come from, perhaps, internal databases or other systems.
As the global dictionary is used by the WYSIWYG editor too, time will be saved by users as more words are added, because, unlike in tools such as Word, the custom words are global; if one user adds a special term, it will appear correctly for all users.
Some organisations, such as local government, will be measured on HTML compliance. Even for those who don't have that obligation, HTML compliance is important for search engine optimisation and browser compatibility.
Contensis ensures that content published is fully standards-compliant, so you may ask why you need a checker? The checker is there to take care of situations that can occur with developers using custom code in templates and developers writing bespoke web controls.
The HTML compliance check will ensure that your site fully meets current standards guidelines.
There are a number of different ways in which links are managed in Contensis.
Links exist between objects in the CMS, such as links between pages. The CMS manages the content of both source and destination, so we know if the target updates at any point and we can then automatically update the link in the source.
An example of this may be when we delete a particular page. At the point of deletion the user will receive a message indicating that deleting the page will affect x-number of other pages that link to it. At this point the user can change their mind or continue with deletion anyway. When the page is deleted, the first action the CMS will undertake is to remove the link from all of the source pages, so that no broken links occur. When all these links are removed, the system will then delete the actual page in question from the relevant servers. Having prevented broken links and successfully deleted the page, the editors will be informed about the page deletion, so they have the chance to either point to a new page or remove the link altogether.
As you can see, a broken link in Contensis-managed content is near impossible. An area where broken links can occur is either in bespoke code that creates links automatically or in links to external non-managed resources. For this reason, the systems sweeps the entire site regularly for broken links. If there are any, the system will remove the links from the page and inform the relevant editors. The system will require internet access to check external links.
Tying these two forms of link management together will give you a system that makes it almost impossible to have broken links.
When the QA module scans a page it will check the entire size of the page including all images, CSS and other web resources.
You can define a maximum acceptable page size for your target audience. If a page goes over this size it will be flagged.
You could alternatively choose to order pages by size and check the largest ones.