Setting and Customized Up by Prelaunch Testing Method

Building web pages is one of those activities that require you to remember a bunch of little details that all add up to a finished web site. Besides designing the pages, optimizing all the graphics, building the pages, pasting in all the relevant content in every page ,dropping in JavaScript and media files and formatting everything with CSS.
Building web pages is one of those activities that require you to remember a bunch of little details that all add up to a finished web site. Besides designing the pages, optimizing all the graphics, building the pages, pasting in all the relevant content in every page, dropping in JavaScript and media files and formatting everything with CSS.
You have to remember to include meta tags in the code add customized titles to every page, give images alternate text, and add target attributes to links that should open in separate browser window. The list could go on and on.

The help you remember all the things to do, try creating your own web-testing check-list, like the starter list every site you build prior to publishing: Web site prelaunch testing checklist. Have you performed a spell and syntax check, included the correct DTD, applied source formatting, organized your CSS, and cleaned up any a HTML and word HTML coding errors. Have you tested the pages in multiple browsers and browser versions on both the Mac and PC platforms and found solutions for any glaring errors?
Do all the page on the site include meta tags. Does each page have a unique, descriptive title. Do all the images include alt text or empty alt text attributes. Do all the hyperlinks include title attributes. Have you hand-checked all the internal and external hyperlink for accuracy. Do they go where you want them to go? Did you find any broken links that need fixing. When aligning tables, have you replaced tag alignment attributes with surrounding alignment tags. Does the site have any unused files, images or folder that can be safely moved to another location or deleted. Are the site’s forms and tables fully accessible and functional. In the sections that follow, you learn about some of best tools for completing all these tasks.

Cleaning Up Code:-some people might think that hand-coders must always make a practice of checking the hierarchical order, syntax, and spelling of their HTML code, but that designers using HTML editors need not worry about syntactical or other HTML errors. Not true. Even if you use the best program out there, your code will have errors because you’re human and because the program was made by a human. No matter how carefully you build a site, the HTML in your pages might inadvertently become cluttered with redundant tags, the unnecessary markup and outright detrimental code that can negatively impact the presentation of your pages. Many of the error within the coding happen when you paste content from other sources like a world or Excel file, from an online resource, or from another code editor or application. Other times , an error might just be an honest typo that wasn’t caught or something that happened behind the scenes when moving elements around the page by clicking and dragging or cutting and pasting. Which some code editors occasionally leave in the code for no apparent reason when you move a link from one spot on the page to another.