Let’s make Machine Learning on the web and in the client happen. We need your input!

Machine learning and deep learning is the hot breakthrough in computing and a well-hyped topic. How “intelligent” your systems are can be a significant factor in sales and many a mobile device is sold as “personal AI” for your convenience.

O hai, robot

There is no question that learning interfaces are superior to hard-wired ones. The biggest example to me is the virtual keyboard on my mobile. The more I use it, the better it gets. It doesn’t only fix typos for me but also starts guessing the words following the current one correctly. And it doesn’t even matter if I swipe in English or German, the system is clever enough to recognize my needs based on earlier actions on my part.

Machine Learning is everywhere – it is just not accessible to most developers

I love the idea of learning machines and I think it is an inevitable step in the evolution of human-machine interaction. What we saw years ago in Star Trek – a ubiquitous computer at our beck and call with a voice interface – is now common. And we use it mostly to ask it about the weather. It makes no sense that we need to buy a certain device to reap the rewards of a new technology – I want this to be available on the web and any device.

The problem I have with this new evolution in computing is that it is opaque and locked to a few vendors. I love the web for what it is and how it broke down closed development environments and vendor lock-in when it comes to tooling. Anyone can start developing on the web, as it is the one and only truly open and distributed platform we have. The difference is the skill you have, not what device you have access to.

Now, when it comes to Machine Learning on the web, things look a lot less open and mature than I’d like them to be. In order to train models or to even get insights from models you need to use a third party service or library. Out-of-the-box, you can’t do any training or even image or facial detection in the browser.

Enter the WebML Community Group

I think this needs to change, which is why I am happy that there is a new community group of the W3C that works on an API proposal for Machine Learning on the web. This work started with Intel and Microsoft and I am happy we’ve come quite far, but now we need your help to make this a reality.

Let’s quickly recap why Machine Learning on the web and on device is a good idea:

  • Enhanced performance – results from trained model are returned immediately without any network latency
  • Offline functionality – lookups running on device don’t need a connection to a cloud service
  • Enhanced privacy – it is great that many cloud services offer us pre-trained models to run our requests against, but what if I don’t want that image I just took to go to some server in some datacenter of some corporation?

As with every innovation, there are current limitations and things to consider. These are some of the ones we are currently working on in the discussion group:

  • File size – well-trained models tend to be on the large side, often hundreds of megabytes. Using file sizes like that on the client side will result in I/O delays and also extensive RAM usage of browsers or your Node solution
  • Limited Performance – browsers are still hindered by a single thread JavaScript engine and no access to multiple cores of the device. Native code doesn’t have that issue which is why we propose an API that allows access to the native ML code on different OSes instead of imitating them.

The current state of affairs

Currently you can use tensorflow.js and onnx.js to talk to models or do your own training on device. Whilst there are some impressive demos and ideas floating around using those it still feels like we’re not taking the notion that serious.

That said, it is pretty amazing what you can do with a few lines of code and the right idea. Charlie Gerard’s learning keyboard is a great example that uses tensorflow.js and mobilenet to teach your computer to recognize head movements and then control a keyboard with it.

Why not just offer this as browser functionality?

One of the requests we often heard was why browsers don’t have this functionality built-in. Why can’t a browser create an alternative text for an image or recognize faces in a video? Well, it could, but once again this would mean your data is in the hand of some company and said company would control the functionality. It is no better than the offerings of native platforms in their SDKs. The web doesn’t work that way.

How can you help?

We’re right now in an experiment and investigating phase. As rolling out a new standard in the W3C isn’t a matter taken lightly we want to make sure that we deliver the right thing. Therefore we need to get real-life implementation examples where running ML on-device would make a massive difference to you.
So, please tell us what use cases aren’t covered in a satisfactory manner in the current web-talks-to-cloud-and-waits-for-data-to-come-back scenario.
We’re not looking for “I’d like to do facial recognition” but scenarios that state “If I had face recognition in JavaScript, I could…”. I’d be very interested in companies who do need this functionality to improve their current products, and I am already working with a few.
You can reach me on Twitter , you can fill out this form , or you can mail me at chris.heilmann@gmail.com with the subject “[WEBML scenario]”.

Thanks for your attention and all the work you do to keep the web rocking!

View full post on Christian Heilmann

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Feeling chart – to make you write more goodly with better emotionness

Lagwagon: Let's talk about feelings

(Or something like that)

A few weeks ago I found this incredibly useful chart that describes different emotions you can use when you write about, well, emotions.

unreadable chart

As you can see it’s been through the optimise-by-force mill of several posts on Facebook and other social media mangles and thus has become hard to read.

Fret not, for I spent the five minutes to turn it into a more readable interface.

You can find the source code of the HTML version on GitHub or click through it in all its glory on capable browsers. Older browsers get a simpler interface. I tried to make the showing and hiding as accessible as possible, but there is still space for optimization which I will ponder when I am back from the Christmas market.


View full post on Christian Heilmann

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

PHP 5 – End of Life

PHP Matters

PHP is a commonly used language for web sites and web application development. It is a general purpose, server-side scripting language run a web server that’s designed to make dynamic pages and applications. PHP is mainly focused on server-side scripting tasks, such as collecting form data, generating dynamic page content, or tracking session state. PHP also does much more.

Decorative image displaying text on a monitor

PHP 5.6 Released August, 2014

PHP 5.6 was released August 14, 2014 with end of support scheduled for December 31, 2018. As readers know, many sites rely on this version (or slightly older versions).

The main features of PHP 5.6 included:

  • Constant scalar expressions.
  • Variadic functions and argument unpacking using the … operator.
  • Exponentiation using the ** operator.
  • Function and constant importing with the use keyword.
  • phpdbg as an interactive integrated debugger SAPI.
  • php://input is now reusable, and $HTTP_RAW_POST_DATA is deprecated.
  • GMP objects now support operator overloading.
  • File uploads larger than 2 gigabytes in size are now accepted.

For those who need more information about this version, we recommend this link.

PHP version life cycle

Each release branch of PHP is fully supported for two years from its initial stable release. During this period, bugs and security issues that have been reported are fixed and are released in regular point releases.

After this two year period of active support, each branch is then supported for an additional year for critical security issues only. Releases during this period are made on an as-needed basis: there may be multiple point releases, or none, depending on the number of reports.

Once the three years of support are completed, the branch reaches its end of life and is no longer supported. A table of end of life branches is available.

Here are the currently supported versions of PHP. Keep in mind that PHP 7.1 was released roughly 2 years ago. Unfortunately, many sites have still not upgraded to PHP 7. This will become more of an issue after December 31, 2018.


After over a decade without any major upgrades to the language, PHP 7 made its debut in December 2015. Since this upgrade brings so many significant changes after such a long time, the process of adapting to it can be intimidating.

However, there are quite a few reasons to switch over to PHP 7, particularly if you use WordPress. The minimum PHP requirements for WordPress core have increased, and many plugins and themes may soon become incompatible with older versions of PHP. Meanwhile, those past versions will not continue to receive security fixes forever, which could leave your site exposed to hackers.

Making the switch to PHP 7 is essential. At the same time, there are a few issues to watch out for during the process, such as non-compatible scripts. In this article, we’ll show you how to handle the upgrade to receive the best possible results.


The simplest way to upgrade to PHP 7 is by asking your hosting company to update it for your account. This means you’ll need to be working with a hosting company that supports PHP 7 in the first place. Some companies make it easier to upgrade to PHP 7 than others.

This link has more information regarding a PHP upgrade for WordPress along with how to check compatibility issues.

What are the implications of doing a PHP upgrade?

When PHP is updated, it may break systems that relied on old or no longer supported features.  Existing themes, plugins, or modules may be incompatible with a PHP upgrade. To offset this risk, the best practice is to test the PHP update on a copy of your site (we recognize WordPress powers roughly 30% of web sites these days, but any site running older versions of PHP should be upgraded, regardless of the content management system or other application used). This initial testing allows developers to identify problems and test fixes before the update is made on your live site. Major hosting platforms like Pantheon and Acquia will automatically update applications that run on end-of-life versions. These automatic updates are a good safety measure but can break organizations’ sites unintentionally. Budget hosting platforms may continue to let organizations run end-of-life versions of PHP, leaving site owners unaware that their infrastructure is now vulnerable.

We found this article Ending the Year with a PHP Update contains a lot of useful information on why we need to do a PHP update and implications of doing this PHP upgrade.

For more information, we recommend


PHP is the programming language in which many common web applications are written – for example, Drupal, WordPress, and Joomla! PHP is the underlying framework for these content management systems. By the end of 2018, older versions of PHP (5.6 and 7.0) will officially be end-of-life and will stop receiving active security support.

The PHP team provides three years of support to major versions. This support includes fixes for bugs and security issues; however, at the end of three years, security patches will stop being released. These older PHP versions are then marked “end-of-life”.

In this case, PHP 5.6 and 7.0 are end-of-life on December 31, 2018, and December 3, 2018, respectively.) Continuing to run an end-of-life version is extremely risky and leaves a web server vulnerable to malicious scripts, malware, data breaches, etc. Although exploits to WordPress and Drupal – and their plugins and modules – get more media coverage, PHP vulnerabilities can be just as serious. Web Professionals should aware of these changes in the PHP.

Now is the time to confirm your site is running a newer version of PHP. We are always interested in your thoughts and look forward to your comments.

We encourage members (and non-members) check out our social media channels. If you aspire to be a web professional and don’t know where to start, we offer a number of beginning classes to our members via our School Of Web learning management system. As a member, your first class is free.

The post PHP 5 – End of Life appeared first on Web Professionals.

View full post on Web Professional Minute

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

How to tell at a glance if a website is fake

Hackers and cyber criminals are constantly looking for new ways to trick internet users into exposing their personal and private data. These attacks are easier to execute than trying to infect an entire computer or local network, but the results can be just as damaging.

The term phishing applies to any instance where a message or website pretends to be part of a legitimate organization but in fact has malicious intent. Most begin with an email distribution, urging readers to click on a link and enter their passwords, social security numbers, or other identifying information.

When a person falls victim to a phishing scam, they may not realize the extent of the impact. Nowadays, stolen personal data is commonly sold on the dark web, a trend which will encourage more attacks in the future.

Even computer experts can sometimes be fooled by a phishing attempt, so it’s important to know what to watch for when opening your email and browsing the web. This article will describe the top five methods for quickly determining whether a website is real or fake.

1. Examine the URL Closely

Screen capture of illegitimate website with descriptions of potential problems (and why they are problems).

All websites on the public internet must use the hypertext transfer protocol (HTTP) with a registered domain name, which is the part of a web address that includes .com or .net. So when you first browse to a new website or click on an unfamiliar link, be sure to take a few extra seconds to review the URL in the address bar. If the address does not start with HTTP or HTTPS, close your browser right away as the site is unsafe.

Hackers will often buy domains that look like they are connected to a reputable company but actually redirect to a nefarious site. These addresses typically have misspellings in their name or use a different suffix.

Another trick that cyber criminals use is the disguising of a URL within a phishing email message. They may have a hyperlink that shows a familiar .com address, but when you click on it, the link will point to an entirely different location. When it comes to URLs, don’t trust anything except for what you see in the address bar at the top of your browser.

2. Check For the SSL Certificate

Overview of SSL encryption.

Websites with a secure sockets layer (SSL) certificate are equipped to handle requests over an encrypted connection. This means that all data sent between your browser and the website’s back-end servers cannot be decoded by any outside entities or hackers.

One of the first indications of a suspicious website is a missing or out of date SSL certificate. You can quickly check for this by looking at the left side of the address bar in your browser to see if a padlock icon is displayed. A simple padlock indicates a standard SSL certificate, while a green bar means that the website is using an extended validation SSL certificate, which offers some additional levels of security.

Modern browsers like Google Chrome and Mozilla Firefox will automatically warn you when you try to load a website that has a missing or expired SSL certificate. To be extra careful, you can click on the padlock icon to view the status of the certificate and the entity who registered it. Never submit any credit card transactions or other personal data through websites that lack an SSL certificate.

3. Scan Developer Tools

When you load a website’s contents into your browser, the HTML displayed in the window does not always tell the full story. In fact, the most dangerous part of phishing websites is often hidden in JavaScript and other code that is invisible to the untrained eye.

Fortunately, you can use the Developer Tools option in Google Chrome to scan for suspicious threats. To launch it, open the Chrome menu, go to the “More tools” submenu, and choose the “Developer Tools” option. A new panel will open with various tabs of information.

Perform a full refresh of the webpage and first check the “Sources” tab to see what external content is being loaded by your browser. Then do the same in the “Network” tab. If you see an unfamiliar domain listed in the logs, consider closing your browser and manually navigating to the website with a typed URL. You can even examine the webpage’s HTML and JavaScript code through the “Elements” tab.

4. Look for Contact Information

Reputable websites will either include their contact information in a dedicated page or else within the footer at the bottom of the HTML content. If you are unsure whether to trust the company with your sensitive data, consider checking these locations to validate the website owner’s identity. If you can’t find any contact information at all, chances the site is dangerous or poorly maintained.

Website footers also typically include a link to a privacy policy, which is a critical piece of information for internet users concerned about how their data is stored and who prefer that it not end up being hawked for a few bucks on the Dark Web. The policy will explain what kind of information is tracked by the website, how long it is kept, and what a user needs to do to delete it.

5. Query the Website Registration

Overview of Whois query

Upon purchasing any public domain name on the internet, whether it’s by an individual or a large company, the new owner must register it through the Internet Corporation for Assigned Names and Numbers (ICANN). Think of it like a DMV system for website registration.

This can come in handy when you want to check on the validity of a suspicious looking website. You can navigate to a ICANN lookup service and query any domain on the public internet with a WHOIS command.

The result of WHOIS query will indicate the legal name and address of website’s owner. It cannot tell you for sure whether a website is real or fake, but if the information provided does not look genuine or references a suspicious organization, you should avoid visiting the address entirely.

Final Thoughts

While phishers can be sneaky, the real problem lies in a gullible public or one too busy to take the time to learn how to properly vet websites. These tips we’ve just covered aren’t foolproof but can go a long ways towards ensuring you don’t hand over your credit card or other personal information to every hacker who throws a fake website in front of you.

It’s like crossing the road. Stop for a few seconds, look both directions, and make sure you have the lay of the land before proceeding. Good luck and thanks for reading.

Editor’s note: Will Ellis develops the guts beneath beautiful websites and can’t wait to see what the blockchain world will look like once the technology fully emerges. He invests in cryptocurrencies and studies history.

Photo of member Will Ellis

The post How to tell at a glance if a website is fake appeared first on Web Professionals.

View full post on Web Professional Minute

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Codemotion Berlin – AI for good keynote and making people happier JavaScript developers

Audience at Codemotion Berlin

The day before yesterday I was honoured to open the Berlin Edition of Codemotion
. Codemotion touts itself the biggest developer event in Europe and is a multi-track event in Amsterdam, Rome, Madrid, Milan and many other European locations. I spoke there before in Rome, but I have to say the event grew much bigger and they do a great job with the marketing around the event.

Christian Heilmann presenting at Codemotion Berlin

My opening keynote covered the topic of ethics in AI and democratizing Machine Learning. I made sure to end on a positive note and invite anyone to start playing with and owning these technologies instead of just becoming consumers or victims of it.

In addition to the keynote, I also got interviewed by InfoQ on the same topic and you can read the interview and my answers here .

I collected the slides, resources and tweet reactions of the opening keynote on notist.

Christian Heilmann presenting at Codemotion Berlin

My second task was a more technical JavaScript talk about getting to grips with the changed world of JavaScript without feeling overwhelmed. Again, all the resources, slides and tweet reactions of the JavaScript talk are on notist.

I’d love to say more about the event, but with me being interviewed in between and generally having a bad cold, I didn’t watch too many other talks and stayed in the shadows.

That said, I managed to bring my partner and the web-famous Larry the dog to the speaker dinner and he was a much bigger success than I could ever be .

I’m looking forward to the videos and the interviews done at Codemotion and thank everyone I met, as there were some interesting leads for me.

View full post on Christian Heilmann

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Let’s all go to the pub – to learn about web development – Halfstack 2018 in London, England

Halfstack is a conference that is close to my heart. Because it is in London, because it is in a pub, because it is run by a person who is lovely, ginger and did so, so much for the JavaScript community over decades without having a huge ego or being weird: Dylan Schiemann.

This, in addition to a few other factors, makes Halfstack incredibly affordable, relaxed and at the same time full of great content. That’s why I keep presenting there, even when this time – for the first time – I had to fly to London to participate.

This year had quite an amazing line-up and a lot more talks than the past editions. The average talk length was a lot shorter than in the earlier years. To me, that’s a good thing. Better to make one point really well than treating an audience once again to the history of computing and how that relates to that brand new technology you actually wanted to talk about.

I shot a lot of photos, all of which are in this Google Photos album and here’s a quick recap of the talks.

The talks

Chris Heilmann, Microsoft: “Bringing best practices front and centre”

My opening keynote was about what we consider best practices and how they are often not applicable in context. How we miss out the opportunity of making them a starting point for new developers rather than something they have to learn to value after making the same mistakes we did before. With open and extensible editors like Visual Studio Code and tools to test the quality of our products while we deploy or even create them like webhint, we have a chance to embed our knowledge into the development flow instead of hoping people start caring.

My slides, resources and twitter reactions for ‘Bringing best practices front and centre’ are on notist.

Ada Rose Cannon, Samsung: “The present and future of VR on the Web”

Ada Rose Cannon and Alex Lakaitos

Ada Rose is chock-full of talent, knowledge and does a lot of good work to move the web into the third dimension and beyond. Working for Samsung’s Internet browser has its benefits as you have access to a lot of hardware to test. Ada showed examples from the history of VR/AR and XR and how it applies to web technologies. She ended with a call to action to support the Immersive Web Community Group of the W3C to get this work further along. It is fun to see someone who is so emerged in a topic explaining it in an accessible manner rather than drowning in jargon.

Alex Lakatos, Nexmo: “Building Bots with JavaScript”

Alex Lakatos worked with me at Mozilla, back then as a community member and was one of the first to benefit from their speaker training program. And it shows. In a few minutes he explained the benefits and pitfalls of bots as a platform and communication channel and showed in live demos how to train a bot in JavaScript how to understand humans. Both his slides and his demo code are available.

Alex also runs the developer avocados newsletter, a great resource for Developer Advocacy, call for papers and all that is related to that.

Anna Migas, Lunar Logic: “Fast But Not Furious: Debugging User Interaction Performance Issues”

Anna Migas presenting at halfstackconf

Anna Migas doesn’t only have an incredibly easy to remember Twitter handle (@szynszyliszys), she also has done a lot of homework in the area of web performance when it comes to making interfaces react quickly to the user. There is a truckload of information on the topic out there, and Anna did her best to distill it for the audience into sensible, digestible chunks in this short talk. Well worth a watch and share. Her slides are here to peruse.

Liliana Kastilio, Snyk: “npm install disaster-waiting-to-happen”

Liliana Kastilio presenting

Liliana Kastilio gave her first ever presentation and covered a lot of security ground about what not to do in your JavaScript. I expected a different talk considering the title, but I was not disappointed. A lot of sensible takeaways in a short amount of time.

Andrico Karoulla, Trint: “Enter ES2018

Andrico Karoulla on ES6

Andrico Karoulla is heir to a Fish and Chip shop and thus should already be set for life. However, his passion is telling people about the cool new features of JavaScript and he did so in a short talk. He didn’t only tell us about the features, but also managed to explain why they are important and what real implementation problems they fix. Good show, even when he had a tough time speaking into the mic and coding at the same time. 🙂

Stephen Cook, Onfido: “100% CSS Mario Kart”

CSS trick used to fake interactivity

Stephen Cook delivered the first jaw-dropping talk of the day by creating a CSS Mario Kart game. He applied a few interesting tricks, like a negative delay on CSS animations and using the validity state of the hidden form field to read out keystrokes in CSS. I’ve seen a few demos like that before, but it is pretty impressive to see it done live in such a short amount of time including explanations why some of these tricks work.
Both Stephen’s slides with explanations about the hacks and the demo of the Mario Kart animation are available

Sean McGee, Esri UK: “Buying a House with JavaScript”

Sean McGee presenting

Sean’s talk was a big let-down for anyone who thought they could learn how to afford buying a house in London with JavaScript as your only skill. If you came to learn about creating a clever mash-up of house offers, crime and travel information, you had a great time. Sean explained not only how to scrape the data, but also how to mash it up and display it in an intelligent manner that allowed him to find an affordable place with all the trimmings he wanted. As a former pipes/YQL and maps person, I was very happy.

Jonathan Fielding, Snyk: “Home Automation with JavaScript”

Jonathan Fielding is another person who spoke at a few Halfstack events and this time he covered the topic of home automation. It is a great topic and a market that needs cracking open as there are not many standards available. Instead you need to do a lot of reverse engineering and tinkering and Jonathan explained in an accessible fashion how to do this. Amongst other things, Jonathan lit and changed the colour of light bulbs on stage and deactivated his home security system – as you do.

Rob Bateman, The Away Foundation: “Reanimating the Web”

Rob Bateman with his TypeScript joke

Rob gave a similar talk at the warm-up of Beyond Tellerand Duesseldorf earlier this year, so you see the high quality and lots of work that went into this. He covered the history of animation on the web and went deep down into the nitty gritty on how we can ensure both that animations are buttery smooth and comparatively fast to native solutions doing the same things. A good reminder that we had a lot of innovation in the Flash space, and we now need to catch up again – both in tooling and in our approach to write animations.

Carolyn Stransky, Blacklane “The Most Important UI: You”

Carolyn on Self Care

Carolyn Stransky was the second “wow” moment for me this time. Her talk (slides are available here was about self care, how to be good to yourself and how to ensure we are not creating a horrible work environment. I’ve seen a few of these talks, but often they are high-level and “why aren’t we all better at this” finger pointing. Carolyn did a great job showing a truckload of resources you can use to make your life a bit easier and better and explained how to use them instead.

If you’re a conference organizer, contact her. This was absolutely lovely.

Tom Dye, SitePen and Dylan Schiemann, SitePen: “Cats vs. Dogs”

Tom and Dylan mostly did this talk to play out their fetish of wearing rubber animal masks:

Rubber cat and dog masks

Other than that kinky interlude, the talk was about all the weird little discussions and endless threads we have as a community about pointless things like tabs vs. spaces.

Cats vs. Dogs

The real important part here was though that they build a PWA that allowed the audience to vote for cats or dogs and control the speed of their tails wagging. You could also make them miaow or bark. ARE YOU NOT ENTERTAINED?

Cameron Diverand and Theodor Gherzan of Balena: “JavaScript at the edge”

Controlling a board of LEDs in JavaScript

Cameron and Theodor showed how to control a board of LEDs in JavaScript with sound coming from the audience. They didn’t talk about the Edge browser, which – to me – was disappointing. If you like the sort of thing of doing crazy hardware things in JavaScript, though, this was a lot of fun.

Jani Eväkallio, Formidable: “This Talk Is About You”

Jani did a poetry reading at the last Halfstack. This time he went further and did a visual storytelling kind of presentation reminding us that we’re not victims of the market we are in but should be much more in control over the quality of and the impact our code has on the world. This is tough to explain, it may make more sense to wait for Halfstack to release the video, as it was thoroughly enjoyable.

Jani does a lot of performing and is a joy to see present. Check it out. The keynote file of his talk is here. He also organises a technology comedy night called Component did Smoosh and the next one is 30th of November in Berlin.

Tony Edwards, Software Cornwall: “Beats, Rhymes & Unit Tests”

Tony Edwards is an incredibly passionate person about the web and organiser of the FutureSync conference, where he was crazynice enough to invite me to speak. In this session he covered the experimental web speech to text API and tried it on different rap lyrics with not much success. He then proceeded to do a live rapping session expecting the (mostly) British audience to go wild like a rap battle in Detroit or LA. It worked to a degree though, and his rap was much better converted by the API. All in all a thoroughly enjoyable talk by a multi-talented, nice bloke.

As a side node, using a full fledged deep learning API would give you much better results. The big thing about text recognition isn’t the interface to the browser, but the quality of the trained model. And they don’t come cheap which is why Mozilla tries to open-source that idea with their Common Voice project.

Professional detection software also started mixing audio recognition with lip-reading, which is incredibly exciting and yields much better results.

Joe Hart, Blend Media: Alpha, Beta, Gamer: Dev Mode

Competitive Tetris

Joe Hart’s talk was a splendid end of the evening. He covered oddities in the history of computer gaming and had a lot of interactive games with the audience. A Flappy Bird clone that worked by shouting at it, a Tetris clone where one player painted impossible Tetronimos and the other had to fit them in and other cruel measures to make the audience have fun and participate. Joe Hart is a Fringe presenter, so there is no question about the quality. This was fun from start to end.


Pub Quiz

Yes, Halfstack is different and the quality of the projector was questionable. The food was lovely though and having it in a pub means speakers are much more relaxed and lapses in their presentations much easier forgiven by the audience. Dylan and team are trying to take this concept on the road and for the first time plan to do a Vienna and NYC edition of the conference. I am really looking forward to seeing this succeed. I’ll be back and I’ll be having a great time again. Halfstack is an easy-going, yet valuable and highly diverse event, and well worth the money.

View full post on Christian Heilmann

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

November Update – Voice User Interface

What is Voice User Interface Design?

A voice-user interface (VUI) makes human interaction with computers possible through a voice/speech platform in order to initiate an automated service or process.” VUI design focuses on the process of interaction design for the user and the voice application system.

Smartphone with microphone icon highlighted

Everything You Should Know About Voice User Interface Design in 2018

Language is a communication method unique to human beings. We are now in the era of rapid development of artificial intelligence (AI) which will inevitably liberate our hands through the use of a Voice User Interface (VUI). Voice User Interface is a major trend in 2018 and has become a part of our daily lives. VUI is used in smartphones, smart homes, smart TVs, and a range of other products. All over the world, people are getting used to talking to Siri, Google Assistant, Cortana, or Bixby.

Voice User Interface design is a promising brand new field which provides solutions through voice control. With VUI and GUI combined, human-machine interaction can be enhanced and streamlined using input via facial expressions, gestures, and audio.

We encourage readers to follow this link for more information.

How to Design Voice User Interfaces

If you are new to designing voice user interfaces, you may quickly find yourself unsure of how to create great user experiences. The way users interact with voice user interfaces is very different from how they interact with graphical ones. Not surprisingly, users’ expectations for voice user interfaces are that the interaction will be more like communicating than using technology, because they associate voice and talking to other people, not technology. Voice user interfaces are growing in number, sophistication and reasonably priced availability. Here, you will learn what the users expect from voice communication and get practical guidelines for how to design great voice user interfaces.

This article has more information on designing the voice interface.

The Impact of Voice in UX Design

In the article The Impact of Voice in UX Design: And what to do about it, everything related  web and application designers, voice interaction represents, perhaps, the biggest UX challenge since the dawn of the touchscreen age has been explained.

  • Voice 101
  • What is Voice UI?
  • The Rise Of Voice
  • The Impact Of Voice On Web Design
  • The importance of words
  • Understanding user intent and adaptability
  • Engagement and personalization

The continuing growth of voice UX is undoubtedly a welcome development – as evidenced by the proliferation of platforms and devices integrating the tech, and the increasing number of people getting acclimated to using voice.

Some additional links

For those who would like to learn more about voice interfaces and various uses, we recommend these articles.

Voice user interface is emerging as a major trend in 2018. Readers should understand the implications and begin thinking of how best to incorporate this technology into their business goals.

As always, we look forward to your comments and feedback (whether you are a member or not).

We encourage members (and non-members) check out our social media channels. If you aspire to be a web professional and don’t know where to start, we offer a number of beginning classes to our members via our School Of Web learning management system. As a member, your first class is free.


The post November Update – Voice User Interface appeared first on Web Professionals.

View full post on Web Professional Minute

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Accessibility and WordPress Gutenberg

What is WordPress Project Gutenberg?

Gutenberg is more than an editor. While the editor is the focus right now, the project will ultimately impact the entire publishing experience including customization (the next focus area). Gutenberg looks at the editor as more than a content field, revisiting a layout that has been largely unchanged for almost a decade. This allows us to holistically design a modern editing experience and build a foundation for things to come.

Here is the link to get more information on the Gutenberg plugin.

WordPress logos on blue background.

Accessibility in Gutenberg

There is an accessibility team which provides accessibility expertise across WordPress to improve the accessibility of WordPress core and resources. The WordPress Accessibility Coding Standards states that all new or updated code released in WordPress must conform to the WCAG 2.0 guidelines at level AA. This is a good standard and an industry best practice.

However, this standard does not seem to be followed within Gutenberg. How accessible is Gutenberg in its current state (version 2.4)? The internal WordPress Accessibility team set up a list of minimum requirement, did code reviews and research, gave recommendations and set up user tests. Here is their short answer –

  • Gutenberg still needs extensive work to meet basic standards, like keyboard accessibility and semantics.
  • Especially for screen reader users, Gutenberg as it stands right now is a dramatic step back in usability.
  • There is a need to write a manual/documentation for assistive technology users.

The article Accessibility in Gutenberg – state of play written by Rian Rietveld focuses on the current state of Gutenberg accessibility.


Tim Berners-Lee, W3C Director and inventor of the World Wide Web says the power of the Web is in its universality. Access by everyone, regardless of disability, is an essential aspect.

The Web is fundamentally designed to work for all people, whatever their hardware, software, language, location, or ability. When the Web meets this goal, it is accessible to people with a diverse range of hearing, movement, sight, and cognitive ability.

The impact of disability is radically changed on the Web because the Web removes barriers to communication and interaction which many people face in the physical world. However, when web sites, applications, technologies, or tools are badly designed, they can create barriers that exclude people from using the Web.

Accessibility is essential for developers and organizations that want to create high quality websites and web tools, and not exclude people from using their products and services.

There are problems the accessibility team encountered as they tried to make the Gutenberg editor experience more accessible. The accessibility team lead of WordPress has resigned. The code base of Gutenberg is difficult to modify because no one in the WordPress accessibility team is a skilled React developer. So it was hard to implement changes. A lot of accessibility work has been done by the Gutenberg team but major issues still exist.

Another problem is that there was no React developer with accessibility experience in the community, and no React accessibility experts from outside the community were willing to work on the issues for free.

Rian Rietveld’s post – I have resigned as the WordPress accessibility team lead. Here is why explains more about some of the problems regarding accessibility.

Brad Frost provided another article about the accessibility in WordPress and why the WordPress accessibility team resigned.

Accessibility in Websites should be a core requirement

Since WordPress powers a significant number of websites (32% according to this WordPress statistics site), WordPress should be a leader with established best practices and web standards. Certainly, one can still use the classic editor (as a plugin) once Gutenberg is released, but that is only a temporary work around. How long will this classic editor survive? For those who need a refresher on accessibility, we offer the following resources/ reminders.

Project Gutenberg is scheduled for release on November 19. As a professional organization, we are very concerned that significant accessibility problems remain just before the official launch. We have been a proponent of web standards (including accessibility) for over 2 decades and find this approach troubling. We understand the need to improve WordPress to remain competitive in the marketplace. However, this should not be achieved with a loss of accessibility in the process. Since this project is a foundation for future enhancements to WordPress, accessibility issues must be addressed (and addressed soon).

What are your thoughts about Project Gutenberg and accessibility? We look forward to your comments.



The post Accessibility and WordPress Gutenberg appeared first on Web Professionals.

View full post on Web Professional Minute

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Learning about DevRel for the Asian market at DevRelSummit Singapore

I’m in the lounge of the Singapore Airport waiting for my flight. Yesterday I spent the whole day at DevRel Summit in a fancy event space listening to peers and colleagues how they tackle the task of reaching out to developers in the Asian market.

I didn’t have any speaking slot at this event, so I took the time to take a lot of photos and take lots of live notes of the event

I was very happy to be able to help out with a workshop for the leadership of the Asian Women Who Code chapter, giving an “Ask Me Anything” style Q&A in the local Microsoft office.

The things I was asked about the most were:

  • How to get invited to present at events. I pointed out that having a good online portfolio with what you can cover, examples of your work and your speaking terms and conditions help a lot. Feel free to fork and change my terms and conditions on GitHub
  • How to deal with bad feedback online
  • How much to charge for speaking engagements
  • How to ensure that more diverse people get a chance to represent your company

Many of the answers I gave sparked a constructive discussion amongst the directors of Women Who Code and resulted in answers presented at the closing panel of the DevRel summit.

I look forward to working more on this.

The summit was organized by the same people who run the DevRelSummit in Seattle, Barry Munstersteiger and Sandra Persing, together with a local crew and MC. It was held in a hotel in Clarke Quay, an entertainment section of town close to places for the after party and walking distance from my hotel. The event space was good, with excellent catering, good room facilities and excellent WiFi. A few more power outlets and a better sound system would have been beneficial, but the ample space to sit down and have conversations made up for it.

DevRel Summit

Some talk feedback

  • Jarod Reyes of Twilio did a really good job talking about reaching Dark Matter Developers, aka the ones not publicly visible (a term coined by Scott Hanselman) showing how Twilio found out more about their developers by doing in-depth research and surveys on what they are and altering their outreach and materials accordingly. It is also interesting to see that Twilio has a defined content creation program that offers money per article to people who want to write for them and give them writing training. They also have an open policy for people to ask for event sponsorship and they have a game you can host, Twilio Quest, that teaches coding and participating in open source.
  • Tomomi Imura of Slack explained where developers go to learn based on the Stackoverflow survey and described how to create developer education materials for different types of learners based on the VARK system (which is loosely based on the Honey&Mumford research into learner types). She also gave her insights into how to reach out to developers in Japan with important information how to run events.
  • Yohann Totting of Google explained in detail how they localized Google’s devrel model to the Indonesian market based on a government hackathon he organized. In the notes there are some interesting numbers on that.
  • Ali Spivak of Mozilla did a great job describing how Mozilla uses a data-driven approach to developer outreach and how they scaled and diversified their speaking engagements by training up community speakers. This is directly based on the work I started when I worked at Mozilla and fun to see how it worked out.
  • Keir Whittaker of Shopify had a very detailed talk about how Shopify had a different problem than other DevRel organisations as they reach marketplace owners with a slight developer angle or resellers and not developers. I was impressed with his candidness about what worked and what didn’t
  • The closing panel with directors of different Asian countries of Women Who Code was a good insight into how they work differently from country to country
  • The biggest win for us according to my agenda of learning more about the Asian market was the talk by Thomas Gorissen, organizer of JSConf Asia who gave a detailed talk about what the developer landscape and company interests are in Singapore


I had a great time and met a lot of lovely people to follow up with on right now. There is a lot of opportunity in the market in Asia and the differences to what the landscape is like in Europe is a good challenge to tackle. Thank you for the organisers and everyone involved to make this a great event worth the long flight.

Live notes

View full post on Christian Heilmann

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)