Note — — 78 words

Current affairs — Personal

Me holding a bottle of Corona

Virtual birthday party — 9pm tonight

It’s my birthday today. But I couldn’t really be bothered to organise a physical get-together. Instead, I thought it would be fun to imagine there was some horrific virus that meant we couldn’t really leave the house much, and I had to celebrate it remotely.

Update: This will now take place at 9pm, not 7pm as before.

Join us at 9pm for 40 minutes of free Zoom-based party times.

Bring your own Corona.

Linknote — — 84 words

Accessibility — Web

HTML: The Inaccessible Parts — Dave 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.

Linknote — — 79 words

Business — Human-centred approaches

McKinsey: CEOs have no clue what chief design officers do — Mark Wilson — Fast Company

Picture of a hipster drinking coffee with headphones hanging of a massive Mac screen. I guess that's what a designer is.

Talk about designers “having a seat at the table” generally leaves me cold. But this useful article explains why it can matter — but why designers have a duty to do more than simply be at the table.

Evidence has long suggested that companies with a strong design focus are more successful. The example of Logitech outlined here bears that out.

But if some CEOs don’t understand the value of design, it’s up to designers to articulate it properly.

Linknote — — 83 words

Accessibility — Human-centred approaches — Web

Why the Gov.UK Design System team changed the input type for numbers — Hanna Laakso — Technology 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.