Free Webinar: The State of HTML 5 Video

On Wednesday 16 April at 2pm EST, we hosted a free webinar on the State of HTML5 Video. Jeroen Wijering was joined by Sam Dutton of Google Chrome and Mark Robertson of ReelSEO to provide insights, present demos and answer your questions on HTML5 video.

Webinar Contents

As both online video and mobile video consumption grow exponentially, HTML5 is the standard for delivering high quality, cross-platform experiences. Join JW Player, Google and ReelSEO in this webinar to learn what is possible with HTML5 today, and what will become available in the near future! Topics include:

  • Current browser support for HTML5 Video – what works where?
  • Video playback on mobile – pitfalls and best practices.
  • Next-generation video codecs – VP9, H.265 and Daala.
  • The Fullscreen API – how to offer a lean-back experience.
  • Text Tracks & WebVTT -make your video accessible and interactive.
  • The new Streaming & Encrypted Media Extensions

This webinar will be hosted by Mark Robertson, Editor in Chief of ReelSEO. Co-presenters are Sam Dutton, Developer Advocate of Google Chrome and Jeroen Wijering, Founder & Creator of JW Player.

Webinar Replays

Didn’t make it? Don’t worry! We recorded the webinar and made it available for replay:

Also, be sure to check out both the HTML5 Rocks website and our regularly updated State of HTML5 Report.


    • Sibercat

      April 18, 2014 at 5:09 pm

      Dam i missed the webinar, where can i find the recording ?

    • Jeroen Wijering

      April 21, 2014 at 4:25 pm

      It’s in the post now!

    • Dean Flory

      May 2, 2014 at 10:51 pm

      Seems like there is a 1-2 minute lag in audio behind the video track, making it difficult to focus on what is being said since we’re already reading ahead on the next subject. Just FYI. Thanks for the info!

    • Per-Anders Legeryd

      May 6, 2014 at 8:09 am

      I experience the same lag as Dean.

    • Jeroen Wijering

      May 12, 2014 at 6:09 pm

      Ah, thanks for noting the lag. Fixed this in the encode…

Comments are closed.