The Accessibility Challenge
Making sure a site stays accessible once it’s been handed over to the client is often very difficult, even next to impossible. In The Accessibility Challenge, Kassia Krozser talks about some of the issues that make it hard for non-technical editors to produce accessible content.
- Previous post: Keeping multiple Macs in sync
- Next post: Tipping Firefox across the chasm
Subscribe / follow
Sponsors
Authentic Jobs
- Web & Print Designer at Dance of the Deer Foundation (Santa Cruz, CA, Ca, US)
- Senior Front End Developer at Synacor, Inc. (Buffalo, NY, Ne, US)
- Senior Visual Designer at Fidelity Investments (Jersey City, NJ, Ne, US)
- Public Information Specialist I (Limited-Term) at West Basin Municipal Water District (Carson, CA, Ca, US)
DreamHost web hosting
Use the promo code 456BEREASTREET3 to save USD 20 when you sign up for DreamHost


Comments
I am jumping straight in without reading the article, but I will say that this is where Macromedia Contribute comes in to play with me.
It’s a great way to introduce the idea of standards as whole, doing so in a MS Word like situation, you just have to know how to set it up for standards. A post to be had out of this maybe!
I haven’t looked at Macromedia Contribute, but what you’re saying does sound interesting. Can it be used together with a CMS though? Is it practical when the client has multiple editors working on different (or the same) parts of a site? Hmm.. guess I’ll have to find the time to take a look.
Contribute is used to edit “static” files. We use it for our college site, enabling non-webmasters to edit their own content with freedom, but within the limits of templates etc.
So far it is a success, but it takes some setting up and careful access settings, particularly in an environment where users don’t use FTP to access the files. With FTP it is much easier.
Comments are disabled for this post (read why), but if you have spotted an error or have additional info that you think should be in this post, feel free to contact me.