Training and events

There’s a number of upcoming events I wanted to blog about, partly to lend a hand to their promotion, and partly to tell you what I’m up to.


Workshops over the last 12 months have really increased for me – both in public workshops (often via events) and private company workshops. I’ve now finally got so much HTML5 content that companies can now create a “pick and mix” HTML5 workshop spanning over anything from 1 to 4 days.

I’m up in Manchester next week doing private workshops for the BBC on mobile web dev. Possibly my favourite quote from the last time I ran this event was from James O’Brien aka @sparrk:

Remy’s HTML5 for mobile workshop showed me how to do at least three things I’d previously thought were impossible.

There’s a few public workshops you can attend, starting with:

I’ll also be releasing a new workshop for Full Frontal – so keep an eye out for that :)


  • SourceDevCon – talking about using Node to go real-time (with a healthy dash of HTML5)
  • Mobilism – on debugging mobile devices and the pain and some technique (also 10% discount off regular ticket price (whilst stocks last!))
  • Future of Web Design – on how developers and designers can work better together (or at least from my perspective!)
  • Reasons to be “Appy” – mobile debugging again – this time in London (a small conference with only 250 places)
  • NDC 2012 – on the lesser known (or used) technologies in and around HTML5 that I think should be worthy of your attention
  • From the Front – the same HTML5 talk, but this time in Italy (early bird tickets still on sale until end of April)

I’m sure more talks will turn crop up and there’s a talk in me that I want to give about what I’ve learnt in developing JSBin over the last 4 years.

If you want me to talk…

Do get in touch (via my company site) if you’ve got an event and want to hear one of these talks, or equally if you company would like some in-house training.

Otherwise, I look forward to seeing and meeting some of you at the upcoming events!

3 Responses to “Training and events”

  1. Hi Remy,
    is there any chance to discuss the problem of the new HTML5 elements and assistive technologies? In Italy there’s a law (Legge Stanca, January 2004) which regulates the publication of public administration web sites. This law states that all new sites must be shipped with a well-recognized and approved DTD, which currently includes HTML 4 Strict and XHTML 1.0 Strict / XHTML 1.1. Following this rule, you can’t use the HTML5 DOCTYPE and the brand new elements. There’s been an heated debate among my colleagues of IWA Italy during the past years about HTML5 and accessibility, mostly regarding assistive UAs and HTML5 elements but also about the aforementioned law and HTML5. I wanted to let you be aware of what’s currently going on here in Italy when it comes to HTML5. I’m an avid fan of this standard, but if I should work for my government, well, I’ll probably fall back to XHTML. If you need more info on the Legge Stanca, let me know.


    Gabriele Romanato

  2. @Gabriele – I don’t generally talk about the HTML5 elements. To me personally, the interesting technology is what APIs the browsers are supporting. However – you’ve raised a really interesting point.

    Without writing a full blog post about my ideas on this (which I might be convinced to do, but time comes sparingly lately!) – I will say this:

    law states that all new sites must be shipped with a well-recognized and approved DTD

    This sounds like arbitrary rubbish. No browser has any knowledge of the DTD that you provide. If you point to a DTD that isn’t online or if you have a typo in the url, the browser doesn’t fail to render the page – because browsers, and Assistive Technologies don’t parse the DTD. Validators do, but that’s not what the law is for, it’s to ensure everyone can access your content.

    The HTML5 “versionless” doctype is well-recognised and in fact better supported than XHTML – because only up until IE9 did XHTML actually work (but who needs the benefits of MathML anyway – that’s the only real reason to use XHTML, right?). Providing IE with XHTML correctly delivered meant it was XML, which would break upon delivery.

    Most assistive UAs don’t follow the standards anyway – they’re development cycle is closed and slow. Assistive Tech like NVDA has the advantage of complementing the UA and being open source, it’s moving faster (last update of the code looks to be very recent).

    My personal opinion is that it sounds like the technology hasn’t been fully reviewed. From a validation point of view and most importantly the browser point of view, using an HTML5 doctype is just as compatible (and in fact more compatible) that the current “standard DTDs” the law is allowing for. As for new elements, if you want IE to recognise the elements (and that’s IE’s render engine, so I can’t speak for UAs like JAWS) you need JavaScript – and AT does support JavaScript – and ultimately if you don’t like that – don’t use the new elements, but those sites, in the future, will be the equivalent to sites today that use tables for layout.


  3. I fully agree with you. I was just playing the role of the devil’s advocate. ;-)

Leave a Reply
Not required

CODE: Please escape code and wrap in <pre><code>, doing so will automatically syntax highlight