On accessibility, I'd have loved to try out some screen readers but at the moment I write this article, I thought this accessibility analysis would deserve its own separate topic/article. A11Y is always hard.
The thumbs down was meant to be for the use of an icon font nowadays, in this case, FontAwesome. Don't get me wrong, I'm still using FontAwesome for many projects.
The thing is there are so many good reasons to use an SVG icon font system nowadays: pure vector, control over the individual shape symbols, positioning is easier thanks to knowing its exact size etc.
I'm afraid that using a regular table wouldn't allowed me to create this pricing table as it looks now. Although this is called a "pricing table", I think using a table isn't recommended in this case as it is quite restrictive.
Also, I avoided using HTML5 elements like "header" because I didn't wanted to include an extra HTML5 shim (for older browsers) dependency.
Regarding using <b> versus <strong>, this could be a long discussion here :). I think <b> just fits in this case as I don't want to add any importance from a content or SEO perspective.
I just updated the article and demo:
-Added CSS3 animation support for Mozilla 5+
-Fixed flickering the proper CSS3 animation
-CSS3 gradients syntax updated. Now, Safari also renders background stripes.