There will be no “back to normal”Nesta

Faded out aerial view of an urban area taken on a fisheye lens

This is more than a month old. In terms of the coronavirus outbreak, that’s an eternity. But I still found this list of possible future scenarios interesting and thought-provoking.

It also comes with the major caveat that predicting the future is a mug’s game at the best of times, never mind during these times. This is inherently recognised in the fact that some of the predictions are contradictory.

I was particularly interested in the political, economic and sociocultural predictions. For instance, I have wondered if in the coming decades society will prioritise getting the basics right more over relentless innovation. This article suggests that may be the case, but that the shift may not last long.

The crisis may prompt a reappraisal of what society cares about most, with short-term attention focusing on the bottom of Maslow’s ‘hierarchy of needs’. (This may have the effect of, for example, boosting relative status of health workers and farmers, and diminishing ‘luxury’ industries, including leisure, gaming, arts – although history suggests that this will be short-lived, and the luxury status of some goods and services may ultimately be reinforced.)

We’re hiring a Senior Content DesignerWebsite and Communications Blog

View of Edinburgh Castle from our office

The University of Edinburgh Website and Communications team is hiring a Senior Content Designer. Come and join my team!

If you’re passionate about using evidence-based approaches to create great content that meets users’ needs, we want to hear from you.

Read the blog post to learn more about the position and how to apply.

UK infosec experts flag concern over NHSX contact tracing appLaurie ClarkeNS Tech

Mobile app displaying a text message from the government

This is the sort of reason why I don’t trust the state with my data as much as I trust many private companies. Apple and Google have worked together (itself a minor miracle) to develop a method of contact tracing that does not collect personal data and does not invade people’s privacy.

NHSX has rejected that model in favour of one that will enable them to deanonymise people, and store that information in a centralised database. This is the surveillance state. It risks reducing goodwill towards the NHS and other public institutions.

A statement for medical privacy campaign group Medconfidential reads: “Given NHSX has chosen to build an unnecessary massive pool of sensitive data, it must ensure that the data is well protected. With combined effort, GCHQ and NHS Digital will likely be good at defending the big pool of sensitive data. But there is no need to have that data. The best way to make sure data doesn’t leak, is to have chosen the method that never collected it.”

Principles and prioritiesJeremy KeithAdactio

What makes a good principle? How do you avoid principles that are mere motherhood and apple pie? According to Jeremy Keith, it’s all about establishing priorities.

He goes on to outline the danger of prioritising the experience of developers or designers above the user experience. He makes an interesting observation about a perceived difference in the way developers, er, develop and the way designers do.

Developer efficiency is prized above all else. Like I said, that would be absolutely fine if we’re talking about technologies that only developers are exposed to, but as soon as we’re talking about shipping those technologies over the network to end users, it’s negligent to continue to prioritise the developer experience…

I’ve been talking about developers here, but this is something that applies just as much to designers. But I feel like designers go through that priority shift fairly early in their career. At the outset, they’re eager to make their mark and prove themselves. As they grow and realise that it’s not about them, they understand that the most appropriate solution for the user is what matters, even if that’s a “boring” tried-and-tested pattern that isn’t going to wow any fellow designers.

HTML: The Inaccessible PartsDave Rupert

Following on from Gov.UK’s revelation about <input type="number">, Dave Rupert has compiled a list of other bits of HTML that can cause inadvertent accessibility issues.

There are some cases where even using plain ol’ HTML causes accessibility problems. I get frustrated and want to quit web development whenever I read about these types of issues. Because if browsers can’t get this right, what hope is there for the rest of us.

Not that we should give up, of course.

Why the Gov.UK Design System team changed the input type for numbersHanna LaaksoTechnology in government

Numeric keypad interface

The Gov.UK Design System team have discovered that using the HTML element <input type="number"> creates some surprising problems in certain environments.

Some of the limitations in assistive technologies such as Dragon Naturally Speaking are disappointing but unsurprising.

But Chrome deciding to convert large numbers to exponential notation is rather more eyebrow-raising. Then there is Safari adding commas to long numbers that are in fact credit card numbers. You have to wonder about some of the decision-making among browser vendors.

Coding is for everyone — as long as you speak EnglishGretchen McCullochWired

This year marks the 30th anniversary of the World Wide Web, so there’s been a lot of pixels spilled on “the initial promises of the web”—one of which was the idea that you could select “view source” on any page and easily teach yourself what went into making it display like that.

This article makes a great point about how this promise only truly works if you can speak English.

The process described above is exactly how I learned HTML. The fact that I would have to use “color” instead of “colour” is a mildly amusing inconvenience. I hadn’t really considered before how it must feel if you don’t speak any English.

I don’t speak Russian, and assuming you don’t either, does <заголовок> and <заглавие> and <тело> and <п> still feel like something you want to tinker with?

Join our team as a Content DesignerWebsite and Communications Blog

View of Edinburgh Castle from our office

Come and work with our team!

We are looking for three experienced Content Designers to join the University of Edinburgh’s Website and Communications team as we embark on major projects to launch our new web publishing platform and services.

If you’re passionate about using evidence-based approaches to create great content that meets users’ needs, we want to hear from you.

There are three positions available. [Find out more in the blog post](https://blogs.ed.ac.uk/website-communications/join-our-team-as-a-content-designer/). If you have any questions, just get in touch with me.

For my personal view on what it’s like working with the University of Edinburgh, check out my previous blog post: [Why I value working in user experience in higher education](https://duncanstephen.net/why-i-value-working-in-user-experience-in-higher-education/).

Opera: Phantom of the TurnaroundHindenburg Research

Screenshot of one of Opera's predatory loan apps from the Google Play store

If you still have the Opera web browser installed anywhere, now might be the time to stop.

With its browser business in decline, cash flow deteriorating (and balance sheet cash finding its way into management’s hands…), Opera has decided to embark on a dramatic business pivot: predatory short-term lending in Africa and Asia.

The article goes on to outline evidence of some seriously dodgy practices. What a sad end to the Opera story.