Re: DHTML browsers [was Accessibility]

On Mon, 13 Sep 2004 15:35:19 -0500, Austin, Darrel wrote
> 
> I looked at about 15 WYSIWYG editing components over the last few months.
> They all suck in one way or anther. ;o)

I haven't worked with many, but even conceptually they all suck as they merge
content with presentation.  But the business users get sold on these things to
the point where they think they are the true value of CMS and can't work
without them.  Accessibility concerns in the markup seem to dwarf all my
WYSIWYG code and usage complaints based mostly Ektron EWebEditPro/Interwoven
Visual Format Editor.

There do not seem to be any hard and fast rules on structuring content into
templates.  Personally I don't like seeing each paragraph as a field, but I
also don't like lazy templates that are just wrappers for the WYSIWYG with one
or two other fields.  Almost every project seems to end up with the latter. 
If you've ever built a template that tries to help a user build tables without
a WYSIWYG you know that's not a real solution either.  

Unfortunately, anything using ActiveX is not an option as business users may
not have admin rights on their machines and SMS updates can blow those things
away.

But there can't be an impossible problem, so a software solution must exist.