Using Dreamweaver and Front Page

Cyber-Sierra Workshop 2002: Accessible Webs

Using Dreamweaver and FrontPage
| Index | Tools | WYSIWYG | Checkpoints | MarkUp |

The two WYSIWYG editors most likely to be used in building a web site are Dreamweaver and FrontPage. Both editors have some features that can be used in the WYSIWYG mode for creating more accessible pages. But neither program can achieve fully accessible web sites using just WYSIWYG. Consequently I highly recommend the Extension Course: Web Site Accessibility for everyone.

Dreamweaver

Dreamweaver: Here is a brief summary list of the features that either are or aren't available in the graphical interface (WYSIWYG interface: What You See Is What You Get). To see the entire tutorial, see How to Make Accessible Web Content Using Dreamweaver

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 contrastof 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.

Frontpage

Frontpage 2000, like many other web editors, can be used to create accessible web content. Many accessibility features can be added from Frontpage 2000's main interface. However, some accessibility fixes can only be done by changing the HTML code directly. Fortunately, Frontpage 2000 makes it relatively easy to edit the code. In addition, the Frontpage application has been updated so that it no longer "fixes" your HTML when you make a change to the code.

Here is a summary list of the features that either are or aren't available in the graphical interface (WYSIWYG interface: What You See Is What You Get). To see the entire tutorial, see How to Make Accessible Web Content Using Frontpage 2000

Edits that CAN be done
from the WYSIWYG interface

Edits that CANNOT be done
from the WYSIWYG interface

Adding alt tags to images.
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 the TABINDEX feature.
Adding meta-data.
Adding labels to form elements.

Adding alt tags to java applets and image maps.
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 colorblindness compatibility.
Checking the flicker rate of images or animations.
Give titles to frames.
Identify the natural language of the document, or changes in the natural language.
Creating ACRONYM tags.
Providing keyboard shortcuts.
Providing summaries for tables.

More Information:

WebAIM Center
Web Accessibility In Mind Center has extensive articles, checklists and tutorials that will help you modify your site to make it most accessible.

Extension Course: Web Site Accessibility
This is a six-segment electronic class aimed at web site developers and managers to help them become familiar with web site accessibility issues and compliance with the Americans with Disabilities Act (ADA). I strongly encourage you to save-file the pages to have the information available offline for reference. The tereminology is in HTML, so you may need to refer to the Bare Bones guide to help you through. The course itself is very read-able.

The Bare Bones Guide to HTML
A handy cheat sheet for HTML tags.