Hi, We are currently in the early phases of a project to make our local government sites responsive. What is the best practice for including #Skip to Content links in responsive skins.
I know html 5 has structural elements but some of our customers will still be using older screen readers so we need to accomodate all.
I ask this question because many of the commercial responsive skins I have looked at do not seem to have #skip to content so wondered if this Accessability tool has been superseded or not considered much in the race to responsive designs.

I haven't ran DNN through the various compliance scanners recently, but as a lot of output is rendered via your skin/containers and modules, typically this is what is of most concern. DNN was made xhtml compliant back in late 4.x (and 5.0), so typically it is not a problem to meet ADA508/WCAG 1 etc. As to your question, I also am not using to seeing page fragment (#) operators in responsive skins, primarily as some of them will become invalid as some content will disappear depending on the viewport/media queries etc. I believe there are some "hacks" such as http://stackoverflow.com/questions/14... , and I know some people prefer to use DNN's mobile support instead as it allows for different pages and therefore you can specify details such as page fragments without fear (http://www.dnnsoftware.com/videos has various videos of interest). BTW in case you don't know, DNN 7.2.0 ships with the built in gravity skin being a bootstrap 2 responsive skin.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

I'm UK based and in my experience the UK (and EU in general) takes this a lot more seriously than the US and other parts of the world. However they generally look for WCAG A or/and xhtml as they're primarily concerned about screen readers reading content and sites being organised so they can be used by impaired users (e.g. no javascript hovers), rather than items such as page fragments (which is an oddity as it's not in HTML - it's a browser extension as the part after the # is seen as user generated content so typically not read by screenreaders).

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US