Are you an SEO craftsman that takes pride in the code that you release or is validation just a complete waste of your time?
8 Comments
8 Comments
8 Comments
Search Engine Land produces SMX, the Search Marketing Expo conference series. SMX events deliver the most comprehensive educational and networking experiences - whether you're just starting in search marketing or you're a seasoned expert.
Join us at an upcoming SMX event:
Learn more about search marketing with our free online webcasts and webinars from our sister site, Search Marketing Now. Upcoming online events include:
Comments
The magic is in the comments.
Phil Green is my new hero.
I guess only when more sites start getting hammered in the courts will validation and accessibility become more prevalent in the site code.
Till then I'm still happy to spend the extra time sending out sites that at least attempts to tick all the boxes.
Since valid code and accessibility are not the same thing, your point is moot, NSM.
Well, at least I try Jill, for me trying to make a site accessible I've found a good starting point is getting the code to validate first.
@Paul - THe UK DDA makes no reference to the W3C as far as I am aware (I'll check again), but there is a 'responsibility' for all concerned to make your web pages accessible and it's thought if any case went to court the W3C would be cited - but being taken to court wont happen in the UK as the law stands.
@Jill - I agree but accessibility relies on standards (see recommendations) HTML accessibility tags are defined in standards (see “recommendations”) issued by w3c - if you have accessibility provisions and want them to work as expected you must work with the standards, not against them.
Valid code and accessibility go hand in hand.
A site can validate as strict (X)HTML, but the more important variable in the web standards equation is sematics. Oodles of nested tables used for layout will validate, as will using generic divs in place of list items for navigation, but the resulting markup would still be pretty inaccessible!
(Conforming to WAI and 508 specs will add to accessibilty however)