ATAG10 evaluation of Dreamweaver 3.0 (Macintosh)

1.1 Ensure that the author can produce accessible content in the markup language(s) supported by the tool. [Priority 1] (Checkpoint 1.1)

Yes. There is a source editing mode. Most HTML features are also supported in the WYSIWYG mode or property sheets (but not all - for example longdesc is lacking)

1.2 Ensure that the tool preserves all accessibility information during authoring, transformations, and conversions. [Priority 1] (Checkpoint 1.2)

1.3 Ensure that when the tool automatically generates markup it conforms to the W3C's Web Content Accessibility Guidelines 1.0 [WCAG10]. [Relative Priority] (Checkpoint 1.3)

No. It allows img to be inserted without an alt attribute (P1 violation), automatically generates HTML presentation markup instead of using style sheets(P2 violation), misuse strucutral elements for formatting (P2 violation).

1.4 Ensure that templates provided by the tool conform to the Web Content Accessibility Guidelines 1.0 [WCAG10]. [Relative Priority] (Checkpoint 1.4)

Not Applicable. Dreamweaver does not seem to have any templates included.

2.1 Use the latest versions of W3C Recommendations when they are available and appropriate for a task. [Priority 2] (Checkpoint 2.1)

No. It uses HTML elements, but does not produce HTML 4.0

2.2 Ensure that the tool automatically generates valid markup. [Priority 1] (Checkpoint 2.2)

No. According to the help files, Dreamweaver generates valid markup. However, it is lacking a doctype declaration, so cannot in fact be valid (or tested for validity)

2.3 If markup produced by the tool does not conform to W3C specifications, inform the author. [Priority 3] (Checkpoint 2.3)

No

3.1 Prompt the author to provide equivalent alternative information (e.g., captions, auditory descriptions, and collated text transcripts for video). [Relative Priority] (Checkpoint 3.1)

No. See below for details.

WCAG Checkpoint 1.1 Provide a text equivalent for every non-text element [Priority 1]

No. Dreamweaver provides a place to put an alternative image for more complex multimedia formats (such as flash) but not a text alternative. The relevant property is a secondary (initially hidden) part of the dialog, except in the case of images.

WCAG Checkpoint 1.2 Provide redundant text links for each active region of a server-side image map. [Priority 1]

Refer also to WCAG checkpoint 1.5 and WCAG checkpoint 9.1.

Techniques for WCAG checkpoint 1.2

HTML

Use the same User interface for server and client side image map creations, including prompting for alternatives for each region. Use alternatives provided to generate redundant text-based links for server-side maps.
Prompt for text which describes the range and the effect of possible coordinate entries, and generate an alternative, form-based entry system.

WCAG Checkpoint 1.3 Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation. [Priority 1]

Techniques for WCAG checkpoint 1.3

WCAG Checkpoint 1.4 For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation. [Priority 1]

Techniques for WCAG checkpoint 1.4

WCAG Checkpoint 1.5 Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map. [Priority 3]

Refer also to WCAG checkpoint 1.2 and WCAG checkpoint 9.1.

Techniques for WCAG checkpoint 1.5

HTML: Use the alt associated with area elements to build a redundant text navigation bar

WCAG Checkpoint 3.1 When an appropriate markup language exists, use markup rather than images to convey information. [Priority 2]

Refer also to WCAG guideline 6 and WCAG guideline 11.

Techniques for WCAG checkpoint 3.1

WCAG Checkpoint 6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes. [Priority 1]

No. Allows the inclusion of rollover or layered content without requesting alternative content at all.

WCAG Checkpoint 6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. [Priority 1]

No. Allows the inclusion of applets etc without prompting for alternative content at all - there is an alt property in the extended properties, but no mechanism in the main user interface to include alternative functionality.

WCAG Checkpoint 6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. [Priority 2]

Techniques for WCAG checkpoint 6.5

WCAG Checkpoint 7.3 Until user agents allow users to freeze moving content, avoid movement in pages. [Priority 2]

When a page includes moving content, provide a mechanism within a script or applet to allow users to freeze motion or updates. Using style sheets with scripting to create movement allows users to turn off or override the effect more easily. Refer also to WCAG guideline 8.

Techniques for WCAG checkpoint 7.3

WCAG Checkpoint 8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.]

Refer also to WCAG guideline 6.

Techniques for WCAG checkpoint 8.1

WCAG Checkpoint 9.1 Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape. [Priority 1]

Refer also to WCAG checkpoint 1.1, WCAG checkpoint 1.2, and WCAG checkpoint 1.5.

Techniques for WCAG checkpoint 9.1

HTML: Use the same interface for defining areas of client- and server-side maps, and produce the image as client-side where possible

WCAG Checkpoint 11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. [Priority 2]

Techniques for WCAG checkpoint 11.1

Raster images (PNG, JPEG, GIF)

Use RDF to incorporate textual equivalents in image encodings

Vector images

Use SVG, and prompt the author to provide appropriate title and desc elements for each g element.

WCAG Checkpoint 11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.) [Priority 3]

Techniques for WCAG checkpoint 11.3

WCAG Checkpoint 11.4 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page. [Priority 1]

Techniques for WCAG checkpoint 11.4

General: Note that the alternative page is required to be an accessible version, rather than simply a plain text or other partial view of the information

WCAG Checkpoint 13.2 Provide metadata to add semantic information to pages and sites. [Priority 2]

Refer also to WCAG checkpoint 13.5.

Techniques for WCAG checkpoint 13.2

Images: Metadata can be added to most image formats commonly used on the Web, including PNG, JPEG, GIF, and SVG. See the W3C Note "Describing and retrieving photos using RDF and HTTP" [[RDFPIC]].

WCAG Checkpoint 14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page. [Priority 3]

Refer also to WCAG guideline 1.

Techniques for WCAG checkpoint 14.2

HTML: Provide libraries of accessible clip art to illustrate common concepts, or allow the author to build them. See also ATAG 3.5

3.2 Help the author create structured content and separate information from its presentation. [Relative Priority] (Checkpoint 3.2)

Yes (perhaps). The editing model is of visual formatting, but it is possible to edit by structure. There is support provided for using Style Sheets (in a menu-based user interface - the author is not required to learn CSS)

WCAG Checkpoint 2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup. [Priority 1]

Techniques for WCAG checkpoint 2.1

General: Prompt the author to identify a class, or markup element for uses of color.

WCAG Checkpoint 2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen. [Priority 2 for images, Priority 3 for text].

Techniques for WCAG checkpoint 2.2

WCAG Checkpoint 3.1 When an appropriate markup language exists, use markup rather than images to convey information. [Priority 2]

Refer also to WCAG guideline 6 and WCAG guideline 11.

Techniques for WCAG checkpoint 3.1

WCAG Checkpoint 3.3 Use style sheets to control layout and presentation. [Priority 2]

Techniques for WCAG checkpoint 3.3

WCAG Checkpoint 3.5 Use header elements to convey document structure and use them according to specification. [Priority 2]

Techniques for WCAG checkpoint 3.5

Text / hypertext

Prompt the author to identify headings and subheadings
Provide an "outline" or "structure" view which allows the author to easily grasp the heading structure, and edit it.

WCAG Checkpoint 3.6 Mark up lists and list items properly. [Priority 2]

Techniques for WCAG checkpoint 3.6

text / hypertext

Include lists (marked as lists) in a collapsible structure view

WCAG Checkpoint 3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation. [Priority 2]

No. Uses blockquote for formatting effects.

WCAG Checkpoint 4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). [Priority 1]

Techniques for WCAG checkpoint 4.1

WCAG Checkpoint 4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs. [Priority 3]

Techniques for WCAG checkpoint 4.2

HTML: Ask the author to provide an expansion for abbr and acronym elements or confirm that a previously supplied one should be used again.
General: Provide a dictionary mechanism that recognizes abbreviations and prompts the author to include appropriate markup.

WCAG Checkpoint 4.3 Identify the primary natural language of a document. [Priority 3]

Techniques for WCAG checkpoint 4.3

General:: Ask the author to identify the language of any document. Provide a mechanism for setting a default.

WCAG Checkpoint 5.1 For data tables, identify row and column headers. [Priority 1]

Techniques for WCAG checkpoint 5.1

WCAG Checkpoint 5.2 For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells. [Priority 1]

For example, in HTML, use THEAD, TFOOT, and TBODY to group rows, COL and COLGROUP to group columns, and the "axis", "scope", and "headers" attributes, to describe more complex relationships among data.

Techniques for WCAG checkpoint 5.2

HTML: Ask the author to group columns, rows, or blocks of cells that are related.

WCAG Checkpoint 5.3 Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version). [Priority 2]

Refer also to WCAG checkpoint 3.3.

Techniques for WCAG checkpoint 5.3

HTML

Prompt the author to identify tables which are used as layout devices.
For layout tables, provide a linearized version, and offer it as a link from the table or as a replacement. An example tool which linearizes tables is tablin.

WCAG Checkpoint 5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting. [Priority 2]

Techniques for WCAG checkpoint 5.4

WCAG Checkpoint 5.5 Provide summaries for tables. [Priority 3]

Techniques for WCAG checkpoint 5.5

HTML

In a table creation wizard, include a summary or caption dialog
Render the caption, title and summary of a table, or prompt for content.

WCAG Checkpoint 5.6 Provide abbreviations for header labels. [Priority 3]

Techniques for WCAG checkpoint 5.6

WCAG Checkpoint 6.1 Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document. [Priority 1]

Techniques for WCAG checkpoint 6.1

HTML: Provide a "draft" view which does not use styling.

WCAG Checkpoint 6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes. [Priority 1]

Techniques for WCAG checkpoint 6.2

WCAG Checkpoint 6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. [Priority 1]

Refer also to WCAG guideline 1.

Techniques for WCAG checkpoint 6.3

HTML

Prompt for server-side alternatives for scripts and applets
Prompt for noscript content for each script.
Prompt for alternative content for applets and programmatic objects (for example object elements which have a code attribute).

WCAG Checkpoint 6.4 For scripts and applets, ensure that event handlers are input device-independent. [Priority 2]

Refer to the definition of device independence.

Techniques for WCAG checkpoint 6.4

Applet development

Prompt the author to include device-independent means of activation

WCAG Checkpoint 6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. [Priority 2]

Techniques for WCAG checkpoint 6.5

HTML

Ask the author for:

appropriate links and content to include in a noframes element
a server-side alternative to applets and script functions

WCAG Checkpoint 7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker. [Priority 1]

Techniques for WCAG checkpoint 7.1

WCAG Checkpoint 7.2 Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off). [Priority 2]

Techniques for WCAG checkpoint 7.2

WCAG Checkpoint 7.3 Until user agents allow users to freeze moving content, avoid movement in pages. [Priority 2]

Refer also to WCAG guideline 8.

Techniques for WCAG checkpoint 7.3

WCAG Checkpoint 7.5 Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects. [Priority 2]

Techniques for WCAG checkpoint 7.5

WCAG Checkpoint 8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.]

Refer also to WCAG guideline 6.

Techniques for WCAG checkpoint 8.1

WCAG Checkpoint 9.1 Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape. [Priority 1]

Refer also to WCAG checkpoint 1.1, WCAG checkpoint 1.2, and WCAG checkpoint 1.5.

Techniques for WCAG checkpoint 9.1

WCAG Checkpoint 9.2 Ensure that any element that has its own interface can be operated in a device-independent manner. [Priority 2]

Refer also to WCAG guideline 8.

Techniques for WCAG checkpoint 9.2

WCAG Checkpoint 9.3 For scripts, specify logical event handlers rather than device-dependent event handlers. [Priority 2]

Techniques for WCAG checkpoint 9.3

WCAG Checkpoint 9.4 Create a logical tab order through links, form controls, and objects. [Priority 3]

Techniques for WCAG checkpoint 9.4

HTML: Where there are only a few links that change in each page of a collection, ask the author if they should receive focus first. If so, then give them a tabindex, leaving the rest to after the tabindexed links have been focussed. Note, of course, that in most cases presentation order will be the logical order for sequential access such as tabbing with the keyboard.

WCAG Checkpoint 9.5 Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. [Priority 3]

Techniques for WCAG checkpoint 9.5

HTML: Ask authors to specify an accesskey for links that appear common to a number of pages

WCAG Checkpoint 10.1 Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user. [Priority 2]

Techniques for WCAG checkpoint 10.1

HTML: Where a link or active element will spawn a new window, prompt the author for title text to make this clear.

WCAG Checkpoint 10.2 Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned. [Priority 2]

Refer also to WCAG checkpoint 12.4.

Techniques for WCAG checkpoint 10.2

WCAG Checkpoint 10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas. [Priority 3]

Techniques for WCAG checkpoint 10.4

HTML: Prompt the author for default place-holder text. Offer the value of the name attribute as a default.

WCAG Checkpoint 10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. [Priority 3]

Techniques for WCAG checkpoint 10.5

WCAG Checkpoint 11.2 Avoid deprecated features of W3C technologies. [Priority 2]

Techniques for WCAG checkpoint 11.2

WCAG Checkpoint 11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.) [Priority 3]

Note. Use content negotiation where possible.

Techniques for WCAG checkpoint 11.3

WCAG Checkpoint 11.4 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page. [Priority 1]

Techniques for WCAG checkpoint 11.4

WCAG Checkpoint 12.1 Title each frame to facilitate frame identification and navigation. [Priority 1]

Techniques for WCAG checkpoint 12.1

HTML

Prompt the author for a short, human-readable title for each frame. Default text presented in the prompt could use the title defined for the document referenced in the src

WCAG Checkpoint 12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. [Priority 2]

Techniques for WCAG checkpoint 12.2

HTML

Prompt the author for a longdesc for each frame in a frameset.
Prompt the author to add a noframes section to the frameset. Encourage the author to include sufficient links to navigate the site, and relevant information. For example, where a frameset defines a navigation frame and a welcome page, include the content of each of these frames in the noframes.

WCAG Checkpoint 12.3 Divide large blocks of information into more manageable groups where natural and appropriate. [Priority 2]

Refer also to WCAG guideline 3.

Techniques for WCAG checkpoint 12.3

HTML: Where there are more than 10 choices in a list (select, checkbox or radio boxes) ask the author to identify subgroups

WCAG Checkpoint 12.4 Associate labels explicitly with their controls. [Priority 2]

Techniques for WCAG checkpoint 12.4

HTML: Ask authors to mark explicitly the labels for form inputs (input and textarea elements)

WCAG Checkpoint 13.1 Clearly identify the target of each link. [Priority 2]

Techniques for WCAG checkpoint 13.1

General: Prompt the author to provide text which can be used as a title for a link.

WCAG Checkpoint 13.2 Provide metadata to add semantic information to pages and sites. [Priority 2]

Refer also to WCAG checkpoint 13.5.

Techniques for WCAG checkpoint 13.2

General: Ask authors for information about a page or site. If its function is known (see also WCAG checkpoint 13.9) add this information as metadata.

WCAG Checkpoint 13.3 Provide information about the general layout of a site (e.g., a site map or table of contents). [Priority 2]

Techniques for WCAG checkpoint 13.3

General: Prompt the author to provide a link or content describing the structure of the site, and its accessibility features.

WCAG Checkpoint 13.4 Use navigation mechanisms in a consistent manner. [Priority 2]

Techniques for WCAG checkpoint 13.4

WCAG Checkpoint 13.5 Provide navigation bars to highlight and give access to the navigation mechanism. [Priority 3]

Techniques for WCAG checkpoint 13.5

WCAG Checkpoint 13.6 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. [Priority 3]

Techniques for WCAG checkpoint 13.6

HTML: Ask authors if lists of links are a group and should be a map.

WCAG Checkpoint 13.9 Provide information about document collections (i.e., documents comprising multiple pages.). [Priority 3]

Techniques for WCAG checkpoint 13.9

General

Pattern-matching - ask authors to specify the role of pages linked from a navigation bar.
Where common names are used (search, home, map) as links, ask the author to confirm these functions for use in linking.

WCAG Checkpoint 13.10 Provide a means to skip over multi-line ASCII art. [Priority 3]

Refer to WCAG checkpoint 1.1 and the example of ascii art in the glossary.

Techniques for WCAG checkpoint 13.10

HTML: Where a PRE element is used with substantial punctuation and non-words, ask for text alternative.

WCAG Checkpoint 14.1 Use the clearest and simplest language appropriate for a site's content. [Priority 1]

Techniques for WCAG checkpoint 14.1

General

Provide readability ratings for text.
Provide a thesaurus function
Provide a grammar-checking function

WCAG Checkpoint 14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page. [Priority 3]

Refer also to WCAG guideline 1.

Techniques for WCAG checkpoint 14.2

3.3 Ensure that prepackaged content conforms to the Web Content Accessibility Guidelines 1.0 [WCAG10]. [Relative Priority] (Checkpoint 3.3)

Not Applicable.

3.4 Do not automatically generate equivalent alternatives. Do not reuse previously authored alternatives without author confirmation, except when the function is known with certainty. [Priority 1] (Checkpoint 3.4)

Yes.

3.5 Provide functionality for managing, editing, and reusing alternative equivalents for multimedia objects. [Priority 3] (Checkpoint 3.5)

4.1 Check for and inform the author of accessibility problems. [Relative Priority] (Checkpoint 4.1)

No.

4.2 Assist authors in correcting accessibility problems. [Relative Priority] (Checkpoint 4.2)

No.

4.3 Allow the author to preserve markup not recognized by the tool. [Priority 2] (Checkpoint 4.3)

Yes. Dreamweaver has full support for clean round-trip of source.

4.4 Provide the author with a summary of the document's accessibility status. [Priority 3] (Checkpoint 4.4)

No.

4.5 Allow the author to transform presentation markup that is misused to convey structure into structural markup, and to transform presentation markup used for style into style sheets. [Priority 3] (Checkpoint 4.5)

5.1 Ensure that functionality related to accessible authoring practices is naturally integrated into the overall look and feel of the tool. [Priority 2] (Checkpoint 5.1)

No. Some functionality is, but some is only available through source editing.

5.2 Ensure that accessible authoring practices supporting Web Content Accessibility Guidelines 1.0 [WCAG10] Priority 1 checkpoints are among the most obvious and easily initiated by the author. [Priority 2] (Checkpoint 5.2)

No. See for example comments about mechanisms for adding alternative content for multimedia elements.

6.1 Document all features that promote the production of accessible content. [Priority 1] (Checkpoint 6.1)

No. Very nearly - but some HTML features appear not to be documented (searches for longdesc and acronym turned up nothing).

6.2 Ensure that creating accessible content is a naturally integrated part of the documentation, including examples. [Priority 2] (Checkpoint 6.2)

No. For example, the only use of the term noframes is in a single, stand-alone page about how to create noframes content.

6.3 In a dedicated section, document all features of the tool that promote the production of accessible content. [Priority 3] (Checkpoint 6.3)

No. (At least not that I could find)

7.1 Use all applicable operating system and accessibility standards and conventions (Priority 1 for standards and conventions that are essential to accessibility; Priority 2 for those that are important to accessibility; Priority 3 for those that are beneficial to accessibility). (Checkpoint 7.1)

Not tested. I am told that Dreamweaver probably meets the requirements for Microsoft Active Accessibility, but probably not those for the Macintosh.

7.2 Allow the author to change the presentation within editing views without affecting the document markup. [Priority 1] (Checkpoint 7.2)

No. Dreamweaver implements CSS. The user can create a local style sheet to use in addition to the others, but needs to remove it to publish

7.3 Allow the author to edit all properties of each element and object in an accessible fashion. [Priority 1] (Checkpoint 7.3)

Dreamweaver allows source editing. (Since it is a WYSIWYG editor, this would not meet the requirements of cheeckpoint 5.1. I suspect there is a better way to do this, but haven't learned the product well enough yet.)

7.4 Ensure that the editing view allows navigation via the structure of the document in an accessible fashion. [Priority 1] (Checkpoint 7.4)

7.5 Enable editing of the structure of the document in an accessible fashion. [Priority 2] (Checkpoint 7.5)

Yes. The elements can be navigated, cut, copied and pasted.

7.6 Allow the author to search within editing views. [Priority 2] (Checkpoint 7.6)

Yes. Dreamweaver has a search function in the editing view.

ATAG10 Conformance Review of Dreamweaver 3.0 (Macintosh)

1 Introduction

2 Guidelines

Guideline 1. Support accessible authoring practices.

Checkpoints:

Guideline 2. Generate standard markup.

Checkpoints:

Guideline 3. Support the creation of accessible content.

Checkpoints:

Further techniques for this guideline are given in the appendix Techniques for User Prompting

Guideline 4. Provide ways of checking and correcting inaccessible content.

Checkpoints:

Guideline 5. Integrate accessibility solutions into the overall "look and feel".

Checkpoints:

Guideline 6. Promote accessibility in help and documentation.

Checkpoints:

Guideline 7. Ensure that the authoring tool is accessible to authors with disabilities.

Checkpoints: