ANY DNN DEVELOPERS OUT THERE READING THIS THREAD???

I also would like to know if any progress has been made towards making DNN ADA 508 compliant. I have been scanning my University's DNN site and am seeing non compliant (XHTML) being generated, 508 breaks, 508 warnings and just some sloppy code output from DNN. We are running 4.5.x  We absolutely have to comply with the Texas Administrative Code (TAC) and use ADA 508 testing tools along with manual checking to ensure compliance. It is difficult to get past the non standards based code generation to get to the TRUE ADA issues.

I have serious reservations about:

• The DNN output of standards based compliant web code
• The modules/controls provided which put the information in the database; after all if garbage in then garbage out
• "skins" provided by other affiliated entities with the DNN Corporation
• The forthcoming of the DNN corporation with a statement as to their compliance stance; I don't see any hard and fast statements other than "we're looking into it" and I don't see any published action plans

One more issue:

If DNN is "billed" as a simple, easy, turn-key tool, then it should provide (in a turn-key fashion) what is expected by today's standards which include ACCESSIBILITY and standards-based compliant code generation.

Not an update, but here's what I know.  DNN is Sec 508 compliant.  That's because it's not DNN, but rather the skin and modules you choose that make it non-compliant.  It's also a factor of your content.  Frankly, most of the Sec 508 violations I receive are from missing ALT tags problems in forms.  These can all be fixed rather easily.

Jeff