Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Accessibility - DNN 3.3 / 4.1Accessibility - DNN 3.3 / 4.1
Previous
 
Next
New Post
5/10/2006 11:30 AM
 

I have read several posts regarding accessibility issues with DNN. As I am still learning about the issue myself, I found some of them very informative and i saw some of them ending up in arguments.....constructive or otherwise.

Therefore, my simple and humble question to the good DNN Core Team / Development Community would be........Is the default installation of DNN 3.3 / 4.1 without any custom skins and modules W3C / ADA / DDA compliant??? If not, are there any plans for development in this area for future releases??

Many Thanks
Arif 

 
New Post
5/17/2006 11:02 AM
 
I'm almost positive the answer to all of those is, no, DNN is not 100% compliant. We are working on it, tho. If you notice a problem, let us know by posting an issue in Gemini. We don't always notice when there's a problem, so your support is greatly appreciated.

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com
 
New Post
5/17/2006 12:18 PM
 
This is likely to become more of an issue, this case is the most recent one that highlights the potential dangers facing site owners who don't or won't or can't comply
 
New Post
5/17/2006 12:36 PM
 
Yes, we have just had an Accessibility Consultant come in and go through our product (non-DNN) - really scary how far you can go with it. It was very high level but you have to consider that some browsers don't have JScript (rendered out app useless) and might be read through screen readers like Jaws (where each table row needs to be named etc.)

One site that they used as a good example of an accessibily website was www.bbc.co.uk - they have really gone far in making it accessible. Bear in mind that this was with our non-public facing webapp - we could not even dictate the minimum requirements in this area... scary...

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
New Post
5/18/2006 12:06 PM
 

Thanks for your replies.

I know accessibility and compliant HTML are different issues but I have read interviews from Tim O' Brien on Lee Syke's website where they claim that if the document definition is changed to XHTML and some changes are made in default.aspx with minor changes in ascx controls for modules, the website completely validates to W3C standards.

Ofcourse he has used just text/html module on his site. Those changes would need to be spread over all the other ascx controls for the modules. But still, that would be the first step for an accessible website.......completely valid HTML.

Is there any reason why is this process not implemented in the default installation of dotnetnuke??

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Accessibility - DNN 3.3 / 4.1Accessibility - DNN 3.3 / 4.1


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out