The Best of the Internets

Accessibility Requires App Developers to Consider Every End User

There’s a ton of great info in this article, but this one little bit is definitely worth calling out:

Android app developers know that there are over 24,000 devices in the marketplace that can potentially run their app. The number of end users that can be reached is staggering and that sheer volume of individuals means that app developers tailor their build for the majority of users and not the minority. iOS developers don’t have the same level of device fragmentation but there are over 1.5 billion apps in the App Store and (again) millions of end users to think about.

Now consider that this is focused purely on native apps and not products delivered on the Web. We should do everything in our power to deliver positive experiences to our users while simultaneously recognizing that it is impossible to deliver the same experience to each of them.

Your Computer School Sucks

Accessibility is an afterthought in much of our industry. In order to change that, education needs to change and code schools need to change. Karl nails it in this post:

While Hacker You should be applauded for their regular lunch-and-learns, I think that all computer schools should include accessibility embedded in core curriculum. It will create an alumni population better prepared to create interfaces that are universally usable. Their alumni will be differentiated by their ability to consider the user’s needs. After all, if you’re not developing for the user, who are you developing for?

Notes on Use of Multiple ARIA Role Attribute Values

Did you know the ARIA role attribute allows for multiple values? It’s how role supports fault tolerance: the first value (of the space separated list) is applied, but if the assistive technology in use doesn’t understand it, the second value will be tried, etc. until a usable alternative is found. It works a lot like font stacks.

ES6 in WebKit (October 2015)

This is an update on where things stand with the ECMAScript 6/2015 spec in WebKit. Currently in Safari for El Capitan & iOS9:

  • Classes
  • Promises
  • Map, Set, WeakMap, WeakSet, for…of loops, and
  • Symbols

Coming soon:

  • let, const, and class block scoping
  • a portion of the Reflect API
  • some of the current module specification
  • Tail calls
  • Default parameter values
  • Default destructuring values
  • Arrow functions, and
  • a portion of the internationalization API

For an excellent overview of ES6 support, consult this handy chart.