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 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/

Clean minimalist site using nice HTML5 markup. Good use of the email input type. The bars section could arguably use a nav element as they are the primary navigation of the site. The p element used for the copyright information could be enclosed in a small element instead.

Some pages curiously use a tag element, which is not part of HTML5 nor HTML 4.01 for that matter. Bear in mind that the script element no longer requires the type attribute.

URL: http://dropdeck.com/

URL: http://www.theremedy.be/

URL: http://internetbureaubolt.nl/

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

The pulldown “mini” menu on the right doesn’t need to be in article or section elements here since they are being used for styling purposes only, so the div element would be more appropriate. It also causes the HTML5 outliner to display many untitled sections.

Each of the portfolio images should be contained within a figure rather than an article, with the figcaption element being used to the text associated with each one. The same could be said for the employee about page. Also remember that the type attribute is no longer required in script elements or style elements.

URL: http://stormen.nu/

Good to see ARIA roles being used throughout the site. This often gets overlooked. The content tends to be wrapped in section elements where a div might have been more appropriate as it seems to be used for styling only. Use could also have been made of the figure and figcaption elements in the portfolio. The social sharing links in the blog shouldn’t be contained with a nav as they take the user away from the site rather than navigate it.

The comments section and contact form could have made use of some of the new input types and the copyright information could have been wrapped in the small element. Remember that the type attribute is no longer required in the script element.

URL: http://www.etondigital.com/

All the content is grouped into one section element, with each different content area in its own nested section. This is correct since they are not related under a generic header, and so an article element would not have been appropriate.

The section used for the header should really be contained within a header element, since that’s what it’s for. The images within the slider could have been contained within a figure element. Nice to see care being taken to largely remove the type attribute from the script element (although there are some rogue ones) – but of course this isn’t absolutely necessary.

URL: http://hashfive.com/