Section 508 compliance

    Date: 06/28/05 (WebDesign)    Keywords: css, asp, web

    I need some advice. My company is trying to become Section 508 compliant and I am the leader of such an aggressive move. There are several problems involved with this whole project and my experience with Section 508 compliance is limited (basing a lot of my knowledge on government contracting experience). I know some of the basics, but I need to give more solid proof and evidence that we need to completely revamp the website.

    The biggest (and strongest) argument I have is that our website is completely designed using frames and depends heavily on them. I have already created a CSS driven layout that will mimic the current layout, but we are having issues with the ASP coding for the website. It was very poorly developed and not option explicit, which makes moving to ASP.NET difficult on top of frames.

    My question for you all is if you have resources that I can read more about Section 508 Compliance. If you have tips as well, that would be VERY appreciated.

    X-posted Almost Anywhere.. Sorry if you are seeing this constantly.

    Source: http://www.livejournal.com/community/webdesign/915449.html

« Line height? || Just had to share »


antivirus | apache | asp | blogging | browser | bugtracking | cms | crm | css | database | ebay | ecommerce | google | hosting | html | java | jsp | linux | microsoft | mysql | offshore | offshoring | oscommerce | php | postgresql | programming | rss | security | seo | shopping | software | spam | spyware | sql | technology | templates | tracker | virus | web | xml | yahoo | home