- http://msdn.microsoft.com/asp.net/reference/design/default.aspx is a very good resource for learning
- http://www.csszengarden.com/ is a good site to see how CSS makes it easier for developers to concentrate more on content rather than playing with tables etc.
- It's a pain to get cross-browser compatibility across browsers with complex designs
- Skinning is good in .NET 2.0. However, it's very painful to discover that you can't change the Skin Id after Init events. Changing skin is required in many cases after a particular event.
- Nested tables are a pain. Use Divs??? but Divs are not supported in all the browsers :(
Law behind accessible/ XHTML compatible sites:
- There are many good reasons for building accessible Web sites: financial, moral, legal, and so on. Let's concentrate, however, on the legal motivations. In the United States, any Web site developed by a federal agency is required by Section 508 of the Rehabilitation Act to be accessible to persons with disabilities. This law applies to federal agencies and companies that contract with federal agencies (see http://www.section508.gov).
- Other countries have similar requirements. For example, in Canada, the Treasury Board Common Look and Feel Standards require that Web sites developed by federal agencies be accessible. In Australia, the Disability Discrimination Act requires that all Web sites hosted on Australian servers (regardless of whether or not it is a government Web site) be accessible. (For more details on accessibility laws, see http://www.w3.org/WAI/Policy.)
No comments:
Post a Comment