The site uses some of the new HTML5 structural elements including nav, footer and section. The section elements on the home page make sense but it’s rare for a section not to need a heading, so the links that are visual headings could go into headings.

URL: http://marqueemedia.com

The markup ticks a few boxes, for example the type attribute is absent from script and link elements, and some WAI-ARIA roles are used. However it seems a find and replace has been done on div with section, and a look at the document outline shows the effect of this. The humble div is still a very useful element when no semantics are required.

URL: http://www.weheart.co.uk

The site uses HTML5 technologies such as localStorage and offline appcache, as well as the geolocation API, a technology closely related to HTML5.

URL: http://beta.dublinbikes2go.com/

The site is a single page, using JavaScript to switch the tabbed content, so each part would be a good candidate for the section element. It depends on your interpretation of the nav specification, but I would say as it’s their content the social links could go into a nav.

URL: http://www.ernestograterol.com/

The site is really well constructed and makes good use of headings to create a nice outline. Other boxes are ticked too including hcard microformat and good use of new form input types and attributes. There is a little WAI-ARIA which could be rolled out to cover banner, navigation, form, complementary and contentinfo roles.

URL: http://www.mba-multimedia.com

The site is nicely constructed and each portrait is in a section element, which helps build a document outline. Perhaps they would be better as articles as they work as standalone items, but a bigger problem is the lack of heading elements within each.

URL: http://www.galleryofmo.co.uk

Good use of some of the new structural elements that HTML5 has to offer. Where there are two h elements together, they could be grouped in a hgroup. The section element is sometimes being used for styling purposes only, so a div would be more appropriate. The time element could be used to enclose the blog post dates.

Remember that the script element no longer requires the type attribute.

URL: http://srchea.com/

Good clean use of semantic HTML5 elements in this layout, although the “content” section element should probably use a div instead. The article element is used to enclose each entry and the time element is used for the post date, although the small element probably shouldn’t be used here. The canvas element is used to draw a diagonal red line in the page background.

URL: http://styro.alwaysdata.net

The site overall makes good use of some of the new structural HTML5 elements such as header, hgroup, nav, section and footer. The use of an aside in the footer to contain information such as copyright and other links probably isn’t ideal as this is still important information. And header elements which contain a single h element could have been left out.

URL: http://cmstec.de/

The social links in the top bar shouldn’t be contained within a nav element as they’re not the primary navigation of the site. Some of the section elements used could use a div as they seem to be used for styling purposes only.

The type attribute is no longer required for the script element.

URL: http://www.buttonbar-plus.com/