Rhondas fully cooked

Home Recipe

ICTWEB304 - Assesment Task 1

Q1. Describe the difference between an XML Sitemap and a HTML Sitemap. List the benefits and disadvantages of using each.

XML (Extended Markup Language) is designed for search engines (bots), it is storing, transfering data and listing all the important URLs on a website in XML format. While HTML, it displays the data and lists links to important pages in a user-friendly format, helping users/visitors navigate the website easily.

  1. XML:
    • ✔ Helpful for big websites with lots of pages
    • ✘ Not designed for human, only for search engine.
  2. HTML:
    • ✔ Easy to create for human, better and easier navigation for human
    • ✘ Not designed for a large website and does not give search engine extra information
Q2. Evaluate three IDE’s (Integrated development environments) and provide a brief summary on the positive and negative aspects of each. Also, in your own words include how it would suit an entry level trainee code developer.
  1. Visual Studio Code:
    • ✔ Free on Windows and Mac
    • ✔ Simple layout and has auto-complete and error-checking
    • ✘ Features need to be manually install
    • • Visual studio code is a great tool for beginner as it is not complicated in setting up and does not use much of computer capability.
  2. PyCharm:
    • ✔ Specifically made for phyton, it has lots of smart tools for Phyton coding
    • ✔ Has a built-in code suggestion, makes it easier for beginner
    • ✘ Slow on older or less powerful computer
    • ✘ Cost-associated and focuses only on phyton
  3. Eclipse
    • ✔ Free & supports various languages (Phyton, Java, etc)
    • ✘ Heavy program, sometimes can be slow (depending on the computer)
    • • This can be confusing for a beginner at first. It suits for someone who has a basic knowledge of coding and wants to work for a bigger project.
Q3. Provide a brief history on web browser development and the issues encountered by web developers, specifically, the adherence to web standards.

The first web browser was called WorlWideWeb created by Tim Berners-Lee in 1990, it allowed users to access and navigate linked documents over the internet. The second web browser is released in 1993 which is called Mosaic, it introduced a graphical interfece that made the web more user-friendly, providing support to display text and images together.

Netscape Navigator and Microsoft Internet Explorer were released by mid-1990s, they became a main competitor. Both tried to rushed to introduce new features to dominate the market and appeal more users. However, these updated features were not based on a standard, thus it created lack of consistency and made it difficult for web developers.To resolve theses issues, World Wide Web Consortium (W3C) established a web standards such as HTML, CSS, and JavaScript guidelines. These standards designed to achieve the consistency and make web development easier. However, not every web browser adhered strictly to the standards, especially Internet Explorer, which follows its own rules.

In the early 2000s, web browsers such as Mozilla Firefox, Google Chrome and Apple Safari got published with stronger support for web standards. These web browsers was aiming to achieve more consistet experience.
Q4. What are website testing methodologies? Your answer MUST cover browser compatibility, and website functionality.
Webiste testing methodologies are techniques can be used, works as intended, and accessible accros various devices and browsers. These methodologies can significantly enhance user experience, identify bugs and helps improve performance. Website testing methodologies includes:

  1. Functionality testing

    Functionality testing includes links testing (such as anchor links to other pages), forms testing (submit data, display success/error messages) and navigation testing (buttons must lead users to the right page/destinated page)

  2. Browser compatibiliy testing

    Check if the website is working on various browsers (Chrome, Firefox, Safari, Edge, etc.). Also to ensure images, fonts, and layouts work and load properly in all browsers.

  3. Performance Testing

    Load testing (how the site performs when many users is using at once) and speed testing (how quick the pages load)
Q5. What are the endorsed requirements of accessibility for all NT Government webpages?
  1. WCAG 2.1 Level AA Compliance
    Adequeate colour contrast and resizeable text, user should be able to navigate without a mouse, alt text for images, video caption and transcripts (for users with hearing impairments), clear structure and headings (can easily understand content flow/structure)
  2. NT Government Style Guide and Web Standards
    Plain english, jargon free unless necessary, mobile-friendly and responsive design and designed forms must be easy to use with assistive technology
  3. Testing and quality assurance
    Manual testing with screen readers (NVDA), keyboard only navigation testing, user testing (for people with different access needs)
Q6. How do you think it’s best to organise all the assets used for a specific webpage? Think locally on your computer AND within the root folder of the website.
  1. Local computer. Use a different folder for each website project and use a consistent structure. Keeping everything grouped together by type and needs, easy to find, avoiding messy folder chaos. Have a folder for css style, images, and java scripts, leaving index.html and other pages outside of the folder.
  2. Root folder of the website. The root folder is where the main directory of the website (index.html and other pages) located. The structure of the web server should mirror the local setup so everything uploads and links smoothly. Also to name files clearly so it can be navigated and remembered easily.