W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > April to June 2002

RE: Selecting Software: FYI DreamWeaver MX Accessibility Features

From: <saylordj@WellsFargo.COM>
Date: Thu, 27 Jun 2002 09:09:49 -0700
Message-ID: <583643968681D4119D170001FA7EEA8106F315D4@xcem-casfo-04.wellsfargo.com>
To: corcora1@msu.edu, w3c-wai-eo@w3.org
[Archive edit made 2002.07.02 pursuant
to W3C Archive Editng Policy* - in response 
to request made to archive-editor@w3.org.

* http://www.w3.org/Mail/ArchiveEditingPolicy] 

We have evaluated Flash in regard to its features and looked
at some disability features.  I will look at them this weekend.
Doyle Saylor
Wells Fargo
-----Original Message-----
From: Charmane K. Corcoran [mailto:corcora1@msu.edu] 
Sent: Thursday, June 27, 2002 8:55 AM
To: w3c-wai-eo@w3.org
Subject: Selecting Software: FYI DreamWeaver MX Accessibility Features
Has anyone checked out DreamWeaver MX yet? 
It prompts the developer to enter accessible coding for web page components.
We are in process of upgrading our office software to DW-MX Studio which
includes the more-accessible version of Flash etc. It has a lot of other
great features, including more-accessible Cold Fusion and components from
the earlier version of DreamWeaver Ultra Dev. 
If you haven't looked at the specs yet, may be worth your time. 
Please see http://www.macromedia.com/macromedia/accessibility/mx/dw/ 

Resent-Date: Thu, 27 Jun 2002 11:44:46 -0400 (EDT) 
Date: 27 Jun 2002 11:44:42 EDT 
From: Sarah.Horton@Dartmouth.EDU (Sarah Horton) 
To: w3c-wai-eo@w3.org 
MIME-Version: 1.0 
Subject: Selecting Software 
Resent-From: w3c-wai-eo@w3.org 
X-Mailing-List: <w3c-wai-eo@w3.org> archive/latest/2760 
X-Loop: w3c-wai-eo@w3.org 
Sender: w3c-wai-eo-request@w3.org 
Resent-Sender: w3c-wai-eo-request@w3.org 
Precedence: list 
List-Id: <w3c-wai-eo.w3.org> 
List-Help: <http://www.w3.org/Mail/> 
List-Unsubscribe: <mailto:w3c-wai-eo-request@w3.org?subject=unsubscribe> 
Hello, all! I have a new version of Selecting and Using Authoring Tools for
Web Accessibility. I have not made many changes since we last talked. I cut
down the intro a bit and moved the inline links to ATAG and WCAG. 
For my own enjoyment I made a version with the links removed altogether: 
I still feel that we could remove the references to ATAG in the context of
discussing workarounds, but I promise I won't mention it again. 
If you follow the links below to the changelog you will see the specific
entries that I still have questions about: 
>From Change Requests from 11 Feb 2002 
1 Is this item a "not"? Hard to tell from the changelog. 
2 I added A-Prompt to strategy 2 but wasn't sure how to add it to strategy
3 This item does not seem related to selecting software or even strategies
for working around software limitations. It's more of an accessible Web page
authoring strategy. 
4 and 5 Unclear from changelog what to do about language issues. 
>From Change Requests from 13 Feb 2002 
1 I was uncertain where this item belongs. Is this a vendor question? Is
this something you ask webmasters when considering authoring tool selection?

2 I do not know what this means. 
I hope we can wrap up these last entries tomorrow during our meeting and
then pronounce this document done! 
Until tomorrow, 

Have a Productive Day! 
Charmane K. Corcoran            
Information & Project Principal 
Michigan State University                       
Client Advocacy Office          
Digital Information Group                       
114 Computer Center     
East Lansing MI 48824   
HmPg: http://www.msu.edu/~corcora1/ 
E-Mail: corcora1@msu.edu (Personal) 
        webmaster@msu.edu (MSU Web Related) 
Ph: 517/353-4856 
FAX: 517/432-0366 
Received on Thursday, 27 June 2002 12:10:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:29:33 UTC