Or if you just want two elements then use a sliding door approach and have one whole very long image sprite (longer than you need) and just apply it without a repeat. The downside is the increased filesize. If you wamt to use three images then wrap them up into one sprite and position accordingly.
Paul is quite correct in suggesting sliding doors – the downside he mentioned would be greatly offset by using image recombination so it would only take one image instead of three. I would do this with a span inside the anchor so hover states could be easily added without scripting assistance in older browsers. I would ALSO suggest easing up on all the unnecessary classes and ID’s, particularly since you seem to be using them JUST for applying presentation. Also, you’ve basically got 41k in three jpegs there to do a single 3.5k PNG file’s job so…
Paul also mentioned that you can’t apply multiple backgrounds – I think in general you missed that CSS is applied by ELEMENT, not by class – which is to say if you declare something once with an ID and once with a class, whatever you say on the ID overrides the class… just as a class overrides tag specific… you declare two classes on a element whichever one appears in the CSS second overrides the first – that’s called “specificity” and is a hefty chunk of the “cascade” in “cascading style sheets”.
Oh, and what’s with the tranny doctype, what is this 1998? The lack of a specific line-height, attempt to declare a fixed height – it’s all extra stuff that’s just not going to be reliable cross browser.
This is a very rough demo, it kind-of looked like your images weren’t quite sliced out of whatever they’re from completely. I included examples of it in a one atop the other list, a inline list, and as a standalone. For standalone, apply class=“button” to the anchor; if it’s all in a nice list like a menu then you make the menu have the “buttonList” class on it, and all the anchors inside the list will pick up on it. Figured it would be a good idea to show you both ways being we don’t know in what context you are using those buttons.