RESOURCES  UNSW EDUCATIONAL DEVELOPMENT & TECHNOLOGY WEBSITE
Flexible EducationWeb & Media ProductionWebCT @ UNSWLearning Resource Catalogue
Web & Media Production
    

 

 

Producing Content for the WebWeb Design & ConstructionAccessibility in Web Design

Accessible web design

 
Content & navigation HTMLInteractive & other mediaWebCT accessibility issuesValidation

Using Dreamweaver

Accessible web content may be created using practically any authoring tool. Unfortunately, many of the more useful accessibility features of HTML are not programmed directly into the Dreamweaver interface (or any of the other commonly used HTML editors). However there are some things that you can do in Dreamweaver without having to go to the source code.

Formatting the default Dreamweaver template

The default Dreamweaver template needs some adjustment for HTML4.0 compatibility. You can follow the instructions here: http://www.webaim.org/howto/dreamweaver#h21.

or save this page to replace the existing template (in Dreamweaver>Configuration>Templates).

From WebAIM, here is a summary list of the features that either are or aren't available in the Dreamweaver graphical interface (WYSIWYG interface: What You See Is What You Get).

Edits that CAN be done
from the WYSIWYG interface

Edits that CANNOT be done
from the WYSIWYG interface

  • Adding alt tags to images, java applets, image maps.

  • Adding a method to skip over long lists of links (e.g. "skip to main content" links).

  • Adding table headers (using TH).

  • Providing redundant text links to server-side image maps.

  • Creating client-side image maps rather than server-side image maps.

  • Changing the contrast of a page or element.

  • Controlling the destination of links (to avoid opening up new windows).

  • Marking up quotations.

  • Creating valid lists.

  • Using relative size units (e.g. for tables) rather than absolute sizes.

  • Adding headings and subheadings.

  • Creating templates that can be used across pages (so that you can have a consistent navigational scheme and style of presentation).

  • Providing transcripts for videos or audio clips (you have to do the work, but you can type it into the WYSIWYG page).

  • Adding empty alt tags for decorative images, spacer gifs, etc.

  • Adding the LONGDESC attribute.

  • Associating table headers with data cells (using ID, HEADERS, SCOPE, AXIS, etc.)

  • Adding alt tags for embedded plug-ins.

  • Adding form accessibility features (LABEL, OPTGROUP, FIELDSET and LEGEND).

  • Captioning videos.

  • Checking for color-blindness compatibility.

  • Checking the flicker rate of images or animations.

  • Giving titles to frames.

  • Identify the natural language of the document, or changes in the natural language.

  • Creating ACRONYM tags.

  • Adding the TABINDEX feature.

  • Providing keyboard shortcuts.

  • Providing summaries for tables.

  • Adding meta-data.

How to implement each of the above items is explained in some detail at: http://www.webaim.org/howto/dreamweaver. This page also describes how to enhance the accessibility features of Dreamweaver.

A similar tutorial on creating accessible sites using FrontPage is at: http://www.webaim.org/howto/frontpage.php

Back to HTML

 

 
 
UNSW Educational Development & Technology Centre RESOURCES home RESOURCES home