Archive for the 'accessibility web standards' Category

Reading List

Reading List

Reading List

Reading List

Reading List

The reading list – a day early as I’m off to the taverns and love-dungeons of Brussels for the weekend to teach Belgians how to drink beer.

Reading List

Dear webdevs, from European Blind Union

Many of you lovely readers aren’t on Twitter 24/7, so heres’s a blog retweet. Or a “re-bleet” as I like to call it.

This was posted yesterday by the European Blind Union (“The voice of 30 million #blind and partially sighted people in Europe”)

In other words: yes, please use viewport meta to make content responsive. But don’t muck around with maximum-scale, minimum-scale, and user-scalable properties, as these restrict zooming.

Couldn’t be clearer, could it? We’ve been asked nicely, by those who are affected, so let’s not do it anymore.

Reading List

Edge Conf: notes on User Queries

Edge Conference is basically like TPAC for web developers, so there are always great hallway and pub chats sparked by the main speeches. I’ll write up the breakout session that my boss, Andreas Bovens gave on Installable Web Apps/ Progressive Apps (the jury is out on the preferred name) tomorrow, but there was another interesting conversation I was asked about, so here goes.

In the CSS breakout session (which I didn’t attend) the idea of user queries was discussed. Orde Saunders wrote it up:

The twitter pitch for user queries is: “Like media queries but for user preferences.” … With user queries there would be a number of settings available in the user agent. Presented via a settings UI these would allow users to set certain preferences that were then made available in the runtime in the way media queries provide information about the user agent.

One problem with this is the classic web dev chicken-and-egg problem. Web developers wouldn’t use it until it’s in browsers, browser makers wouldn’t add it until consumers requested it, and consumers won’t request it because they don’t know it’s (theoretically) possible.

Another problem is that most developers wouldn’t care enough to add something to stylesheets that reacted to an expressed user preference for high contrast like this:

@user (contrast: high) {
  background-color: white;
  color: black;
}

and consumers wouldn’t bother expressing preferences if only a handful of sites took note of them.

The proper place for acting on user preferences, I think, is in the browser rather than in the stylesheets of individual sites. We’ve seen the latter experiment in the early 2000s in which some sites gave a method of upping the font size on their sites and remembering the user choice with a cookie. But this only worked for that site. So browsers and operating systems provided a mechanism for zooming, or over-riding the author stylesheets and imposing a minimum font size for all sites.

There are many examples of this: night mode settings that reverse colours; Opera Mini’s image quality setting that will always choose the lowest-quality image, regardless of what <picture> and srcset say, in order to save bandwidth (or even download no images at all); mouse gestures for those who prefer to browse that way; settings to avoid auto-start media; extensions that spoof location to get over location-based content blocking. or block advertising. These work on all sites, regardless of whether the developer cares about user preferences.

And I declare an interest here: I work for a browser vendor and such settings are exactly the kind of personalisation and UX enhancements that we compete on, now we’ve seen the light and stopped building nonsensical proprietary web “standards” to lock users in.

Reading List