Robin Whittleton

Kyan vs. HTML5

Here at Kyan we like to keep up to date, so new technologies regularly come under the spotlight. This week’s focus: HTML5. Jumping straight into an unknown is rarely a good idea for a client project, but with no such qualms about internal projects I elected to rework our intranet.

First off, it’s important to point out that a lot of the promise of HTML5 comes from new technologies: the canvas element, <video> and <audio>, and the new &lt;input&gt; types (previously known as Web Forms 2.0). For our intranet these either have no obvious applications (&lt;canvas&gt; & &lt;video&gt;) or aren’t implemented in the common browsers being used (for us that’s Safari, Chrome and Firefox). Where we can benefit currently is the extra semantic elements and the tidying up that comprises the majority of the specification.

So what specifically did we change?

  • Simplified the header. The new simpler &lt;doctype&gt; and &lt;meta&gt; elements remove a bunch of cruft, and I took the opportunity to simplify the linked CSS and Javascript.
  • Changed some of the in-page containers to their ‘added semantics’ versions. For example, where previously we were using a &lt;div id="header"&gt; we can now just use the HTML5 &lt;header&gt;.
  • Changed some of the text elements to be more semantic. For example, previously the &lt;small&gt; element was defined to mean ‘make this text smaller’. In HTML5 it’s gained a semantic meaning of ‘this text is smallprint’.
  • Ran the code through an HTML5 validator with some interesting results. There isn’t an official W3 HTML5 validator yet, but you can use their development version (which is based on Henri Sivonen’s validator.nu). This is capable of some validation that the older W3 validator couldn’t do: e.g. warning if the number of table cells in a row doesn’t match the number of table headers.

The results

All in all, a lot of the benefit of this exercise came from a thorough reading the HTML5 spec and blogs like HTML5 Doctor even if we can’t directly apply those technologies yet. It also gave me a chance to refactor some of the older parts of the system into a more modern markup style. This should stand us in good stead when we start to use these technologies on a public-facing website.

Tags: html, html5, standards, upgrade

See more posts

Comments: 1

gav
commented on

Looking forward to seeing the 'cruft' tag implemented ;)

Add a comment

Note: comments are moderated before publication.

Most Popular

The Entifyr

Steven Wake

The Entifyr is a small web application that started life as an personal experiment to automate the removal of problem characters from client supplied content (usually Microsoft Word documents). The offending characters are replaced with corresponding entities (hence the name) al…

Get on the 'social media' bandwagon

Matt Hamm

‘Social media’ is the new buzz term. Everybody’s doing it, and why? Because it can generate masses amount of traffic to your website, which can easily turn into revenue. It’s really what ‘web 2.0’ is all about.

Garmin Edge 705 Data Recovery with DD & XML

Joel Richards

After recently taking part in a race across Scotland, using a Garmin GPS device (Edge 705) I had around 12 hours of GPS data which unfortunately seemed to get corrupted during the ride. The device was properly displaying the data on the unit, but Windows, OSX and Linux were all …

Google+