Website Development Example

Website development example

Most computer-based systems perform some automated procedures or processes.Even the simplest website enables a visitor to navigate around the site to find information. More complex websites authenticate visitors and may automate transactions through e-commerce. Technical requirements for system procedures and processes identify the non-functional specifications of the proposed system itself.

Usability

Go to to read about usability testing. Usability testing can involve principles such as

navigation
functionality
control
language
feedback
consistency
error handling
visual clarity.

from Gerry Gaffney at

Accessibility

A good starting point for information on website usability and accessibility is the World Wide Web Consortium (W3C) website at

Ensuring your website complies with the Web Accessibility Initiative (WAI), Web Content Accessibility Guidelines is a quality assurance issue and is an expected standard in the web development industry. It is also recommended in Australian discrimination legislation.

An online presentation at Judy Brewer and EOWG Participants describes Web accessibility as:

access to the Web by everyone, regardless of disability. Web accessibility includes:

websites and applications
that people with disabilities can perceive, understand, navigate and interact with
web browsers and media players

that can be used effectively by people with disabilities, and
that work well with assistive technologies that some people with disabilities use to access the web

web authoring tools and evolving web technologies

that support production of accessible web content and websites
that can be used effectively by people with disabilities.’

The WAI has four different guidelines for accessibility:

Web Content Accessibility Guidelines 1.0 (WCAG 1.0);
Authoring Tool Accessibility Guidelines 1.0 (ATAG 1.0);
User Agent Accessibility Guidelines 1.0 (UAAG 1.0);
XML Accessibility Guidelines (XAG).

The Web Content Accessibility Guidelines 1.0 (WCAG 1.0) is a reasonably long document. There are summaries and checklists available. The guidelines cover the following areas:

Provide equivalent alternatives to auditory and visual content,for example:

use "alt" text for images
text alternatives for video etc
provide redundant text links for active regions in server-side image maps

Don't rely on colour alone

Ensure any information conveyed with colour is also conveyed via other means.

Use mark up and style sheets and do so properly.
Clarify natural language usage:
identify changes in natural language (such as captions, abbreviations or foreign text).

Create tables that transform gracefully:
use row and column headers in data tables.
Ensure that pages featuring new technologies transform gracefully:
ensure pages can be read without associated style sheets
ensure that alternatives to dynamic content are updated as required.
Ensure user control of time-sensitive content changes:
avoid causing the screen to flicker.
Ensure direct accessibility of embedded user interfaces:

make scripts, etc, compatible with assistive technologies (or provide alternatives).

Design for device-independence.
Use interim solutions.
Use W3C technologies and guidelines.
Provide context and orientation information:

eg title each frame.

Provide clear navigation mechanisms.
Ensure that documents are clear and simple:

use clear and simple language.

For further information on accessibility you should go to read:

Checklist of Checkpoints for Web Content Accessibility Guidelines 1.0 (this checklist provides details on priority levels).

Web Content Accessibility Guidelines 1.0

2836_reading03.doc: Determine technical requirements1