Module 10 Creating A Simple Markup Language Document Remedan
Module 10 Creating A Simple Markup Language Document Remedan
Administration
Level I
Based on March 2022, Curriculum Version 1
Acknowledgment .............................................................................................................. 3
Acronym ........................................................................................................................... 4
Introduction to the Module ............................................................................................... 5
Unit One: Review Requirements .............................................................................................. 6
1.1. Reviewing Document Requirements ....................................................................... 7
1.2. Selecting Markup Language Based on Organizational Standards ........................ 10
1.3. Reviewing Document Structure ............................................................................. 14
Self Check - 1.................................................................................................................. 21
Operation Sheet - 1 ......................................................................................................... 22
Lap Test - 1 ..................................................................................................................... 23
Unit Two: Create Document Structure .................................................................................... 25
2.1. Introduction to HTML ........................................................................................... 26
2.2. Creating Basic Elements of Document .................................................................. 29
2.3. Depicting Document Structure of Markup Sections .............................................. 36
2.4. Writing Simple Markup Language ........................................................................ 54
Self Check - 2.................................................................................................................. 72
Operation Sheet - 2.1 ...................................................................................................... 73
Operation Sheet - 3.2 ...................................................................................................... 74
Operation Sheet - 4.3 ...................................................................................................... 75
Lap Test - 2 ..................................................................................................................... 76
Unit Three: Validate Documents ............................................................................................ 77
3.1. Validating Markup Language Document............................................................... 78
3.2. Validating Markup Language Document in Different Browsers ........................... 81
3.3. Validating Simple Markup Language Document .................................................. 86
Self Check - 3.................................................................................................................. 87
Operation Sheet - 5 ......................................................................................................... 88
Lap Test - 3 ..................................................................................................................... 89
Reference ............................................................................................................................. 90
Developers Profile ................................................................................................................... 91
Ministry of Labor and Skills wish to extend thanks and appreciation to the many
representatives of TVET instructors and respective industry experts who donated their time
and expertise to the development of this Teaching, Training and Learning Materials (TTLM).
This module describes the performance outcomes, skills and knowledge required to design,
create and save a basic markup language document using text editor.
This unit is developed to provide you the necessary information regarding the following
content coverage and topics:
This unit will also assist you to attain the learning outcomes stated in the cover page.
Specifically, upon completion of this learning guide, you will be able to:
The first step in building a simple website is to clarify why the website is needed and what
functions it needs to perform.
You need to understand the purpose of the website, the audience you are trying to attract and
the design elements that will be needed to meet these requirements. This information is
included in a requirements (or design) document.
Web site development includes steps to ensure that the site content meets the client’s needs.
An important final check is then done after development, before presentation to the client, to
find and resolve any last minute problems.
A web site is the public face of an organisation; its quality is seen to reflect the quality of the
organisation itself. The reputation of an organisation can easily be damaged by a thing as
seemingly-trivial as a broken link, spelling mistakes or inconsistent text. The consistency test,
as part of that final check, is usually the final opportunity to ensure client needs are met.
The standards against which a web site might be assessed are usually found in project
documentation such as:
• The project brief
• Style guide
• Technical specifications.
Project documentation is developed in conjunction with the client and it outlines what the
client wants and the product should exist on completion. You should use project
documentation as the basis for designing your quality assurance checklist, while also
including test criteria to ensure that the web site complies with relevant web standards, such
as those pertaining to HTML, cascading style sheets (CSS), and the standards recommended
for accessibility.
The project brief is used to work out, define and clarify the client’s needs, and it is devised
once a contract is in place to develop a web site. Once the project brief is agreed to, the final
product must conform to it. To identify client needs the brief will answer questions such as:
• What is the purpose of the site?
• How is the ‘brand’ or image of the organisation conveyed?
• What is the user profile for the site?
Author/Copyright Creating A Simple Markup Version - 1
Page 7 of 91
Ministry of Labor and Skills Language Document September, 2022
• What are the needs of the site’s users or customers?
• What are the deadlines or milestones for developing the site?
• What is the environment of the web site users likely to be?
The project brief is also the starting point for a final check of the site.
The style guide describes the desired ‘look and feel’ of the web site and lists the elements
needed to consistently produce the desired effect.
The project manager or team will have consulted with the client about the vision they have
for the web site. Often a web site’s design or look will be linked to the corporate style of the
organisation. For example, a bank that targets young and single customers might project a
‘cool’ youthful image and want an internet site with a funky look and feel, but will still use
corporate colours and logos. The bank’s intranet site, which would be primarily used by staff,
on the other hand, might be more formal and plain, but also retain the corporate colours and
logos.
The style guide will set out requirements for design elements such as:
• colours, fonts and page layout
• the placement of logos or other significant graphics
• the style of multimedia and graphics.
Attributes of text-based content that might be assessed against client requirements include:
• font type, size and colour for body text and headings
• colour of text hyperlinks
• colour of visited link
• colour of active links
• leading or line height
• kerning
• text justification.
Technical specifications describe the technology the web site requires or should work on. The
quality assurance process must ensure that the web site functions correctly on each
combination of the technology specified. It may list requirements such as those outlined in
Table 1 to follow.
This section will look at the different markup languages available for website development
and cover things to consider in the design of a website.
What is markup language?
A markup language is a combination of text and information describing the text. This extra
information explains how the text should be displayed on a page. Markup languages for the
web use tags to tell a browser how to display text on a page.
1.2.1 Markup Languages for the Web
You will need to comply with certain web standards if you want your site to be accessed by
the broadest possible range of users. Remember that you users will have a range of computer
platforms, operating systems and web browsers. The manufacturers of these different systems
will have made efforts to comply with agreed web standards.
Standards for the web are developed by the World Wide Web Consortium (W3C)—an
international group including input from member organisations, full-time staff, and the
public. W3C’s mission is: ‘To lead the World Wide Web to its full potential by developing
protocols and guidelines that ensure long-term growth for the Web’. The W3C website
(www.w3.org) is the hub for standards information and includes technical guidelines,
educational information and code-checking tools called ‘validators’ that allow developers to
ensure their sites meet required web standards.
You may also want to look at examples of current ‘best practice’ in web design. Take note of
websites that you like or are similar in function to the site you intend to build—think about
the technologies and mark-up they employ and their useability. Also take a look at sites
showcasing recent designs such as:
• Webby Awards: www.webbyawards.com
• Cool Home Pages: www.coolhomepages.com
• NetGuide Australian Web Awards: www.netguide.com.au
Your choice of mark-up language will inevitably be affected by the resources you have at
your disposal. You will need assess and balance the amount of money, resources, time etc.
that you have available for your project. Starting up an XML project from scratch will require
more resources and planning than building a simple HTML site. However if you build in
HTML because of initial time constraints, but the site really requires XML and database
integration, you may have wasted your effort and need to rebuild your site anyway.
This is why it is important to fully assess you stakeholders’ and users’ needs before you start.
In a similar vein you need to assess what technology and skills you have available to you.
You may personally be a competent HTML programmer but have no knowledge of MathML
or RSS implementation. This does not necessarily make HTML the right choice for your
project.
With a thorough analysis of the site requirements you may have identified that MathML and
RSS would greatly benefit the site. Use this to argue for more resources from within your
organisation or of you are working on your own—seek advice from programmers who are
familiar with these technologies and employ them if you can.
If you want to learn the required skills yourself and have the time, start a small project to
implement these skills. Take a course or make use of the extensive range of online tutorials
and references available free on the web. Software that assists in implementing different
mark-up languages (such as Dreamweaver: www.macromedia.com) often have tutorials built
in to help you get started.
Once you have made a decision about the markup language you will use to create a website,
you need to consider how the website will be designed. There are two aspects of website
design: the folder structure for the website and the storyboard for the website.
Before starting out on a website project, you should create a folder structure to contain all the
files for your website. It is essential that all your web page files, graphics and other files are
collected in the same place right from the start of your project.
The larger the website the more complex the folder structure will be. Often there will be
folders to store related pages, style sheet files and other files such as animations.
It is best practice to create website storyboard before you start creating individual web pages.
A web storyboard is an outline of the pages required for the site (also called a website
structure) and the layout, content, navigation and design elements of the pages (also called
page structure).
Each page in your site should have a descriptive file name (see example storyboard below)
and the home page should be called index.html or default.html.
Figure 1.2 below shows the layout, content, navigation and design elements of the pages.
This was also created using the drawing tools in Microsoft Word.
When you create a link to a web page, or an image, or any file on the web, you could specify
the complete address of the file, such as:
<a href="http://www.example.com/users/jbrown/pics.htm">
This is an absolute address because the file can be located from anywhere on the Web. You
would use this form of addressing when the link is to a site somewhere outside of the server
you are using (i.e. it is on someone else's website).
If the page you wish to link to is located in the same folder as the originating page, you would
use relative addressing. For example, if you were the user (jbrown) in the example above,
and you wanted to link from your own "home.htm" page to your "pics.htm" file in the same
folder, a shorter way to refer to that HTML file would be:
<a href="pics.htm">
This is a relative address because it works as long as the new page is in the same folder on the
same server relative to the originating page. It is not complete enough to be used from
anywhere else on the Web.
<img src="images/picture_01.gif">
How do you go up a folder level? Take a look at the following example of a website folder
structure:
<a href="../contact.htm">
This address says "starting where you are, go up one level in the directories (that's the "../"),
and find the file "contact.htm"".
If you wanted link from "project_01.htm" in the "project_files" folder to a picture in the
"images" folder, the link would look like this:
<img src="../images/picture_01.gif">
This link says "go up one level and then look in the "images" folder for the file
"picture_01.gif"
In addition, to direct the browser to start at the top level of the server's directory structure
regardless of where the page you are linking from may be, use "/" as shown in this
example:
<a href="/project_files/project_01.htm">
This address says
• start at the top level of this website (that's the "/" symbol) and refers to the "www"
folder.
Note that this reference works from any page on this server (but not on the web), because it
starts by returning to the top level (the folder called "www" in the example above). This is a
useful technique on websites where there are many files and folders and where HTML files
may be moved around (for example, archiving news items)
File and folder organisation is crucial to building a website. Your website must have a logical
structure that does not change when you move files from your own computer to the web
server where your files will be available on the web. The main reason is that if a file moves in
relation to another file that contains a link to it, that link will break.
Creating Folders
Take a look at this sample of a website folder structure (it was created in Windows XP but
the principle of folder structures will remain the same across all operating systems):
Within the website root folder "www", there may be other folders containing the images and
media files. The root folder will contain only the files you need your viewer to see on your
website. On the web server where the files will be made available on the internet, there will
be no "my_website" folder. The web server will contain only the files in the "www" folder.
You can control where these files are located in relation to each other. These links to your
own files will be relative links. You should be able to pick up your entire root folder
("www") full of files and perhaps other folders, move it to another server and all the links
within the site would still work. None of the links can refer to the name of the server where
the files live.
You could test this by saving your root folder onto a USB flash memory stick or burning it to
a CD and taking it to another computer - once you open the home page in a browser, all the
other links should still work.
Make sure you collect all of your files together into a single root folder ("www") and
organise them first before starting to make links between them. If you link to an image and
then move it into a different folder, that link will break.
If you are pointing to someone else's file on another website, you have to indicate the
complete, absolute address of the file, since it most likely resides on another server.
Source files
Remember that your root folder ("www" in the example above) should contain only the files
that need to be made available on the website.
Your "source" files should be saved outside your website folder and do not need to be
transferred to the web server. In the example above the project folder "my_website" contains
not only the website folder "www" but also a folder for "source_files" and a folder for
"website_admin".
There are many different types of computers and servers used across the web. You need to
make sure that your file names will be read the same on all systems. To do this there are a
few simple rules which you must follow when creating files and folders for websites:
No spaces: Never use spaces in your file names - HTML will not read the code correctly. For
example, a file called "my pictures.htm" may be changed to "my%20pictures.htm" ("%20" is
code for a blank space) and your links may not work!
Use lowercase: Most web servers are case-sensitive and it is too easy to get case-sensitive
errors (Mypage.htm VS. MyPage.htm). Also lowercase names are much easier to remember.
This also applies to your tags - start making your tags lowercase now because it will save
you a lot of problems if you go on to learn other web mark-up languages (such as XHTML).
No special characters: HTML uses characters like &, >, #, !, /, etc. as part of it's code and
each can signify something in other mark-up languages. Use basic numbers and letters for
your filenames.
Less than 32 characters: Again this is an older convention (comes from earlier versions of
Apple and Windows operating systems) but to ensure compatibility on all computers it is still
a good rule to stick to.
8. What function do "tags" perform and how are they written? Give one example of a tag
and what it does.
9. You have been asked to create a website for a new Italian restaurant chain. When you
meet the marketing manager she tells you:
"We don't want any pizzas flying across the screen, or anything like that! We just want a
simple website that says 'quality'. We want a photo, addresses, phone numbers and a
menu that changes once a week. That's it."
Which of the following mark-up languages would you choose to build the site in and
why?
A. HTML
B. SGML
C. XHTML
D. DHTML
Purpose: Before starting out on a website project, you should create a folder structure to
contain all the files for your website. It is essential that all your web page files, graphics and
other files are collected in the same place right from the start of your project.
Procedures:
2. Create a new 'root' folder to store your pages and give it a name of your website(e.g.
my_website ), no space is required use underscore instead.
3. Create a separate folder under the 'root' folder name it images, where you store all the
graphics you use on the website.
4. Create another separate folder under the 'root' folder name it styles, where you store
all the styles you use in the website.
5. Create another separate folder under the 'root' folder name it scripts, where you store
all the scripts you use in the website.
6. Create additional separate folder under the 'root' folder name it pages, where you store
all the pages you use in the website.
7. Create one additional separate folder under the 'root' folder name it documents, where
you store all the documents you use on the website.
you can create additional folders based on the website requirements, those you created
above, specially from 3-5, are the common or basic folders for a websites.
Instructions: Given necessary templates, workshop, tools and materials you are required
to perform the following tasks.
They have 3 sample products: DC100 (a simple digital camera), DC250 (their next
step up in digital cameras) and DC500 (their best digital camera)
The site does not need to incorporate animated design features, but the code used to
create the site must be well formed and adhere to the latest standards.
Read the above scenario and perform the following tasks based on the scenario.
Task 1: Decide which markup language you will use to build a website for this client.
Task 2: Create Pixel Digital Products Folder Structure
• On your computer, create the minimum best practice folder structure for the Pixel
website. Call your ‘root’ folder Pixel.
Task 3: Create A Requirements Document
• Complete the following steps to create a Requirements document for Pixel:
1. Create a new word processing document called Pixel_Website.
2. Include a Title page with the Company Name and the company logo
3. Create a Table of Contents.
4. Include the following headings and content:
This unit is developed to provide you the necessary information regarding the following
content coverage and topics:
This unit will also assist you to attain the learning outcomes stated in the cover page.
Specifically, upon completion of this learning guide, you will be able to:
this text is not bold <b>this text is bold</b> this text is not bold
To be more correct you could use the tag <strong> to bold your text. The code is shown
below - the page would look exactly the same.
this text is not bold <strong>this text is bold</strong> this text is not bold
Note: Although HTML tags are not case-sensitive it's a good idea to get in the habit of
using lowercase. This is because XHTML only recognises lowercase. Also get used to
closing tags – even ones that don't need to be closed for HTML such as <br>. XHTML
requires all tags to be closed. XHTML will eventually replace HTML as the major mark-up
language on the web. To find out more about getting ready for XHTML go to the W3 Schools
website (www.w3schools.com). Look for the "XHTML Tutorial and find the section on
"Differences between XHTML and HTML".
Let's save it in an HTML file test.html using Notepad text editor. Finally open it using a
web browser like Internet Explorer or Google Chrome, or Firefox etc. It must show the
following output:
Figure 2-1: Web and Database Level I displayed on the title bar of the browser
We will study all the header and body tags in subsequent sections, but for now let's see what
is document declaration tag.
The <!DOCTYPE> Declaration
The <!DOCTYPE> declaration tag is used by the web browser to understand the version of
the HTML used in the document. Current version of HTML is 5 and it makes use of the
following declaration:
<!DOCTYPE html>
There are many other declaration types which can be used in HTML document depending on
what version of HTML is being used.
2.3.2. HTML Header Section
This section will give a little more detail about header part which is represented by HTML
<head> tag. The <head> tag is a container of various important tags like
A. <title>,
B. <base>,
C. <link>,
D. <style>,
E. <script>,
F. <meta>, and
G. <noscript> tags.
</body>
</html>
Save your document. You can give it a name like blank.html and then use it each time you
want to start a new document by opening it, making changes, and resaving the file with a
different name.
Indenting the tags for the document title has no impact on the way the code is rendered by a
browser. However, it greatly improves the readability of your code by others, including
yourself. The head section defines information about the document that doesn’t get displayed
in the browser window.
2.4.2. Controlling the Document Background
You can specify a document’s background color or background image using two different
attributes of the <body> tag; bgcolor and background. Background colors simply fill the
entire document. Background images are tiled by the browser, meaning they are repeated
left to right, top to bottom, filling up the visible space of the browser window. The default
body text color is controlled with the text attribute of the <body> tag.
• To define a background color for a document, set the bgcolor attribute equal to a
hexadecimal color value or predefined color name
<body bgcolor=”#0033FF” >
• To specify a background image, set the background attribute equal to the pathname
of the image file on your web server., as shown here:
<body background=”images/bgstone.jpg”>
Browsers indent list items by default, not because we’ve done so in the code. Indenting your code
just makes it easier to read.
Even though browsers allow you to omit them, always use closing </li> tags. They produce
cleaner, more readable code. And, of course, XHTML requires them. Bulleted lists (also called
unordered lists) aren’t radically different from ordered lists in their construction.
Modifying Ordered List Styles
By default, an ordered list renders items with Arabic numerals: 1, 2, 3, and so on. You
can modify the style of list items by defining the type attribute of the <ol> tag. The type
attribute for the <ol> tag accepts five possible values.
• To create an uppercase alphabetical list, set the type attribute equal to “A”:
<ol type=”A”>
• To create a lowercase alphabetical list, set the type attribute equal to “a”:
<ol type=”a”>
• To create an uppercase Roman numeral list, set the type attribute equal to “I”:
<ol type=”I”>
• To create a lowercase Roman numeral list, set the type attribute equal to “i”:
<ol type=”i”>
• To create an Arabic numeral list, set the type attribute equal to “1”:
<ol type=”1”>
While the values of the start and value attributes are always defined with an integer, the
corresponding list item character may not be numerical. For example, if the ordered list’s
type attribute equals A (creating an uppercase A, B, C list), setting the start or value
attribute equal to 3 begins the list with “C.” In an uppercase Roman numeral list
(type=“I”), the list would begin with III, etc.
The above example must show the following output:
<h1>Points to Remember</h1>
<ul>
<li>Don’t run with scissors</li>
<li>Don’t play with your food</li>
<li>Don’t forget to wash your hands</li>
</ul>
Just like ordered lists, there’s no limit to the number of list items you can have.
As with the ordered lists, browsers indent list items by default, not because we’ve done so
in the code. Indenting your code makes it easier to read.
The HTML standard contains a directory and menu list, created with <dir> and <menu>
tags. Like ordered and unordered lists, they used <li> tags for their list items. The
directory list was supposed to create multicolumn lists, and the menu list was meant for
single columns. Unfortunately, no browser ever attempted to render these lists. Using
these tags simply creates an unordered list.
Always use closing </li> tags. They make for cleaner, more readable code, and XHTML
requires them.
The default bullet style for unordered lists is typically a small filled-in disc. To see how to
modify bullet styles, see next Part.
Modifying Bullet Styles
Just like the <ol> tag, the <ul> tag accepts the type attribute. In this case, the type
attribute governs the style of the bullet that precedes each list item. The possible values
for the type attribute are disc, square, and circle.
• To create square bullets, set the type attribute equal to square:
<ul type=”square”>
• To create circular bullets, set the type attribute equal to circle:
<ul type=”circle”>
• To create disc bullets, set the type attribute equal to disc:
<ul type=”disc”>
<ul>
<li>Type defaults to disc</li>
<ul>
<li>First nest defaults to circle</li>
<ul>
<li>Third nest defaults to square...</li>
<ul>
<li>and continues as square until you set a <tt>type</tt>
attribute</li>
</ul>
</ul>
</ul>
</ul>
It must show the following output:
You can put any media file in src attribute. You can try it yourself by giving various types of
files.
Name Salary
Ramesh Raman 5000
Shabbir Hussein 7000
B. Cellpadding and Cellspacing Attributes
There are two attributes called cellpadding and cellspacing which you will use to adjust
the white space in your table cells. The cellspacing attribute defines the width of the
border, while cellpadding represents the distance between cell borders and the content
within a cell.
<table border="1" cellpadding="5" cellspacing="5">
<tr>
<th>Name</th>
<th>Salary</th>
</tr>
<tr>
<td>Ramesh Raman</td>
<td>5000</td>
</tr>
<tr>
<td>Shabbir Hussein</td>
<td>7000</td>
</tr>
</table>
Name Salary
</html>
12. Place your cursor on the line between the opening and closing tags. Type the tag
<head>, which defines the head section of the document.
13. Hit Enter twice and then type </head>. Your document should now resemble below.
<head>
</head>
14. To create the document title, which appears in the title bar of the browser window,
enter <title> and </title> between the head tags of your document, as shown below.
<head>
<title>Web and Database Level I</title>
</head>
15. The last element to add to your document template is the body section. Between the
closing </head> and the closing </html> tags, enter opening and closing body tags.
<!DOCTYPE html>
<html>
<head>
<title> Web and Database Level I </title>
</head>
<body>
</body>
</html>
16. Save your document. You can give it a name like blank.html and then use it each time
you want to start a new document by opening it, making changes, and resaving the
file with a different name.
<body>
<p>HTML only recognizes single spaces between characters. Other than a single tap on
the space bar, HTML has little regard for how you type things. What it does have regard
for is tags.</p>
</body>
</html>
3. To align a paragraph, add the align attribute to the paragraph tag:
<p align>
4. Set the align attribute equal to left, right, center, or justified, as shown:
<p align=”right”>HTML only recognizes single spaces between characters. Other than a
single tap on the space bar, HTML has little regard for how you type things. What it does
have regard for is tags.</p>
Instructions: Given necessary templates, workshop, tools and materials you are required
to perform the following tasks.
Using your Pixel storyboard from Lap Test - 1, create the Pixel website using HTML.
Incorporate the various elements you practiced in these TTLM. Use an internal style sheet for
all colors, fonts etc. As a minimum you should have the following pages:
• A startup page with the company logo only, linking to a Home page
• A Home page that has information about the company
• A Products page (use named hyperlinks to link to each product)
• A Frequently Asked Questions page
• A page where people can download user manuals
• Use a list to provide navigation on each page and an external style sheet for colors,
layout and fonts
• Include appropriate accessibility options
This unit is developed to provide you the necessary information regarding the following
content coverage and topics:
• Validating markup language document
• Validating markup language document in different browsers
• Validating simple markup language document
This unit will also assist you to attain the learning outcomes stated in the cover page.
Specifically, upon completion of this learning guide, you will be able to:
• Validate markup language document against requirements
• Validate markup language document in different browsers
• Validate simple markup language document
You can also download a number of standalone validation tools from the Tucows site:
www.tucows.com. Search for the term 'Validator'.
Note: Some applications for creating mark-up (such as Dreamweaver) also have their own
built-in mark-up language validators. Beware that even though they may be able to check
your site, they may not be 100% standards-compliant.
C. Common validation errors
A few common HTML/XHTML errors that you might encounter are:
• No DTD: You should make the first line of your HTML a 'document type definition'
(DTD) so that the validator knows what version and type of mark-up language you are
using—for example <!DOCTYPE HTML PUBLIC '-//W3C//DTD HTML 4.01
Transitional//EN'>)
• Missing alt tags - all graphics in your website should include "alt" tags to provide a
text alternative to users with vision impairment
• Improper nesting of elements - mark-up tags need to be opened and closed in the
correct order - i.e. the order they were opened in. For example <p><b> will be
followed by </b></p> (not </p></b>)
• Not closing tags - missing quote marks, brackets or colons
• Using spaces in document titles - use an underscore "_" instead
• Missing title - HTML/XHTML documents must have a "title" element in the head of
the document
• Using upper case tags - XHTML is case sensitive (use <body> not <BODY>)
• Missing quotes - attributes should have quotation marks surrounding them. For
example <font color="#003366">
On finding these errors you will need to address them and ideally re-validate your document
until you have eliminated all errors.
3. Name four reasons for writing your mark-up documents to conform to standards
4. What is a validator?
5. Where can you find a validator? Which markup languages are these validators for?
6. Describe three common mark-up code errors that you need to watch out for:
7. What is a "regression bug"?
Step 2:
Choose a validation tool from the list below:
World Wide Web Consortium (W3C) HTML and XHTML validators: validator.w3.org
HTML validator from the Web Design Group: htmlhelp.org/tools/validator/
Alternatively, you can download a number of standalone validation tools from the Tucows
site: www.tucows.com. Search for the term "Validator".
Step 3:
Use the validation tool to validate your mark-up document. Follow the instructions for the
validation tool that you chose.
Use the table you created to record the errors and what you will do to fix them.
Instructions: Given necessary templates, workshop, tools and materials you are required
to perform the following tasks.
Task 1: Validate The Pixel Website you created on Lap Test - 2, using World Wide Web
Consortium (W3C) HTML and XHTML validators: validator.w3.org
Task 2: Validate The Pixel Website you created on Lap Test - 2, using HTML validator
from the Web Design Group: htmlhelp.org/tools/validator/
• Robert G. Fuller and Laurie Ann Ulrich. HTML in 10 Simple Steps or Less, Wiley
Publishing, Inc.
WEB Address
• https://web1.muirfield-h.schools.nsw.edu.au/technology/resources/vetit/