Based on your programming incompetence (that is not an insult), I'd say the easiest way to do it is just to get someone else to do it for you. You have enough readers one of them is bound to know flash or the javascript equivalent (which I'm assuming is another way to solve your problem). So put someone to work! Maybe you can offer a trade of some sort, like a drawing critique if they're into that kind of thing.

Sean's direct link approach is the best. I would add a TARGET="clear" to have the sound appear in a separate window and not replace the current one. However, as we learned on the George Liquor talking comic, everyone seems to have their browser set to use mp3s differently. Some play in the web browser, others use an external player like iTunes. When it comes up in a separate program, it's totally messed up.

It might be clearer to just put an audio link below each image like this...

That will put a text link to the sound below the picture. Usually people expect to see a larger version of the picture when they click on it. If you link to the sound, you can't link to the larger version too.

For usability, it's actually not the best idea to hyperlink directly to the audio file.

People with different defaults set with different browsers and OSes will get unpredictable results. It might force the sound file to open in a 3rd party player, or they could simply not have the correct codec.

Somebody before me had an interesting idea, but it didn't work exactly right the way my browser is set up. But what piqued my curiousity is that they used audio from Archive.org. Coincidentally, archive.org has a little web player doohickey that creates a link for embedding the audio file player when clicked upon. Then it's copy-pasta time. So if you had audio hosted at archive.org, it might be pretty easy to use their little feature to put their embedded player right under your pic on your blog.

An example of their "automagically" generated embed is something like this (but replace the square brackets around the tag with regular "<>", since embedding isn't allowed in comments.):