If you are using a current version of DNN, I believe that you'll find that the default website is compliant.

Of course, if you add modules and themes, you'll need to verify that each of these is compliant. For commercial modules and themes, you can ask their support teams for advice.

Then, as you add your own content, you'll need to use good practices to create compliant HTML.

Willem,

as Joe said. The most important thing is that the skin is compliant, and then every module used. And then you have to be aware that the content editors know how to create barrier-free content, so there are some pitfalls...

Happy DNNing!
Michael

Thanks for the answers... your right most of the issues are in the theme/skin... So there's no need to change the DNN core code?

I tried several DNN website with https://achecker.ca/checker/index.php but none of them past the test... and this is only WCAG 2.0 AA not even WCAG 2.1. AAA DNN Search is for all websites the biggest issue... can you show me how to fix the search issues?

There is NEVER a reason to change the DNN source code.

What is the search problem?

I recently checked some DNN sites and some show no errors, some show hundreds.
I just tried some with the DNN core search and no errors show up, so I don't know what issues you see?
As said it's 90% Theme related.

I validated this website (https://dnncommunity.org/) in https://achecker.ca/checker/index.php

I get this search error:

1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

Success Criteria 1.3.1 Info and Relationships (A)

Line 62, Column 9:

Check 213: input element, type of " maxlength="255" name="dnn$dnnSearch$txtSearch" size="20" text="" type="text" />

Repair: Add text to the input element's associated label that describes the purpose or function of the control. Error Line 62, Column 9:

 

I would first open an issue at https://github.com/dnnsoftware/Dnn.Platform. Doing so will help the team fix this issue permanently for everyone.

In the meantime, there are at least two choices.
1 See if you can modify the .ascx page of the search module to include a generic label.
2 Add the label(s) using javascript or jQuery.

Posted By Willem on 12 May 2020 08:52 AM

I validated this website (https://dnncommunity.org/) in https://achecker.ca/checker/index.php

I get this search error:

1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

Success Criteria 1.3.1 Info and Relationships (A)

Line 62, Column 9:

Check 213: input element, type of " maxlength="255" name="dnn$dnnSearch$txtSearch" size="20" text="" type="text" />

Repair: Add text to the input element's associated label that describes the purpose or function of the control. Error Line 62, Column 9:

 

 

That's a hidden element in this skin that's not in use, see:

https://github.com/DNNCom...ials/_header.ascx#L8

I use this definition and there are no errors reported:

< dnn:SEARCH runat="server" ID="dnnSEARCH" CssClass="ServerSkinWidget" ShowSite="False" ShowWeb="False" UseDropDownList="False" Submit='Search'  >

 

Our themes are all WCAG 2.1 AA compliant but we still have some issues because not all DNN modules from external vendors our fully compliant... We are mainly using DNNsharp, EasyDNN and DNNgo module...

I know the only way is to ask the vendors to fix the WCAG issues as soon as possible... how do you guys deal with this issues/situation?

In the netherlands all government websites should be WCAG 2.1 AA compliant by now...