Hello,

I am using DNN Evoq Content 8.5. I have over two dozen portals that I manage using the DNN CMS. Since we fall under Section 508 compliance guidelines, we need to ensure all parts of our portals are compliant and accessible.

We are using the SortSite tool to test our portals against these guidelines. I have noticed that we are encountering SEVERAL issues where the native CMS controls, such as the search and 'Admin', are not meeting compliance. We have done our best to correct any issues on the skins and custom modules, but many of our errors are now happening on the DNN CMS controls itself.

What is DNN's approach to ensure their CMS meets accessibility guidelines? We would love to meet WCAG 2.0 guidelines, if possible, but we're solely focusing on Section 508 right now.

If anyone would like more info about what errors I'm encountering, please let me know so you can better respond to this question. I have over 77+ errors on any given website, many of them repeating issues that certain DNN controls are not compliant.

Thanks!

I wanted to provide some follow-up on this topic since we've touched base with DNN support regarding compliance issues.

The support technician indicated DNN Evoq Content Version 9.1+ meets accessibility guidelines. We are currently running Version 8.5 and I will be upgrading our development server to Version 9.1 in a week's time to determine if it meets our organization's compliance guidelines for accessibility.

In order to meet these guidelines, our organization is bound to AT LEAST meet WCAG 2.0 Level AA requirements as well as those items found under Section 508 Refresh. We use a tool called SortSite to check our websites when logged onto our DNN websites. The most common errors we have found in Version 8.5 was the fact that many of the control bar elements needed 'ALT' or more descriptive information to meet compliance standards.

Additionally, I have found that the CKEditor rolled out with Version 8. In Version 8.5, it is using CKEditor Version 4.5.3 (the latest is Version 4.7). They have a new tool called the 'Accessibility Checker', which we be beneficial for our organization to use with our content editors. I'm hoping DNN will adopt this in its future releases as the tool looks promising.

CKEditor Accessibility Tool Info: http://docs.ckeditor.com/#!/guide/dev_accessibility_checker