CreateInTO February Meetup

Accessibility with Alison Walden


  • blind and low vision internet users in US are almost as numerous as regular Canadian internet users
  • accessible sites give disabled users their privacy back. Accessible banking sites allow users to bank on their own. Accessible travel sites let users book flights on their own. Accessible commerce sites let users buy their own stuff.

Accessibility is part of UX design, not just development

  • information architects know the intent of the information and can structure headings
  • UX designers know what will be a link vs a button that performs an action on current content ahead of time
  • hidden wayfinding elements might be called out as issues in QA if they aren’t in the test plan. Instead, make them part of the tests
  • developers should implement accessibility features, but not design them

HTML structuring stuff

  • screen readers rely on HTML tags and structure to navigate pages
  • well structure heading tags (h1, h2, etc) are essential and should be chosen by information architects
  • developers sometimes use links and button interchangeably which is confusing for screen readers. One usually takes user to more content, the other modifies or submits existing content. Think about how to label links or buttons that offer filtering functionality
  • use hidden wayfinding elements (eg. [skip navigation links'( so user can jump to product grid of a store)
  • always use labels with form controls, even if the label is hidden eg. search fields in headers
  • tab ordering – think top to bottom and left to right

visual stuff

  • don’t disable the browser’s built in focus indicator! Designers can choose colours for it to look good with the page
  • focused elements could reveal more info as if they are being hovered over

law stuff

  • Many US websites that don’t follow guidelines have been sued by disabled users
  • Canada has fewer lawsuits and less enforcement.
  • In Ontario, WCAG A is the guideline for government and some business websites until 2021. Then it the guideline becomes WCAG AA.

Hugh Elliot talks about life of creative technologist

Hugh’s current gig has him building interactive installations with wondermakr

  • Work now includes driving places to fix installations that are ‘broken’
    • Nobody knows how it broke, or why it is broken it is broken. Be prepared with spare parts!
  • You get to buy stuff from awesome shops like robot shop, digikey, (sparkfun)[], and others I didn’t write down

  • Always buy spare parts

    • 3x the physical buttons you need because they will take a pounding from the public
    • extra monitors so you can swap screens quickly.

Gathering v40.0

Wednesday, Feb 22, 2017, 7:00 PM

159 Augusta Avenue Toronto, ON

47 Creators Went

Join us for our monthly gathering of creative developers, designers, hackers, makers and more.#accessibility #ux #design #hololens #mixedreality #making #installations7:00pm Doors open! Come grab some drinks and support Handlebar.7:30pm Alison Walden – Creating Accessible Experiences Starts with Experience Design”It’s a common misconception th…

Check out this Meetup →

Unity3D, VSCode, OS X and ‘The reference assemblies for framework “.NETFramework,Version=v3.5” were not found’ error

This happened to me in this environment:
* OS X 10.10.5
* Unity 5.6.0b7
* VSCode 1.9.1 with C# extension 1.7.0

I had this error inside of VSCode when I opened up a Unity project:

The reference assemblies for framework “.NETFramework,Version=v3.5” were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the framework you intend.

Also, VSCode’s code completion did not work. Even with the right version of OpenSSL:

$openssl version
OpenSSL 1.0.2k  26 Jan 2017

and dotnet:


Microsoft .NET Core Shared Framework Host

  Version  : 1.1.0
  Build    : 928f77c4bc3f49d892459992fb6e1d5542cb5e86

I found this fix here:

I had to install mono with brew

brew install mono

with that, I could run mono

$mono --version
Mono JIT compiler version 4.6.2 (Stable Sun Jan  8 00:00:20 GMT 2017)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors.
    TLS:           normal
    SIGSEGV:       altstack
    Notification:  kqueue
    Architecture:  amd64
    Disabled:      none
    Misc:          softdebug
    LLVM:          supported, not enabled.
    GC:            sgen

just to prove it is installed. VSCode’s OmniSharp acknowledged found mono and let me know in its own output window while starting up and loading the project in VSCode:

Discovered Mono file path: /usr/local/bin/mono
Resolved symbolic link for Mono file path: /usr/local/Cellar/mono/

Then my code completion worked. Yay!

Ember.js night with Full Stack Toronto

I think the location is a secret.

Jasna gave a live-coded demo of using Ember to make requests to a RESTful API to do CRUD operations and display the results. Ember is an opinionated, batteries-included framework. It has more opinions than Angular when comes to data modelling.

Vikram talked about his experience working with Ember.js at LinkedIn. I wrote down some words:

  • JSON API is a specification for JSON responses from servers. It exists to stop people from arguing about how to format arrays and objects and data in HTTP responses. Just stick to the specification and you’ll probably be OK.
  • Ember Engines are little composable chunks of applications that come together to form bigger applications. An Ember Engine has a lot in common in an Ember Application, but it can’t run on its own or control a router.
  • Glimmer 2 is a new faster renderer for Ember Applications
  • LinkedIn had to figure out server-side rendering for Ember for some pages that had to be visible to search engines & crawlers. Ember now supports SSR with FastBoot.

Ember.js – Feb FSTO Meetup

Wednesday, Feb 8, 2017, 6:00 PM

18 People Went

Check out this Meetup →

February 2016 Toronto Web Performance Group meetup

We met at Shopify‘s office.

David Bokan from the Google Chrome team in Waterloo talked about scrolling performance in Google Chrome


David Barreto talked about optimizing Angular 2 apps for download size & performance

There nice charts in his slides showing the effects of AoT compilation, different chunk loading strategies, and more

The Shiny and New in Chrome/Blink Performance + Big Performance in Angular 2

Monday, Feb 6, 2017, 6:30 PM

Shopify Toronto
80 Spadina Ave. 4th Floor Toronto, ON

39 Members Went

Welcome to 2017.We hope all had a wonderful holiday break. I know that we did. And we’re more than delighted to get things started in 2017. As always, we’re doing our best to bring you all corners of the web performance ecosystems in the form of fascinating talks.One item being tabled was the idea of having more presentations from browser vendor…

Check out this Meetup →

Host your own Git LFS with node-lfs-s3

Want to use Git LFS without a Git-as-a-Service provider like GitHub or BitBucket?

Stuff you will need

  • AWS S3 to store files at a low cost
  • node-lfs-s3 to communicate between Git and S3. This can run on your own machine or in the cloud.
  • Git LFS installed in your development environment or a server you control and available in the system’s PATH. I’m using git-lfs/1.4.4 (GitHub; darwin amd64; go 1.7.3; git cbf91a9) with git version 2.5.4 (Apple Git-61) on OS X, and something else on Windows 10.
  • GitHub for Windows comes with its own Git LFS executable which may override the version you install on your own.

Things to configure

Your Git repository needs a file called .lfsconfig which points it at the Git LFS server. Here’s an example:

url = "http://host:port/github-account-name/repo.git"
batch = true
access = basic
sslverify = true

Commands you will run

Start up node-lfs-s3 with a command like this:

LFS_BASE_URL=http://host:port/ LFS_PORT=port LFS_STORE_TYPE=s3 LFS_AUTHENTICATOR_TYPE=none LFS_JWT_SECRET=a_secret AWS_ACCESS_KEY=aws_access_key AWS_SECRET_KEY=aws_secret_key LFS_STORE_S3_BUCKET=bucket_name LFS_S3_REGION=us-east-1 node git-lfs-server.js