By Louis Lazaris on September 18th, 2009
Categories: Web Design Articles, Web Standards & Best Practices | 7 Comments
Don’t do it.
NEW COMMENT RULES: I no longer have any tolerance for people that use blog comments for link bait and branding. Although comments are pre-approved, comment rules are as follows:
If any of the above rules are broken, one of the following will happen:
I apologize for the inconvenience, but I'm no longer interested in comments that detract from the discussion. Thank you for your cooperation.
I couldn’t agree more!
Ah ah ah… I expected a very long article!
Very funny!
However I agree.
I also think this is all about embedded sound in web pages.
So we should stop audiocasting and videocasting? I don’ t think so.
@TC:
There are exceptions to every rule. Those types of “embedding” you mentioned are under the control of the user, which is fine in most cases.
What about musician websites?
As a live music lover, I go to a musician’s website for one thing: to hear what they sound like. I want it to play right away, and I want it to work.
It infuriates me to go to a musican’s formal, official, ‘designed’ website and have an impossible time digging to the music section, selecting a track, finding out I don’t have the right codec, etc.
Then I find the same musician on a ghetto myspace page and can actually hear what they play. And it plays immediately. Without. any. hassle.
I was really hoping this article had some best practices for including audio across various user agents. Hell, I even bookmarked it before I started reading.
What I wasn’t looking for was someone sharing their opinion with no explanation or caveat.
Impressive Webs not too impressive with this post.
I would have to disagree.
and here’s the reason: http://bit.ly/cCACCe
(turn sound on)…
I think for the majority of the web though, we should have the choice to hear sounds, not be forced to hear them.