Thread Subject: Re: web/software CMS(s) and accessibility
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Smith, Jamie
Date: Wed, Apr 18 2007 10:50 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Roberto Scano - IWA/HWG: "Re: web/software CMS(s) and accessibility"
- Previous message in thread: Andi Snow-Weaver: "Re: web/software CMS(s) and accessibility"
- Messages sorted by: Author | Thread | Date
I agree with you Andi. Ensuring compliance is difficult. I've looked
at many of the open source casemangement systems and the problem is that
most are such that one would cut and paste from something like word.
Header levels unless someone know what that was are lost.
Also, the original template has to be redone with someone who can get to
In essence, even with the best system, garbage in - garbage out applies.
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
Sent: Tuesday, April 17, 2007 11:06 AM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] web/software CMS(s) and accessibility
I would love to have such a tool but I am dubious of any vendor who
claims their tool "ensures" compliance with WCAG AAA. It would be most
interesting to see how can a tool force authors to use accurate ALT text
Sent by: "TEITAC Web/Software
< = EMAIL ADDRESS REMOVED =
= EMAIL ADDRESS REMOVED = >
04/16/2007 10:04 [teitac-websoftware] web/software
AM CMS(s) and accessibility
Please respond to
= EMAIL ADDRESS REMOVED =
how components of authoring tools fit together is a complicated topic,
but if each implements accessibility capacities that match the format in
use at that stage, the end products should be greatly improved. For
example, given a product as listed below, if appropriate mark up is
exported from another format when imported into a CMS tool, it may have
less work to do, but when inaccessible content is imported, work may
need to take place in the new format. Basically authoring tools to me,
should do as much as they can with the format they have, and allow those
attributes to be passed along in the chain. The more formats you
support, the more accessible work may need to be included, or plugged in
to a tool, however, remember that Section 508 compliance always involves
a continuum of products compliance levels.
Note, wonder if the AJAX end-user part of this is fully accessible?
This is only an FYI not any endorsement--just an example of the fact
that authoring tools are taking the steps we are discussing now, some
more than others I'm sure.
DHS Office on Accessible systems & Technology
IT Week, United Kingdom
Friday, April 13, 2007
Webcredible CMS boosts web site accessibility
By Phil Muncaster, IT Week
Content management system ensures sites are compliant with the W3C's
Web accessibility consultancy Webcredible is set to launch a new content
management system (CMS) designed to ensure firms' sites are compliant
with level AAA of the W3C's Web Content Accessibility Guidelines (WCAG).
The product, which will be launched at the Internet World event in a
fortnight, automatically cleans up code so that it complies with the
standards, and forces content editors to use correct heading structures
and accurate ALT text for all images, among other things, according to
the firm's managing director Trenton Moss.
"While the Web Content Accessibility Guidelines (WCAG) provide a useful
framework for developing an accessible web site, online retailers will
run into trouble if they rely solely on their interpretation of these
filled, somewhat vague guidelines," he added. "We are offering a system
that actually forces editors to produce accessible content during the
web page development and editing process."
The product also utilises Ajax technology to improve the user
experience, and can optimise web pages for search engines, according to
"Putting an accessible CMS at the heart of all web site content
development can also save companies time and money, as online retailers
will not need to develop and maintain separate, accessible web pages in
addition to their main web site," explained Moss.
- Next message in Thread: Roberto Scano - IWA/HWG: "Re: web/software CMS(s) and accessibility"
- Previous message in Thread: Andi Snow-Weaver: "Re: web/software CMS(s) and accessibility"