Crafted Pixelz

Crafted Pixelz

Markup Review

Crafted Pixelz is the personal portfolio of Abid Din. A Front End Web Developer, Designer and social media expert from Manchester, UK. Again be wary of the use of section and some of the links in the footer can probably be wrapped with a nav.

8 thoughts on “Crafted Pixelz

steven says
#

this site does not degrade gracefully in opera mini on my pda. i can’t view the source right now, or i’d be more constructive. :-)

steven says
#

I just tried visiting this web site in Lynx and I get an Error 406 even when I set Lynx to accept _all_ media types!

While viewing the source in Opera (not mini) I noticed . Is that acceptable syntax? I wasn’t aware that (x)html spec allowed a comma separated list of sources for href let alone in link. Is this a new (x)HTML5 thing?

steven says
#

Oops, let’s see if this works. What I noticed was <link rel=”stylesheet” href=”resource/css/reset.css,style.css,easyslider.css” />

James says
#

@steven I think the website is using the Rakaz Combine script (http://bit.ly/VZ3pHl) to combine and gzip resources, hence why the sources are separated by a comma. I use the same method on my site too.

BrianG says
#

May I ask why in the world one would ever view a website in Lynx, or more importantly, why would you think anyone would care that it didn’t work?

steven says
#

James: That’s interesting. Thanks for the link, I’ll have to look into this a bit more. :-)

BrainG: First of all, why not? The author claims to make accessible web sites so Lynx should work as well as the next browser. All the same, it’s weird that I got at 406 error considering the parameters that I allowed in my locally running copy of Lynx.

Secondly, some screen-readers are based on the Lynx browser. Are you seriously suggesting that a web author shouldn’t care about users of such screen-readers?

Or are web-sites only about the style? I thought HTML5 was supposed to help facilitate the dissemination of content, making it more accessible using proper HTML semantics.

Abid says
#

Steven, there’s a lot more to accessibility than adding Lynx support. When there are many, many websites out there dropping support for even IE, what would make one think that Lynx is a priority? It’s simply a waste of time and not worth fussing with.

Would you really spend countless hours developing for a browser that you’d maybe get 1 visitor from in a lifetime? I can’t think of anyone who would.

Just my £0.02.

steven says
#

Abid: Actually, countless hours aren’t required. I also think it’s a bit disingenuous of you to suggest that I’m saying that.

If you’re website serves up XHTML as xml then you can’t expect every browser to support it, Lynx included. However, if it’s (x)HTML served as html then simply coding to the specification and keeping in mind the concept of graceful degradation (iow, don’t use propriety extensions) is _all_ that’s required. (http://www.anybrowser.org/campaign/)

Btw, the weird Error 406 issue seems to have resolved itself and your site looks fine in Lynx. Which I think only proves my point.

Please note; no where did I say that your site doesn’t work in Lynx, just that I was getting an error trying a access it when using Lynx.

Please also note; my comments about Lynx usage were directed at BrianG and I continue to stand by what I said.

Got something constructive to say?