Christian Heilmann

10 reasons why our clients don’t care about accessibility and remote commenting

Tuesday, September 13th, 2005 at 2:22 pm

This morning Digital Web finally released the article I have been promising people at @media in July this year: 10 reasons why clients don’t care about accessibility.

The article describes reasonable facts that prevent us from reaching our goal to sell and maintain accessible web sites. I collected these from client interaction in the last three years with clients reaching from Blue Chip down to internal products.

Apart from the normal reaction whenever one of my articles gets released – groupies storming my flat, people offering their firstborn and donating thousands of dollars via paypal – I was also very happy to get lots of good comments.

Being yet another vain web publisher, I also checked who is linking to the article and to me, and found out about a phenomenon I had encountered earlier with other articles (insert thunder and lightning effect here):

Remote Commenting

What that is – and yes, I just made that term up – is the phenomenon that great comments about a certain publication tend to be made anywhere but where the publication lives. In this case, Roger Johannson’s blog got some really good feedback which would have been more beneficial at Digital Web itself.

It is not about the poor writer hunting for other feedback – or even accusations she cannot justify – it also is about the quality of the discussion.

Many a times an A List Apart article had the better solutions to the problem it discussed in the comments, and they are still available years later. If your valuable input was published somewhere remotely, nobody will ever find it once the article became old news.

Share on Mastodon (needs instance)

Share on BlueSky

Newsletter

Check out the Dev Digest Newsletter I write every week for WeAreDevelopers. Latest issues:

Don't stop thinking, AI Slop vs. OSS Security, rolling your own S3 Despite AI you still need to think, Bitter lessons from building AI products,  AI Slop vs. OSS security and pointer pointer…
200: Building for the web, what's left after rm -rf & 🌊🐴 vs AI What remains after you do a rm -rf? Why do LLMs know about a seahorse emoji? What image formats should you use? How private is your car?
Word is Doomed, Flawed LLM benchmarks, hard sorting and CSS mistakes Spot LLM benchmark flaws, learn why sorting is hard, how to run Doom in Word and how to say "no" like a manager.
30 years of JS, Browser AI, how attackers use GenAI, whistling code Learn how to use AI in your browser and not on the cloud, why AI makes different mistakes than humans and go and whistle up some code!
197: Dunning-Kruger steroids, state of cloud security, puppies>beer

My other work: