Is it important for our Rapidweaver sites to be w3c compliant?


(Gabrielle Vickery) #1

Sometimes I use http://nibbler.silktide.com to test my websites for a general feel for whether the site has been built correctly. I’m getting 0 scores on my w3c compliance, is this an important part of the build?

It looks like it means going into the code a fair bit, which I’m not sure I want to do. Should I do it?


(Will Woodgate) #2

I aim towards making everything I build for the internet HTML valid. Web standards exist to promote improved accessibility, performance and integrity of completed websites. I beleive HTML validation is a good benchmark of website quality. It’s sensible not to ignore the errors and to take a more proactive approach towards fixing things.

Making a website pass validation tests isn’t extremely difficult (if you’re coding a site by hand or using a publishing platform that advertises itself as W3C standards compliant). Unfortunately there are some RapidWeaver addons that use invalid HTML code, and these can subsequently “drag a good website under”. Hopefully it is something more RapidWeaver developers will learn about and work harder to resolve in future updates.

From a user standpoint, there is not much you can do. I certainly would not recommend that you start editing any code. It would be better to contact addon developers and request updates to addons that might be throwing validation errors. If it’s filed as a bug, it is more likely to get fixed. Or if you get a rather muted response (e.g. "validation doesn’t matter"), then it might be wise to look at switching towards using addons from other companies.

In all fairness to developers, the HTML5 specification has been painfully slow to get implemented. It has taken about a decade to get HTML5 to where it is now! A number of changes and u-turns have happened along the way. It has been difficult at times for developers to comply with everything; especially if other frameworks, APIs or web browser compatibility are pulling them in a different direction.

For example, for a long time RapidWeaver inserted rel=“self” into links (invalid code) and although that bug has since been fixed, the error still remains in any content migrated into RapidWeaver 6. It’s not something addon developers can fix, even though it looks like a theme or stack issue. Deleting the link and recreating it again is the only way to fix it. But that’s a lot of hard work and rel=“self” doesn’t cause any serious issues.

The automated W3C validator is very fussy and will flag even the most insignificant issues (like social media meta tags it does not recognise). But ultimately lines have to be drawn somewhere, and all designers / developers are subjected to the same specifications and rulesets. I do strongly believe we need specifications to work towards and the W3C validator is a very good tool for testing with.


(Gabrielle Vickery) #3

Hi Will, thank you so much for your detailed reply. I will contact the developer of the theme I’ve been using and ask them about it as you suggest.

I did just put my own site into the W3C validator and nearly gave myself a heart attack!

Regarding the rel=“self” link issue, are you saying that if I delete that particular link and re-instate it, the invalid code flag should then disappear?


(Will Woodgate) #4

Yes, for links you created yourself within your main content or sidebar regions (and if you’re using RW6), deleting and recreating the links again should fix the invalid rel=“self” errors.

But if links in your theme navigation menu contain rel=“self” code, then that is something for the theme developer to address. Likewise, any other errors might be something for the addon developer to look at.