Hello,

My commission here with the State is going to start using DNN as it's Web site technology and I'm wanting to know if I buy a DNN skin what will I need to do to have users view the site on their mobile devices? Or do I just need to have modules created in WAP format?

Also how good are DNN skins about providing a text solution for the visually imparied? What would be a solution for accsessabilty?

Thanks for you help.

Laef

Hello,

If you are purchasing a skin from snowcovered you will have to be really careful that it is accessible, there are vendors that now make sure they are XHTML compliant, but that doesn't necessarily mean it is also accessible.

As long as it is coded cleanly and you also build the site cleanly with semantics in mind you should be ok.

A text solution, well as long as you have managed to semantically set up the site it should be ok, I did some research here:
Semantic Code and Header Tags in DotNetNuke Skins

If the structure of the skin is setup so that the content can be read in a logical order when it is set to text everything should be fine, you will need to have a think about how you will set your skin up to be just text.

The Web Developers Toolbar for Firefox has some useful functions such as: Information / View Document Outline for viewing the semantic structure of a page - you can also disable CSS and view the actual order of the text coming directly from the source code, I suspect this may reveal a few flaws in some skins.

As an example view this page:
http://www.dnncreative.com/DotNetNu...fault.aspx

Use the web developers toolbar and select css / disable styles / all styles

and you can view the source code structure of the text from the site

Having said this, if it is a CSS skin, you should be able to use CSS code to restructure the skin to strip out the graphics and display the text only, you will just need to work out how to use a skin switcher.

Hope this gives you some things to think about,

Thanks,

Regarding modules developed in WAP format: that is a choice for the developer, but it is only a choice and has nothing at all to do with the resulting module. You're modules will all be packaged as ZIP files for installation in DotNetNuke.