Comments for alt tags

Comment on CMS Do’s and Don’ts by Dunn Consulting, LLC Blog | My decision to switch to a Web Content Management System: Part 1

Wed, 03 Mar 2010 02:14:57 +0000

[...] CMS Do’s and Dont’s [...]

Comment on CMS Do’s and Don’ts by My decision to switch to a Web Content Management System: Part 1 - Dunn Consulting LLC Musings

Mon, 01 Mar 2010 03:08:38 +0000

[...] CMS Do’s and Dont’s [...]

Comment on The Content Inventory: Roadmap to a Successful CMS Implementation by Content audits and inventories | qwertyphilia

Content audits and inventories | qwertyphilia — Sun, 14 Feb 2010 16:44:09 +0000

[...] The Content Inventory: Roadmap to a Successful CMS Implementation Article by Kassia Krozser which depicts content auditing as an essential part of a CMS implementation process. Helpfully points out that content inventories ‘almost always take longer than anticipated’. [...]

Comment on Content Migration: Making It Successful by James Robertson

James Robertson — Mon, 02 Feb 2009 23:43:38 +0000

Great article! You may also want to add this article to your list: Content migration: options and strategies

Comment on The Content Inventory: Roadmap to a Successful CMS Implementation by Kirk Biglione

Kirk Biglione — Wed, 12 Dec 2007 02:16:19 +0000

Uma, if you really know your content very well, then you may be able to get away with only document the content types. However, it’s been my experience that those implementing CMS systems are typically not in touch with all of the various content types in any organization. Conversely, the users who really know the content (domain experts) usually aren’t involved in the CMS implementation. The content inventory is a chance for the implementation team to collaborate with the domain experts in order to uncover all of the various content types, as well as exceptions and variations. Essentially, the content inventory is a form of content type discovery.

Comment on The Content Inventory: Roadmap to a Successful CMS Implementation by uma

uma — Mon, 10 Dec 2007 12:47:21 +0000

Can you explain why we need to identify every content. What significance it has got esp. for a CMS? I had always thought that in a CMS we need to understand only the types of content and their general schema… and the no of individual items based on the schema is typically populated by content users… so how will it affect the implementation?

Comment on CMS Do’s and Don’ts by We need editors, not a content management system » Alex around the world

We need editors, not a content management system » Alex around the world — Mon, 20 Mar 2006 17:02:14 +0000

[...] Another interesting article listing some Do’s and Don’ts about CMS is posted on Alttags blog. [...]

Comment on AJAX Hall of Shame: MarketWatch Reinvents The Blink Tag by Artueel blog » Blog Archive » Ajax en usability

Artueel blog » Blog Archive » Ajax en usability — Tue, 28 Feb 2006 19:49:07 +0000

[...] Een (grappig) artikel over overgebruiken van ajax vind je op alt tags. De site die in het artikel wordt vermeld is de website van Marketwatch.com [...]

Comment on Businesses Agree to Make Websites Accessible by Miguel from Ottawa, Canada

Miguel from Ottawa, Canada — Thu, 23 Feb 2006 19:00:52 +0000

Red Baron, you make me nervous. I hope you made your comments because you are merely ignorant and don’t understand what is being discussed. Because, if you think for a second that someone other than the owner of a website should be responsible for the barriers it creates, it’s time to grow up and learn to take some responsibility for your actions (and inactions).

Although I haven’t experienced any barriers because of my disability (mobility impaired, but highly functional) I still have a lot of sympathy for those who find web sites impossible to use. For those who don’t seem to get it, I wish I could show you a video of a visually impaired individual, spending quite a while filling out a form, only to find, in the end, he can’t click the submit button becuase the web designer used an image whcih captures XY coordinates instead. It’s exasperating, to say the least.

There are too many myths about refitting a website to make it more accessible. Of course refitting would take considerable more resources than accommodating accessibility at design stage, but the task can be done in chunks. Break it down into areas of effort and return on investment. First do the low effort/high return work. Then, bit by bit, the site becomes more accessible.

There are several reasons other than accomodating disabled persons as well. Consider the increased readability and better indexing by search engines.

But, I would like to think one would be doing it out of kindness, compassion and a desire to not exclude someone. Certainly, if the site is for a limited audience of friends, that’s one thing, but if it’s for a larger group or the public at large, it should be accessible. You wouldn’t keep a person of a certain race out of a site, why would you keep a disabled person out? Or are they less deserving?

My $0.02,
Miguel Sanchez

Comment on The Content Inventory: Roadmap to a Successful CMS Implementation by Stig Andersen

Stig Andersen — Tue, 07 Feb 2006 13:05:08 +0000

Tomas, Word really isn’t an option in my experience. I’ve tried it once, and will never do it again. Word documents are difficult to handle as they get larger(and they do content inventories do get large).

If I feel I’m out of control and elements may pop up, I leave numbers in between like this: 2.00.00; 2.10.00; 2.20.00; 2.20.10; etc. That way I can insert 2.15.00 if something pops up. Next best solution