Dreamweaver8 handles "web standards"

Preface: This series of original articles consists of eight articles, starting with the popularity of Web Standards, and describes how to use Dreamweaver 8 to build a standard-compliant Web, because the original author's article is an excerpt from "Build Your Own Standards Compliant Website Using Dreamweaver 8" (This article is charged), I have properly deleted and modified the content, the order is the same as that of the original article, but the length will be adjusted. The translation level is limited. Please forgive me.

If you are reading this article, you may be interested in Web standards and use DW (Dreamweaver for short) it is very curious about the standard applications in the site.

You may have some knowledge about WS, but you do not know how to use DW to compile compatible code. Or you are a DW user, and you really want to follow WS, use CSS more extensively, and make more friendly documents. No matter which type you are, this article will give you the answer: tell you how to deal with WS with DW.

Web standard definition

For the WS we care about throughout the article, let's take a moment to clarify what we are talking about:

WS is a specification that guides Web development languages and is developed by W3C. These specifications contain multiple languages, such as HTML, XHTML, and CSS, and some other related languages, such as MathML, used to represent equations in mathematics. When you have such special needs, it may be useful. W3C has also published the "Web Content affinity Guide" (Web Content Accessibility Guidelines -- WCAG)-promoting Web page Accessibility (through WAI)

Tip: directly obtain these specifications

You can read these specifications on W3C websites, even though they are sometimes difficult to read:

In HTML 4.01

XHTML 1, 1.0

CSS 1

CSS 2.1

WCAG 1.0

In this article, we will use specifications and suggestions such as XHTML1.0, CSS1 and 2.1, and WCAG 1.0, but you must be glad to know that we do not have to read too much W3C documentation.

Who needs WS?

You may have only one vague concept: WS is a good thing, but many websites-including many well-known sites-do not comply with WS, and they seem to be well managed. So why are we trying to follow WS? Is there any real benefit from doing so? Who needs WS? Who needs to pay attention to W3C norms and suggestions?

Web developers and designers

The first group of WS users is us: developers and designers of website construction. Is it worthwhile for us to spend time learning how to develop with WS?

A clean flag accelerates BUG fixing.

If you pass W3C verification on your page, at least you will understand that the nonstandard mark is not the cause of the error you have encountered. Sometimes, the process of verifying a page and fixing detected errors can clear some problems encountered in the display. These problems are caused by the tag (element) not ending or tag) spelling error.

Even if your document does not correct these problems, you will at least know that these problems exist in the standard document. Now that you know that this problem is not an error, you can start to focus on other issues, such as CSS processing differences in different browsers.

It is easy to comply with the accessibility requirements

If you write a standard XHTML tag, you can ensure that the document is semantically correct, and you can separate the content from the presentation, you can put a lot of work on the accessibility issues listed in WCAG1.0. Recognizing that accessibility is not just designed for the disabled is also important. A site with good affinity can be accessed by many different devices, such as mobile phones and PDAs. They do not have powerful processing capabilities to deal with scattered and non-standard tags.

Forward compatibility

If you only consider the performance of your newly developed page in several browsers, how can you ensure its performance in the future? The new browser may display your page badly. At this time, you can only search for and fix annoying problems.

Compliance with WS does not completely eradicate this problem; however, compatibility with standards significantly reduces the risk of design failures, and today's browser software companies are also beginning to support standards. They may accidentally explain some of the rules, and they cannot completely support them. If the worst thing happens and a new browser has a strange effect on your standardized website, it is much easier to fix it than to fix an incompatible site. If you encounter a problem, it will also affect other standard-compatible websites. The group intelligence of the Web community will point out this problem and write articles to solve it. Therefore, it is easier to fix this BUG in compatible documents than in incompatible documents.

Easier reconstruction

Have you ever had to strip text from a website and refactor it? And everything has to start from scratch. Have you ever seen messy labels by font labels and tiny table cells (which can only start from scratch? I only know that I have seen it before. This is a long process, and a lot of time and money have been burned out by the reconstruction of this site.

</