WordPress.com is an easy way to start blogging. Get a blog, check out our features, read the latest announcements, choose from great themes, or learn about the team behind it.
Need help? Check out our Support site, then
I came to WordPress because nothing on Blogger will validate for anything. However, after looking through a number of your templates, I found one I liked that also validated.
Great, I went right to work.
The problem now is that the CSS won't validate. Is there anything you can do about that?
-->ptvGuy
This might sounds like a dumb question, but why is CSS validation so important to you?
If the blog displays as it should then what's the problem?
I know this sounds rude, it's not meant to be. I just don't understand people's infatuation with validation on free services.
Collin
Might also be helpful if you produced the error. :)
Cornell's right. It is a free service, and I didn't mean for my post to sound like a complaint. It isn't; I just wondered if there's anything that can be done. It's just ten errors from five of the lines in the CSS file.
As for why validation is so important to me, it's a big part of what my new blog is about. (http://ptvguy.wordpress.com/) I call it "anal coding." It's about achieving perfect coding (including accessibility, cross-browser compatibility, W3C validation, etc.) on the public television station websites that I maintain. My plan is not just to espouse perfect coding, but to demonstrate how it can be done in an environment where the majority of the content comes from outside sources. Hence, validated code in my own blog is a matter of credibility rather than preference.
Anyway, the errors can be viewed on the W3C CSS validator. If they can't be fixed, then they can't. Just thought I'd ask.
-->ptvGuy
P.S. If you guys really get some spare time available, it would be great if you could look over the accessibility problems in the template as well:
Nearly all the errors are down to the non-standard Mozilla/Firefox-specific code that's being used to produce the rounded borders. It's not wrong as such, it's just proprietary code that hasn't been embraced by the W3C. (Some people will say that's wrong, I will say they should switch to Firefox ;) )So no, they won't be fixing that.
So no, they won't be fixing that.
Agreed as it's browser specific. Normally I would suggest contacting the theme author but in this case, they'll probably answer with a "That's the way I wrote it" or some such.
As to accessability issues, (Damn, that scanner takes a while to read, doesn't it) most such users are using text browsers anyway. (And it's still loading...)
41 links = 8 minutes to read. They seriously need to work on their load balancing.
Most of the issues listed appear to be with your own posts and how you did your links within your sidebar. :)
Good luck,
-drmike
Some people will say that's wrong, I will say they should switch to Firefox ;)
I know. I nearly choked the first time I saw my blog in Internet Explorer. I like the stylish rounded corners. IE makes the whole thing look rather harsh.
...(Damn, that scanner takes a while to read, doesn't it) ... (And it's still loading...)
It just does that once in a while. Whenever it takes more than a few seconds, I leave and come back later.
As to accessability issues, ... most such users are using text browsers anyway.
Not so much anymore. The growth in ADA and Section 508 awareness has led to a growing trend in accessible websites that are still designed to be visually appealing.
Most of the issues listed appear to be with your own posts and how you did your links within your sidebar. :)
Actually, I'm not talking about the warnings, just the actual errors. I gave up trying to get rid of all the warnings; most of that is purely subjective, and I don't have that kind of time.
Anyway, thanks to everyone for your input on this. I just thought I'd ask about it.
-->ptvGuy
This topic has been closed to new replies.
ptvguy
drmike
