Small width layout Medium width layout Maximum width layout Small text Medium text Large text
     Search
Downloads Downloads Directory Directory Forums Forums Forge Forge Blogs Blogs        Marketplace Marketplace Careers Program Careers
Community › Forums Register  |  

AspDotNetStoreFront
  Need Help?  
Professional technical support for DotNetNuke is available from DotNetNuke Corporation.
 


  Ads  
Active Modules -- Active Forums for DotNetNuke
 


  Sponsors  

Meet Our Sponsors

AspDotNetStoreFront - E-Commerce by Design - The Leading ASP.NET shopping cart platform for developers!
Click here to go to dev.live.com for Windows Live developer resources
SteadyRain
DataSprings - Great Ideas. Always Flowing.
R2integrated - formerly bi4ce
Jango Studios - Skins, Modules and Hosting for DotNetNuke
 


DotNetNuke Forums
 
  Forum  DotNetNuke® Pro...  Links Module [L...  Accessiblity Compliance Issues
Previous Previous
 
Next Next
New Post 5/6/2008 10:27 AM
User is offline LeAnne Raphael
2 posts
www.santacruzinhomecare.org
10th Ranked


Accessiblity Compliance Issues 

I am running the Adammer ADA Compliant skin on my sites to fill any State and Federal mandates.  In validating one of the external sites I came across issues causing a fail.  Adammer gave me the following information.

2) Error: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified

This is caused by the poorly written Links module. The code should read <|td nowrap="nowrap"|> not <|td nowrap|>. The skin cannot change poorly written module code. Either way nowrap is depreciated and should be accomplished with a CSS style attribute like style="white-space:nowrap;". We recommend that you use the HTML/Text module instead of the Links module. 

Having my users edit/add links through the html/text module rather then the links module is not in the game plan.  I can see information being deleted etc...  Can this be corrected?  Or does anyone know of a third party links module which would pass validation?  Thanks. 
 

 
New Post 6/6/2008 5:37 AM
User is offline Niels-Jørgen Hvidberg
18 posts
newcomtech.dk
10th Ranked


Re: Accessiblity Compliance Issues 

Hi LeAnne and the Link team

I use xhtml a lot and there are now under 50 errors which are not generated by skins or containers. DotNetNuke is going in the right direction.

Here is a fast and simple workaround for the above error from the link module. The Link team can do this a lot smarter, i'm sure.

In the \DesktopModules\Links\Links.ascx file, change the following line:

<td <%# NoWrap %>>

to:

<td style=" white-space: <%# NoWrap %>;">

From now on you will only have css warnings if you have choosen 'Wrap' in the Links Settings (It gives "whitespace: ;" in the html code) which is better than errors :-)

 

 
New Post 6/6/2008 6:16 AM
User is offline ErikVB
2827 posts
www.apollo-software.nl
5th Ranked










Re: Accessiblity Compliance Issues 

version 4.0.0 of the module will solve this (version has been submitted to the release tracker).

also: DNN 5.0 will be almost completely xhtml compliant


Erik van Ballegoij,
a view from my attic, my personal blog

DNN OpenForce 2008... Register Now!
 
New Post 6/12/2008 8:09 AM
User is offline Tim Polack
11 posts
10th Ranked


Re: Accessiblity Compliance Issues 

Eric - We have not been able to find many resources on getting DNN compliant - we're using ver. 4.8.3.  do you know of any good resources?  We've are editing a decent amount of the core coding to attempt to make the existing version compliant.

Tim

 
New Post 6/12/2008 9:07 AM
User is offline ErikVB
2827 posts
www.apollo-software.nl
5th Ranked










Re: Accessiblity Compliance Issues 

one of the things you could do is to check out the DNN 5.0 roadmap, and see what issues have been fixed that have to do with Compliancy: http://support.dotnetnuke.com/project/RoadMap.aspx?PROJID=2

I would very much like to discourage you to make changes to the core, as you will loose all those changes with an upgrade (eg. dnn 4.8.4 was just released, with a few security fixes....)

One of the things i did before was to use a third party http handler that could fix dnn output before it was send to the client. Check out Snapsis Pageblaster, that has a functionality to make the output xhtml compliant...


Erik van Ballegoij,
a view from my attic, my personal blog

DNN OpenForce 2008... Register Now!
 
Previous Previous
 
Next Next
  Forum  DotNetNuke® Pro...  Links Module [L...  Accessiblity Compliance Issues
 


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, 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 DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.

 


FREE Skins, Modules & Control Panel!
Choose how much you want to pay on our Skins, Modules, Containers and Control Panel - Starting from FREE!
www.dnngroup.com
Disgrafic
Diseño y creación de portales web dinámicos :: Desarrollo de módulos personalizados :: Soluciones a medida :: Imagen Corporativa :: Tu proveedor DNN en España
www.disgrafic.com
DM Analytics, LLC
DM Analytics, LLC provides software solutions that facilitate rapid development of independent or dependent datamarts and their associated web-based reporting.
www.dmanalytics.com

DotNetNuke Corporation   Terms Of Use  Privacy Statement
DotNetNuke®, DNN®, and the DotNetNuke logo are trademarks of DotNetNuke Corporation
Hosted by MaximumASP