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

RE: NVU, child of Mozilla Composer (Windows & Linux)

From: Steven Dale <sdale@stevendale.com>
Date: Mon, 21 Jun 2004 21:11:21 -0400 (EDT)
Message-ID: <2144.>
To: <gdeering@acslink.net.au>
Cc: <lois@lois.co.uk>, <w3c-wai-ig@w3.org>

That is what Macromedia Contribute does.  Unfortunately, they dont allow
you to forcibly make the content accessible.  After making a piece of
content available to be edited via Contribute, they can apply styles with
the bold button, they can use font instead of Hx tags, etc.  If you find
an answer Geoff please let me know for I am in the same boat here.


>> > I really feel authoring tools need some facility to be able to
>> only allow
>> > users to update the content within certain <DIV> tags... ie <DIV
>> id="content">  Something like this anyway, I don't know, but
>> some way that
>> > users can use a WYSIWYG editor to update content, for the software
>> to ignore all the other markup and protect it, and also produce
>> valid markup
>> > for any user.
>> You can already do this in Dreamweaver/Composer to some extent:
>> not perfect,
>> but if you start off with an accessible template and the right
>> accessibility
>> settings, you can do quite a lot to stop the end user messing up.
>> (E.g. prevent him/her adding font tags, using <em> instead of <i>,
>> only allowing certain style rules to be selected, and protecting
>> certain parts of the body
>> and header.) It has been my experience that non-expert end users can
>> use the
>> Composer editor much as they would a WP - together with all the
>> freedom to ignore document structure within your hypothetical <div
>> id="content"> that this implies, of course.
> Yes, but you have knowledge of the issues.  Why don't tools help novices
> in these areas.  There are enough tools and plugins out there to build a
> WYSIWYG tool that will guide users who need to be guided, who want to
> be.
> I have been in a situation where I was quoting for a job where the
> requirements were that all pages needed to meet Strict DTD XHTML and
> WAI-AA. No problem, but that they could also be easily maintained by the
> client organisation with DW4.  This to my knowledge is not possible, it
> will screw it up every time.  They couldn't afford to upgrade their
> organisation to DWvX.  What do you do?  They want their cake and eat it
> too.  And
> organisations like this do not what to deal with the issues, as far as
> they are concerned I'm the one who is incompetent if I have problems
> with these requirements.
> WHAT I really feel is needed by Macromedia, is to issue a version of DW
> Lite with the licensed version.  This version would have no code
> generation or design facilities at all, but could be configured to
> distribute to clients of the licensee to update content without touching
> the code, and make sure the marked up content is valid.
> For instance, being configured to only access areas in the content
> marked with content identifiers set by the developer.  Maybe they could
> extract a small license fee for this Lite version.
> It because there is nothing around that addresses this need, I'd like to
> see something address it.
> Geoff
Received on Monday, 21 June 2004 21:11:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:28 UTC