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.

New sim swap hacks highlight carriers’ wobbly securityMartha DegrasseLight Reading

Diagram demonstrating how the attack works

Researchers at Princeton University called three of the four major [US] carriers and tried to convince customer service representatives to move phone numbers to new sim cards. Verizon, AT&T and T-Mobile each received ten calls from the researchers, who posed as customers.

Astoundingly, in all 30 cases the fake customers successfully convinced the carriers to move the numbers to new sim cards.

This matters because so many other services (such as banking systems) rely on SMS for authentication. If you only need to convince one customer service representative to swap a phone number, you could potentially have access to… almost anything.

The complex task of simplicityPaul Taylor

Sainsbury's Basics food packaging - washing powder, flower, canned tomatoes

It is human nature to add things, making them more complex. This feels like you’re doing something, but actually you’re probably making the situation worse.

We see this in web design. People like adding pages to their websites because it feels productive. But actually, the most effective websites are the ones with fewer, simpler pages.

The same can be true for any design, including the way we structure our work.

We often anchor around the wrong thing. That’s why some big institutions have no chance — they are hit by random plans and transformations rather than anchoring around purpose and iteration.

People collaborating with sticky notes on a flipchart

[We’re looking for a University of Edinburgh PhD student intern to work with us next year](https://edin.ac/3301QFy). This is an exciting time to join the Website and Communications team, and an opportunity to help us improve high-profile web services like MyEd and the University website. [Take a look](https://edin.ac/3301QFy)!

I was in a meeting once where someone pitched a really unrealistic idea. I don’t remember the details exactly. But let’s assume this idea depended on pigs being able to fly.

“But how will the pigs fly?”, we asked.

“Oh, we’ll have an algorithm.”

“OK… But, we don’t understand how the algorithm make the pigs fly?”

“I just said, the algorithm will sort that out.”

“But you haven’t explained how?”

“With the algorithm.”

“Algorithms can’t make pigs fly.”

“Algorithm!”

Don’t devolve your thinking to an algorithm.