Friday, May 01, 2009

Designing an influenza pandemic web site for Australia

Students of "Networked Information Systems" (COMP2410/6340) at the ANU have been set the task to design a influenza pandemic web site for the Australian public. In previous years they have been set the task to design a site for bird flu so this seemed a logical and timely topic.
Australian National University

Department of Computer Science

Networked Information Systems


Assignment 2

Website Accessibility


On 29 April 2009 the Director-General of the World Health Organization (WHO), raised the level of influenza pandemic alert from phase 4 to phase 5. All countries were advised to immediately activate their pandemic preparedness plans to combat Swine influenza.

In this assignment you will examine web sites used for providing advice to the public about influenza and design a prototype web site using the techniques learnt in the course. ...

Deadline: 6pm Friday 22 May 2008.

The Task

The Australian Government Department of Health and Ageing (DHA) has provided a web page with links to detailed information about Swine Influenza Outbreaks. However, that information may be difficult to understand for the average member of the general public. Imagine you work for the Australian Government and your task is to design an easier to read web site based on the DHA page as it was at 30 Apr 2009 07:09:19 GMT.

The web site will need to meet accessibility and mobile device standards. The web site will be read by large numbers of people at once and so will need to use the minimum of bandwidth. It will be read by people under stress and so be easy to read.

In addition to the information in the copy of the DHA web site, you can use text and media files (images, audio and video) from International (.int), Australian Government ( and US Government (.gov) web sites in designing your prototype.

Creating the webpage

You must:

  • Convert the HTML of the content from the existing web page to valid XHTML Basic 1.1 which achieves at least 80/100 on Mobile OK tests and passes Level Double A of the W3C - Web Content Accessibility Guidelines 1.0 (WCAG 1.0) as tested by the TAW (Web Accessibility Test)
  • Convert all presentation elements and in-line styles to appropriate rules in a new valid external style sheet called access.css
  • Remove any tables in the webpages which are not used for displaying tabular data, and replace them with CSS rules
  • Remove or replace excessively large or irrelevant images. You are encouraged to consider the use of Pictograms, as well as links to audio, video and other multimedia content.
  • Make any changes to the XHTML code which you consider to either: enhance the accessibility of the page, or improve the compliance of the page with web standards
  • Discuss your design decisions in a report
  • Estimate the download time of your page (using the access.css stylesheet) using a 28.8 kbit/s Iridium satellite modem (as used by the Australian Department of Defence). Suggest ways in which you might reduce the download time. These question must be answered in the form of an additional section in your report.
Your resulting page need not be identical in appearance to the web pages the source material was prepared from. You need only create the home page, but can create dummy links to other pages (which you need not create). The emphasis should be on a simple and efficient design. The page should be designed to display both on a smart phone and a desktop computer. Design decisions about the way the page looks must be discussed in your report.

Writing the report

You are also required to write a report which presents and justifies your design decisions. The report should be between 600-1000 words long (the word length is not assessable, but a report which falls outside these limits may impact on your ability to complete all assessable tasks). The report should include (but is not restricted to) discussions of the following topics:

• Any design decisions you made which significantly alter the appearance of the webpage. These must be justified by an appeal to accessibility, web standards, or best practice coding guidelines.
• Changes you have made to the code which you consider to have enhanced the accessibility of the webpage.
• Alternative design decisions which you considered implementing, along with a discussion of the advantages and disadvantages of these.
• Any accessibility issues, or areas of non-compliance with web standards, which are still present in your completed page.

Your report must be valid XHTML-Basic 1.1. The formatting must be clear, and include headers and paragraphs. Citations are not needed. ...


For examples of government swine flu web sites, see Tom Worthington's posting: Lack of useful Swine Influenza Information online from Australian Government, Thursday, April 30, 2009. ...

No comments: