A core requirement is that content is available fully in semantic html
h1 for your main headings instead of a
span with some css class.
In the Netherlands, the generic guidelines are made even more stringent on www.webrichtlijnen.nl . Some advantages are quicker websites (less html code needed); future-safe as they're also better viewable on mobile devices; etc.
Plone out-of-the-box complies with wcag and section 508. But not the Dutch guidelines. There are just a few changes that have to be made, though. The points where plone doesn't comply:
abbrtag should be easily usable from within kupu.
Tip: check your content on www.webrichtlijnen.nl if you're developing a Dutch website. Thijs did it for the plone.org website, which got a 33 out of 47 score. A tip from the audience: the accessibar firefox extension for checking loads of accessibility features.
So: a few small changes make plone ideal for making websites that comply with the webrichtlijnen.
My name is Reinout van Rees and I work a lot with Python (programming language) and Django (website framework). I live in The Netherlands and I'm happily married to Annie van Rees-Kooiman.
Most of my website content is in my weblog. You can keep up to date by subscribing to the automatic feeds (for instance with Google reader):