This talk is on a specific tool called 'Rooibos' I wrote as a Firefox extension that runs my unit tests in the background and reports results via the Firefox developer tools. If you're writing mocha tests and hate switching tabs back and forth or switching between a browser and a terminal, you'll definitely be interested in this on a practical level.
There are two levels to this talk, so after discussion on how I did this, what it looks like to embed a web app as a developer tool in a browser and how people can get started writing their own tools, I'm going to step back and look at how tooling for web developers by web developers in web technologies isn't just an efficiency or a trend, it's the right thing, it's a revolution, it's a movement and I want to recruit you.
Advice time!
Your talk proposal spends way too much time justifying why it needs to be a talk, as well as justifying the format it's presented in. Bollocks! You have a good idea already, so you don't need to justify anything. Instead, jump right into a friendly chat with an invisible audience. Tell a part of your story, but not all of it, as though we're just at Revolver having coffee.
"So, once upon a time, I was writing some tests, and we all (should have!) been there before. I always hated switching tabs between a browser and terminal, so I found myself writing this thing [...] so if you've ever wondered how to get started writing your own tools, this is the talk for you, because I firmly believe (and you will too by the end of this talk) that tools for web developers should be written by web developers."
Be way less clinical. Don't be afraid to be creative.
Instead of saying 'I am going to talk about x', try making it a little more like 'show don't tell' -
"I am going to show you how to build your own tools."
vs.
"We're going to take a look at how web developers can write their own tools, using the tools they have: HTML, CSS, and Javascript."