All content must be AA and AAA compliance.

Hi everyone,

I am a newbie to Teamsite and i have a requirement stating "All content must be AA and AAA compliance". I have a doubt in mind if this can be acheived through teamsite or CMS or should it be handled at the UI construction side where we can apply CSS to the generated content.

Please clarify if this can be handled by teamsite and is it good to handle this at Content creation side by the content author.

Thanks,
Kiran.

Find more posts tagged with

Comments

sandy123

Hi everyone,

I am a newbie to Teamsite and i have a requirement stating "All content must be AA and AAA compliance". I have a doubt in mind if this can be acheived through teamsite or CMS or should it be handled at the UI construction side where we can apply CSS to the generated content.

Please clarify if this can be handled by teamsite and is it good to handle this at Content creation side by the content author.

Thanks,
Kiran.

Can you please elaborate on what do you mean by AA and AAA compliant. What is this compliance ? is it only look and feel compliance ? or is it some kind of data constraint ?

After getting details to these questions, we will be able to answer rest of your queries ...

Sandy

Slabrador

You can do anything you want with your output files - it's one of strengths of TeamSite. However, AA and AAA compliance are pretty subjective at the best of times, so you have to use a lot of common sense and don't pay too much attention to automated testing (it's a good place to start, but it's not the be-all and end-all).

I think the best approach to AA and AAA compliance is probably the same for all CMSs, and pretty much all projects in TeamSite - restrict the freedom you give your users to foul things up as much as you can.

The only place that it's really a problem is if you're using either of the WYSIWYG editors (or if you're expecting users to write HTML into a text box). Both the WYSIWYG editors have their own idiosyncrasies, but you should be able to deal with most problems with a combination of a trimmed-down editor and some processing in your presentation templates.

The most problematic templates built in TeamSite (in my experience) tend to be the simplest - the ones that give the user a single content field into which they paste code from some HTML generator (Dreamweaver, or whatever) - this always leads to code that you have no control over.

HTH.

Frederik

Can you please elaborate on what do you mean by AA and AAA compliant.

Google says...
http://www.w3.org/TR/WAI-WEBCONTENT/#Conformance

Adam Stoller

Google says...
http://www.w3.org/TR/WAI-WEBCONTENT/#Conformance

Heh - I thought they were talking about batteries or baseball farm leagues ;-)
If the question is with regard to the content generated within TeamSite / deployed to the web / app server - then I think Slabrador hits it pretty much on the head.
If the question is with regard to the TeamSite UI - well, you can play around a bit with the CSS there too (see UICG) - but it would probably be worthwhile to submit FR's to Support for anything you found you needed to change (and not whether you weren't able to do so) in order to choose this compliancy - though given the definitions, AAA is pretty "loose".

Slabrador

What's a 'baseball farm' - makes me think of genetically modified chickens laying very strange eggs...

EDIT: Oh... I thought the query was about the output files as the OP said "All *content* must be AA and AAA compliance"

Michael_Mc_OFI

I have a similar requirement where content entered into templates must be 508 compliant. The letters "A", "AA", and "AAA" describe different levels of accessibility compliance (See W3C for more: http://www.w3.org/TR/WAI-WEBCONTENT/#Conformance)

I've found other CMS solutions that offer this feature in their Visual Formatter type of solution, and I'd be interested in solutions aimed at Interwoven's Product Suite (specifically VF).

While we can initiate process to assist content entry personnel in validating for 508 compliance (FireFox accessibility plugin: http://firefox.cita.uiuc.edu/), we'd prefer to automate the process.

It seems that the company that makes eWebEditPro (the Visual Formatter tool for TeamSite Templates) provides 508 compliance support for eWebEditPro V5+, which would be included with TeamSite V6.7+

Of course we are on TS6.5, using eWebEditPro 4... so I have to see if we can upgrade only the eWebEditPro tool.

Thoughts?