Microsoft FrontPage to Expression Web
|
|  Yüklə 1.85 Mb.
|
Checking for Compatibility and AccessibilityOne of the many benefits of using Web standards to design your site is enhanced cross-browser compatibility and accessibility. Expression Web includes built-in tools to help you check for compatibility and accessibility errors. In order to use the compatibility and accessibility checkers, you should always specify a DOCTYPE for your Web page. A DOCTYPE, as discussed earlier, identifies the specific HTML standard that your document follows. If your page does not already have a DOCTYPE specified, you can go into the HTML code and insert the DOCTYPE manually. Expression Web comes with code snippets to allow you to do this easily:
Once you have the DOCTYPE specified, Expression Web will be able to better help you be aware of coding errors that don’t meet the specifications of that DOCTYPE. In Code view, code errors are highlighted in yellow. For example, if a tag is missing the closing slash, Expression Web will highlight the tag in yellow to let you know that there is a problem with the code. If you hover the pointer over the highlighted code, Expression Web provides a screen tip explaining the error. Similarly, if you hand code and have a typo in one of your HTML tags, Expression Web will put a red squiggly line underneath to let you know that there is a problem. Again, you can hover over the underlined content to view a screen tip telling you what the error is. 
The red underline indicates HTML incompatibility. 
The META element without an end tag highlighted in Code view indicates a code error. Expression Web also displays the HTML Incompatibility Detected icon and the Code Error Icon in the status bar if it detects a problem with the HTML code. This allows you to be notified of code errors while working in Design view. 
The HTML Incompatibility Detected icon and the Code Error icon in the Status bar. Expression Web also helps you to meet Web standard and accessibility guidelines in the Compatibility and Accessibility task panes. Both task panes run reports when you click the green arrow. You choose what specification you want to test the site against. When the report is complete, the errors are then listed, making it easier to locate and address each one. For example, in the Accessibility Checker, you can select the range of pages that you want to check and then select the specific guidelines that you want to test your site against. You can then set the report to show errors (compliance errors), warnings (potential problems), or a manual checklist (issues that require human verification).
Similarly, the Compatibility checker allows you to select the range of pages to check and for which standards to test. After publishing your Web site, you can check your site one more time by using some of the online tools available for validating Web sites:
Apart from testing your site against the various Web standards, you should also use Expression Web to test your Web site in multiple browsers. Install the various browsers you want to test your site against. To add them to your browser list, on the File menu, click Preview in Browser, and then click Edit Browser List. After adding the browsers, you can then open the Web page that you want to check, and then on the File menu, click Preview in Browser. After that, select the browser and resolution that you wish to test your site against. Working with FrontPage Web Components in Expression WebFrontPage included many Web components, also called webbots, that enabled a lot of common functionality which beginning Web designers saw on other sites and wanted to add to their own sites. As mentioned earlier, Web components don’t exist in Expression Web. Web components were notorious for not being standards–compliant and very difficult to customize. For FrontPage users transitioning to Expression Web, the good news is that Web components that require FrontPage Server Extensions (FPSE) will continue to work as long as the site remains on a server with FPSEs. In addition, almost all of the components can be edited in Expression Web by double-clicking the component in Design view. Even though Expression Web supports your pre-existing Web components, you might want to consider moving away from FrontPage Web components for several reasons. First, they produce invalid code; second, your ability to customize Web components is severely limited; third, FrontPage Server Extensions have a limited life span; and fourth, you can’t add new components using Expression Web. This section explains how to edit FrontPage Web components you may have in your site and also provides resources and suggestions to get functionality similar to that provided by unsupported FrontPage Web components. The Insert Web Component Dialog BoxIn FrontPage, you inserted Web components by clicking the Web Components command on the Insert menu to display the Insert Web Component dialog box. 
The following paragraphs address each of the components as they appear in the Insert Web Component dialog box. |
