Léonie Watson
Accessibility Engineer, W3C Advisory Board

You're only supposed to blow the bloody doors off!

What do these imortal words, from Charlie Crocker (AKA Michael Caine) in The Italian Job, have to do with JavaScript? More than you might think.

It is often said that JavaScript makes things inaccessible with a screen reader. This is not true though. It is possible to do good and bad things with JavaScript (as with any other language, or even dynamite) - but it helps if you understand accessibility mechanics in the browser if you want to avoid unexpected consequences.

If you have ever used JavaScript to provide keyboard shortcuts, or used the ARIA application role to enable accessible software UI interactions on the web, there is a good chance it had unintended consequences for screen reader users.

Using code examples and screen reader demos, Léonie will look at accessibility mechanics in the browser, the new Accessibility Object Model (AOM) JavaScript API, and how to use JavaScript so you only blow the bloody doors off!

Léonie Watson

Léonie Watson (AKA Tink) began using the internet in 1993, turned it into a web design career in 1997, and (despite losing her eyesight along the way) has been enjoying herself thoroughly ever since.

Léonie is Communications director and Principal engineer at The Paciello Group (TPG), and also works with Government Digital Service (GDS) on the GOV.UK platform.

As a member of the W3C Advisory Board, and co-chair of the W3C Web Platform WG (working on specs like HTML5), Léonie is closely involved with the web standards community. She is frequently asked to talk about web standards and/or accessibility at conferences.

In her spare time Léonie blogs on tink.uk, writes for tech journals like Smashing magazine, SitePoint.com and Net magazine. She also loves cooking, dancing and drinking tequila (although not necessarily in that order).

Read more

Claudia Hernández
Developer at Dailymotion

Down the Rabbit Hole: JS in Wonderland

What even makes sense in Javascript ?

For a language originally created in 10 days it surely has a lot of quirks and perks many JS developers are unaware of. Sometimes, it might even seem like we fell down the rabbit hole only to find that NaN is actually a Number, undefined can be defined, +!![] equals 1, Array.sort()may not work as you suspected and so much other nonsense that can trip any JS developer’s mind. 

This talk is a collection of Javascript’s oddities and unexpected behaviors that hopefully will prevent some future headaches and help understand the language that we all love in a more deeper and meaningful way.

Claudia Hernández

Claudia Hernández is a Mexican frontend developer at Dailymotion in Paris. She has previously worked on projects for companies such as Air France, EDF, Groupe SEB and Aéroport de Paris. Claudia has a computer science background and loves learning emerging web technologies. When she is not coding, chances are you’ll find her reading a book ! Claudia also loves travelling and discovering new cultures.

Read more

Guillermo Rauch
Zeit, Socket.io


Before starting ▲ZEIT in November 2015, Guillermo was the CTO and co-founder of LearnBoost and Cloudup, acquired by Automattic in 2013. He's the creator of several popular Node.JS open source libraries like socket.iomongoose and slackin. Prior to Node.JS, he was a core developer of the MooTools frontend toolkit.

Read more

Mars Jullian
UI Engineer at Netflix

Best Practices for reusable UI components

React is awesome but even good frameworks don’t prevent you from writing bad code. This talk will focus on some key principles for writing reusable UI components that will make them fun to use and keep your co-workers from going crazy.

ReactJS has been adopted by many companies around the world and encouraged Frontend engineers to think about UI's in terms of small components, as opposed to large applications. While we as a community have started writing our UI's in terms of components, we are all still learning about the best way to write those components.

What size should the components be? How much state should each component contain?

This talk puts forth some best practices learned while building a reusable UI component library for an entire engineering team. And while the talk is specific to writing reusable UI components in React, the best practices and ways of thinking about components presented in this talk can be can be applied to components written in other frameworks as well.

Mars Jullian

I have always been in love with design and the way small details can affect someone's experience when interacting with a space or an object (I blame my parents). Through biology, physics, math, and computer science classes, I also fell in love with problem-solving. I became a front end engineer to be at the intersection between design and problem-solving, and because I am passionate about intuitive UX and designs that are born out of empathy for the user. Currently, I am putting these skills to use as a Senior UI Engineer at Netflix, where we aim to empathize with users all over the world and learn from each other every day.

Read more

Katerina Marchán
Developer, npm CLI team

A Brief History of Prototypes

JavaScript is probably the most famous example of a prototype-based language. But what is prototype-based programming? Where did it all come from? What's the big deal? Why is JavaScript's version of it the way it is?

Prototype-oriented programming has been around for over 30 years now. From its earliest days as a series of language extensions for various languages, to the release of Self and the compiler technology it developed that's used by Chrome and Node.js, to the rise of JavaScript and beyond -- it has been an incredibly influential take on the concept of object-orientation, and withstood the test of time against its class-based counterparts.

A Brief History of Prototypes will tell the story of this programming paradigm, the decisions and mistakes, the technological breakthroughs it led, its explosive rise in popularity on the back of ECMAScript, and puts it all in context with the way we use prototype-based languages today.

Katerina Marchán

I'm a JavaScript developer with a background in various functional dynamic languages who's really into programming language theory. I'm currently a dev on the npm CLI team and one of the admins for http://wealljs.org -- I like being involved with the JS community in various ways, helping mentor folks, etc. I've also been a maintainer for a minor front-end framework in the past (CanJS) and I do random hobby projects that I put up on github.

Read more

Paul Kinlan
Web Developer Advocate at Google


Read more

And more to come...

We will soon announce more speakers. Nordic.js is a single track conference with 8-10 talks per day by internationally renowned speakers as well as rising stars. Previous speakers include names like Douglas Crockford, Alice Bartlett, Tom Dale, Soledad Penadés, Bert Belder & Jake Archibald.

Are you interested in speaking at Nordic.js? Or do you know someone that would give a really interesting talk? Don’t hesitate to send us a proposal!