Comments on: Are You Using CSS3 Appropriately?

By: baagdi

baagdi — Fri, 28 Oct 2011 21:38:07 +0000

I am fully agree with this article. we should not misuse of techno tricks coz it is still not full browser and device compatible. Use it wehere it is necessary. Thanks to the author.

By: sheff

sheff — Mon, 17 Oct 2011 14:09:03 +0000

Nice article. It’s always good to be reminded that any technological enhancement is merely tool. A great tool can be used in inappropriate ways: I could use this hammer to try and change the channel on my remote control (hammer is a great tool but prob not the right one for the task). Keep UX as the focus and use CSS3 to enhance the completion of the task/experience etc.

By: Jay

Jay — Wed, 12 Oct 2011 02:44:11 +0000

Haha, I am definitely NOT using CSS3 appropriately..until now. Thanks for the article.

By: Bifter SVG Comic

Bifter SVG Comic — Mon, 10 Oct 2011 14:14:12 +0000

You’ll be pleased to know that the visual bugs on the Bifter website have now been fixed.

Please bear in mind though that the Bifter website is a demonstration of HTML5, CSS3 and SVG, thus its audience is predominately from the web developer sector. So it’s no surprise that both IE6 and IE7 users make up just 0.3% of Bifter’s web traffic.

Having said that, I think it goes without saying that any client work should always be inclusive for older browsers. On this occasion though Bifter doesn’t really fall into this category.

Thanks for the comments (both positive and negative) regarding the Bifter website. Although I don’t think the Visionaries (featured on the front cover) have had this much PR exposure since their heyday in the late 80s ;-)

By: Rajesh

Rajesh — Sun, 09 Oct 2011 19:16:55 +0000

Very useful article thanks for posting.

By: Lillan

Lillan — Fri, 07 Oct 2011 07:47:27 +0000

I agree with Mick and this article. Even if many browsers supports CSS3 we should never forget web standards and cross browser capabilities. Even if IE is special, we all know that, the big question still are; to whom are you designing? Yourself or the web?

As Mick points out, it aint so difficult to make an alternative stylesheet, linked with conditional comments, to IE and those browsers who have difficulties to support css3.

Have we gone so far in our eager to use css3 so we don’t give a s**t if the layout explodes in case the browser doesn’t support css3? I really don’t hope so, otherwise it is to be selfish.

By: Mick

Mick — Fri, 07 Oct 2011 03:39:01 +0000

Rafael, I don’t understand your reasoning here.
The web is supposed to be for everyone, so then why are so many so-called web designers so selfish when it comes to coding? Why wouldn’t we write code that fits in all browsers, isn’t that the point of the web, that it is accessible to everyone? Not just the elite?

It is not difficult to write code that supports all web browsers, so why do so many developers get upset when they have to put in a small amount of extra effort.

That is just lazy coding.

By: Ade

Ade — Fri, 07 Oct 2011 01:42:14 +0000

Re: “…in fact some of the changes and additions in the specs (especially HTML5) should enhance web accessibility.”

While certain others are reducing it. Whoever thought that it would be a good idea to permit more than one H1 heading per document has almost certainly never used AT.

Issues such as that and block-level anchors used as containers may well at some point be properly accommodated by a wide range of ATs: until then, it is just another good reason to be very disciplined when using HTML5 and very thorough when going through UA and AT testing.

It is, after all, a draft specification and a long way from becoming established as device-agnostic mark-up, which we already have in HTML 4.01.

By: Jacob Gube

Jacob Gube — Thu, 06 Oct 2011 23:00:36 +0000

RE: using the same techniques as before. I think the point is that, you can use old techniques (CSS image backgrounds, text-image replacement), so is CSS3 really adding anything new except a different way of doing things, in just this one particular instance?

Also, there were things that could’ve been done to make that site degrade better in older browsers. Using CSS3 or HTML5 shouldn’t take away from accessibility (and accessibility, to me, means universal design, which I consider to include people using older browsers, mobile phones, etc.); in fact some of the changes and additions in the specs (especially HTML5) should enhance web accessibility.

By: Josh Humble

Josh Humble — Thu, 06 Oct 2011 18:33:06 +0000

Great reminder to not follow the cool-aid, and to think pragmatically. I love what’s coming with CSS3, and I avidly study the specification, but we always need to think of the user experience, and how ANYTHING we do affects it. We’ve see a lot of iffy technique employed in bad context with our new CSS3 tools; makes me wonder, for example, in good print design, wouldn’t create obtrusive text shadows in paragraph copy, so why do it in web?