<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2873" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=626474716-29052006><FONT face=Arial
color=#0000ff size=2>I add my vote to Alessandro's call, especially re work on
accessibility for content authors. It's increasingly a deciding factor in
CMS package selection exercises.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=626474716-29052006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=626474716-29052006><FONT face=Arial
color=#0000ff size=2>Maybe this could be factored into the work which Alexander
Kandzior described on giving the OpenCms back-end an AJAX flavour. I look
forward to hearing more about that because it concerns both accessibility and
general useability. I'd love to see an even more powerful XML content
editing framework, and I'd be happy to contribute in this area.
Functionality I'm thinking would be useful includes (i) a more full-blown
approach to defining schema validity (so XSD for structural definitions
supplemented with something like RelaxNG or a home-grown rules-based approach);
(ii) validity checking at the client without requiring a round trip (with page
refresh problems) just to be told that an element far down the page isn't valid;
(iii) more support in OpenCms for defining and managing standing/reference data;
(iv) richer controls as value editors, e.g. sliders, spinners, ...
</FONT></SPAN><SPAN class=626474716-29052006><FONT face=Arial color=#0000ff
size=2>Oops! I'm going off-topic.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=626474716-29052006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=626474716-29052006><FONT face=Arial
color=#0000ff size=2>Jon</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> opencms-dev-bounces@opencms.org
[mailto:opencms-dev-bounces@opencms.org] <B>On Behalf Of </B>Keith
Davey<BR><B>Sent:</B> 29 May 2006 17:32<BR><B>To:</B> The OpenCms mailing
list<BR><B>Subject:</B> Re: [opencms-dev] Status of OpenCms
accessibility<BR></FONT><BR></DIV>
<DIV></DIV>I second this. <BR><BR>We are working on the accessibility of an
OpenCMS site we have built right now.<BR><A
href="http://www.dublinairport.com">http://www.dublinairport.com</A><BR><BR>Its
going to be a major problem trying to ensure that content entered by editors
is<BR>accessible.<BR><BR>I am happy to have a look at integrating XStandard is
anyone can point me in the <BR>right direction.<BR><BR>Keith<BR><BR>
<DIV><SPAN class=gmail_quote>On 5/29/06, <B class=gmail_sendername>Alessandro
Magnolo</B> <<A
href="mailto:alessandro.magnolo@gmail.com">alessandro.magnolo@gmail.com</A>>
wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">Dear
All,<BR>and dear Alkacon representatives in particular,<BR><BR>I wrote many
times about the need of assuring the accessibility of<BR>content generated by
the CMS users (authors). This is especially true<BR>for Italy, where
accessibility is a law requirement for public <BR>administration sites, and
will soon be for all EU countries.<BR><BR>In my opinion OpenCms is a great
tool for generating<BR>standard-compliant websites, especially since the
introduction of<BR>FCKEditor as the default editor (it can produce XHTML
Strict code if <BR>used in Firefox - not in IE, unfortunately).<BR><BR>The
next step would be to improve the back-end interface<BR>accessibility. I know
this is a very hard task, but it could start by<BR>creating a separate
accessible interface, to be used initially for the <BR>simplest tasks, and
then growing to become a complete alternative (if<BR>not "the"
interface).<BR>For example, a first release of the "accessible backend" could
show<BR>the users the list of files in the VFS and allow them to edit and
<BR>publish content (leaving more complex administrative tasks, like
user<BR>management, to the improved/standard interface).<BR>What do you think
about this? What is your experience? Have you<BR>perceived an interest in
backend accessibility in the community of <BR>OpenCms
users?<BR><BR><BR>Another step, more oriented towards front-end accessibility,
would be<BR>the integration of an editor explicitly designed with
accessibility in<BR>mind (this means not only valid code, but also checks for
<BR>accessibility tags and attributes enforced in the editor).<BR>The only one
I know is XStandard, that recently announced the<BR>availability of a freely
distributable version of the editor for open<BR>source CMS developers. <BR>I
attach part of their press release at the end of this
message.<BR><BR><BR>Again, I'd like to know if this is of interest to the
community, and<BR>what are Alkacon plans for accessibility, in particular
regarding<BR>their stance on accessibility laws for EU countries.<BR><BR>Best
regards,<BR>Alessandro Magnolo<BR><BR>-----<BR>XStandard is the leading
standards-compliant plug-in WYSIWYG editor<BR>for Windows desktop applications
and browser-based content management <BR>systems
(IE/Mozilla/Firefox/Netscape).<BR><BR>The editor generates clean XHTML Strict
or 1.1, uses CSS for<BR>formatting, and ensures the clean separation of
content from<BR>presentation. Markup generated by XStandard meets the most
demanding <BR>accessibility requirements. The editor's cool features include
drag &<BR>drop file upload, spell checking and an image library that
integrates<BR>tightly with your CMS.<BR><BR>We are making XStandard Lite with
some Pro features available to <BR>established vendors of open source CMS who
wish to offer XStandard as<BR>an optional (freeware) editor in their
applications.<BR>Details of the program can be found at<BR><A
href="http://www.xstandard.com/xstandard-lite-for-partner-cms/">http://www.xstandard.com/xstandard-lite-for-partner-cms/</A><BR>-----<BR><BR>_______________________________________________<BR>This
mail is sent to you from the opencms-dev mailing list<BR>To change your list
options, or to unsubscribe from the list, please visit <BR><A
href="http://lists.opencms.org/mailman/listinfo/opencms-dev">http://lists.opencms.org/mailman/listinfo/opencms-dev</A><BR></BLOCKQUOTE></DIV><BR></BODY></HTML>